urxtnw
commented
2 years ago I've fixed it. There was a typo in the server IP. Very shameful.
Closed urxtnw closed 2 years ago
urxtnw
commented
2 years ago I've fixed it. There was a typo in the server IP. Very shameful.
What version of shadowsocks-libev are you using?
3.3.5
What operating system are you using?
Opensuse Tumbleweed
What did you do?
I am just running the command: ss-local -s "server-IP" -p 443 -l 1080 -k -m aes-256-gcm -v
What did you expect to see?
No errors
What did you see instead?
2022-07-29 11:26:07 INFO: initializing ciphers... aes-256-gcm 2022-07-29 11:26:07 INFO: listening at 127.0.0.1:1080 2022-07-29 11:26:14 INFO: connection from 127.0.0.1:53294 2022-07-29 11:26:14 INFO: connect to <VPN IP different than server IP, in Network Manager GUI>:443 2022-07-29 11:26:14 INFO: remote: "server-IP":443 2022-07-29 11:26:18 ERROR: getpeername: Transport endpoint is not connected
What is your config in detail (with all sensitive info masked)?
I am just running the command: ss-local -s "server-IP" -p 443 -l 1080 -k -m aes-256-gcm -v
Also: sudo firewall-cmd --state not running
Not sure what to do or what I'm doing wrong. I start ss-local then I start the VPN through the GUI in KDE, and when the VPN is trying to connect I get the "Transport endpoint is not connected" issue in the terminal. If the issue I filed is solved, I will close it by myself. Thank you!