Open f1h0 opened 4 years ago
journalctl -u shadowsocks-libev.service
will allow you to check the crash log of your service. If the error log is not verbose enough, you can pass some arguments to your executable to make it talk verbosely.
my brain exploded, I was so tired and went to look for the problem step by step.
Now my cool bunch Shadowsocks + V2ray + SSLH + Nginx + TLS CloudFlare It works great with productivity 60-75% internet channel speed
But that's as far as it is safe do not know where the data can be leaked
I have tried all of the options does not want to run through
systemctl start shadowsocks-libev.service
and if so runss-server -c /etc/shadowsocks-libev/config.json --plugin-opts "server;tls;host=host.my"
everything worksHere the error itself at startup
my config file shadowsocks-libev
contents could
/lib/systemd/system/shadowsocks-libev.service
how to solve the problem?