-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom fails to connect to Shadowsocks #131
Comments
Thanks, I replicated with Mullvad (and I also noticed they changed their Shadowsocks credentials too). The interesting thing is that after correcting the credentials, it does work for Mullvad built-in, but not when treated as a custom config file. And yet the logs look identical wrt. the firewall rules, etc.
|
A workaround is to immediately run the shadowsocks server inside the generated network namespace: $ vopono -v exec -o 1080 --custom ~/.config/vopono/mv/openvpn/albania-al.ovpn --protocol openvpn --no-killswitch firefox-developer-edition
# Immediately after in another terminal (get the namespace name from the log):
$ sudo ip netns exec vopono_c_4phFPBNz ss-local -s 43.245.163.18 -p 443 -l 1080 -k mullvad -m aes-256-gcm It will fail to connect at first, but it waits and then connects okay. It's not ideal, but the issue we have no way of knowing what the configuration and password, etc. for the shadowsocks server should be for custom providers, so we can't run it automatically as we create the network namespace. |
Hello, I can confirm that works. Two things would improve this.
|
Hello,
I have Shadowsocks configured to run a socks5 proxy on port 1080 (127.0.0.1:1080). When directly using the .ovpn file to connect with the OpenVPN application (Linux) it works correctly (socks-proxy and route set).
When I try to use the same configuration for vopono, it fails to connect.
"Attempting to establish TCP connection with [AF_INET]127.0.0.1:1080 [nonblock]\n1643794211.874470 1000021 TCP: connect to [AF_INET]127.0.0.1:1080 failed: Connection refused\n1643794211.874514 1 SIGUSR1[connection failed(soft),init_instance] received, process restarting\n1643794211.874526 21000003"
The text was updated successfully, but these errors were encountered: