use xshell on windows to create connection between VPS and SSH
root@brianmai:~# systemctl enable shadowsocks
root@brianmai:~# systemctl start shadowsocks
root@brianmai:~# systemctl status shadowsocks
● shadowsocks.service - Shadowsocks
Loaded: loaded (/etc/systemd/system/shadowsocks.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-09-10 03:27:22 CST; 2s ago
Process: 31303 ExecStart=/usr/bin/ssserver -c /etc/shadowsocks.json (code=exited, status=203/EXEC)
Main PID: 31303 (code=exited, status=203/EXEC)
Sep 10 03:27:22 brianmai systemd[1]: Started Shadowsocks.
Sep 10 03:27:22 brianmai systemd[31303]: shadowsocks.service: Failed to execute command: Permission denied
Sep 10 03:27:22 brianmai systemd[31303]: shadowsocks.service: Failed at step EXEC spawning /usr/bin/ssserver: Permission denied
Sep 10 03:27:22 brianmai systemd[1]: shadowsocks.service: Main process exited, code=exited, status=203/EXEC
Sep 10 03:27:22 brianmai systemd[1]: shadowsocks.service: Failed with result 'exit-code'.
1 Reply
tommydavidson
Linode Staff
I am not familiar with xshell, however it looks like you are trying to use Shadowsocks, and it is having issues starting up. A Google search for the error:
shadowsocks.service: Main process exited, code=exited, status=203/EXEC
did not turn up anything relevant to Shadowsocks, although I did find some information in this discussion on GitHub, which suggests that this error can occur when the actual location of the proxy server differs from it's default setting. I do not know for sure if this would hold true for Shadowsocks, but it may be worth looking into. The error also comes from systemd, so checking out your logs for relevant errors may also be a good idea.
If you are not able to find a resolution, it may be worth trying to set this up again from the beginning, following the instructions in our Shadowsocks guide, which covers configurations for both Ubuntu and CentOS 7.