Настройка VDS сервиса Vultr через Putty - ошибка shadowsocks

Настраиваю виртуальный сервер в Японии по этой инструкции: https://telegra.ph/Ustanovka-svyazki-proksi-serverov-Habarovsk--Tokio-11-30. Необходимо для снижения пингов при торговле на азиатских биржах.

введите сюда описание изображения

После команды "systemctl status shadowsocks-libev-server@config" у меня выходит 2 вот таких ошибки:

[email protected] - Shadowsocks-Libev Custom Server Ser>
     Loaded: loaded (/etc/systemd/system/[email protected]; ena>
     Active: failed (Result: exit-code) since Mon 2025-03-24 18:17:23 UTC; 5s a>
       Docs: man:ss-server(1)
    Process: 1280 ExecStart=/usr/bin/snap run shadowsocks-libev.ss-server -c /v>
   Main PID: 1280 (code=exited, status=255/EXCEPTION)

Mar 24 18:17:23 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Servi>
Mar 24 18:17:23 vultr systemd[1]: [email protected]: Main>
Mar 24 18:17:23 vultr systemd[1]: [email protected]: Fail>
lines 1-10/10 (END)...skipping...

 [email protected] - Shadowsocks-Libev Custom Server Service for config
     Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2025-03-24 18:17:23 UTC; 5s ago
       Docs: man:ss-server(1)
    Process: 1280 ExecStart=/usr/bin/snap run shadowsocks-libev.ss-server -c /var/snap/shadowsockslibev/common/etc/shadowsocks-libev/config.json (code=exited, status=255/EXCEPTION)
   Main PID: 1280 (code=exited, status=255/EXCEPTION)

Mar 24 18:17:23 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 18:17:23 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 18:17:23 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.

Команда по фиксу в инструкции "systemctl enable --now shadowsocks-libev-server@config" не помогла, ошибка сохраняется

Логи выдают следующие данные:

-- Logs begin at Mon 2025-03-24 17:19:32 UTC, end at Mon 2025-03-24 18:20:48 UTC. --
Mar 24 17:25:11 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 17:25:11 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 17:25:11 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
Mar 24 17:25:34 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 17:25:34 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 17:25:34 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
-- Reboot --
Mar 24 17:28:07 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 17:28:09 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 17:28:09 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
Mar 24 17:30:04 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 17:30:04 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 17:30:04 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
Mar 24 17:32:58 vultr systemd[1]: [email protected]: Failed to load environment files: No such file or directory
Mar 24 17:32:58 vultr systemd[1]: [email protected]: Failed to run 'start' task: No such file or directory
Mar 24 17:32:58 vultr systemd[1]: [email protected]: Failed with result 'resources'.
Mar 24 17:32:58 vultr systemd[1]: Failed to start Shadowsocks-libev Default Server Service.
-- Reboot --
Mar 24 17:36:22 vultr systemd[1]: [email protected]: Failed to load environment files: No such file or directory
Mar 24 17:36:22 vultr systemd[1]: [email protected]: Failed to run 'start' task: No such file or directory
Mar 24 17:36:22 vultr systemd[1]: [email protected]: Failed with result 'resources'.
Mar 24 17:36:22 vultr systemd[1]: Failed to start Shadowsocks-libev Default Server Service.
Mar 24 17:38:41 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 17:38:42 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 17:38:42 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
Mar 24 17:53:20 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 17:53:20 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 17:53:20 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
Mar 24 17:57:46 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 17:57:46 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 17:57:46 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
-- Reboot --
Mar 24 18:00:53 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 18:00:55 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 18:00:55 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
-- Reboot --
Mar 24 18:04:40 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 18:04:42 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 18:04:42 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
Mar 24 18:06:11 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 18:06:11 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 18:06:11 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
-- Reboot --
Mar 24 18:13:51 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 18:13:53 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 18:13:53 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.
Mar 24 18:17:23 vultr systemd[1]: Started Shadowsocks-Libev Custom Server Service for config.
Mar 24 18:17:23 vultr systemd[1]: [email protected]: Main process exited, code=exited, status=255/EXCEPTION
Mar 24 18:17:23 vultr systemd[1]: [email protected]: Failed with result 'exit-code'.

Пошагово следую инструкции, но ничего не работает. Раз 10 попробовал. Сервер Токио на Vultr также несколько раз переустанавливал. Подскажите, пожалуйста, что можно сделать, чтобы сервис в конечном итоге запустился и статус изменился на "active running". Шаги делал только те что в инструкции, сам более ничего нигде не менял.


Ответы (0 шт):