Closed gadget1999 closed 5 years ago
Check your firewall rules first.
Tested on Debian 10 hosted on Digital Ocean and shadowsocks-libev operating normally.
Thanks for the quick response. On the Linux machine I upgraded from 9 to 10. It started working today (only change was re-deployed the Azure VM). On the original Debian 10 machine, it's still the same. I tried to use a web server using the same port and it's accessible (so the firewall should be fine); I also enabled debug logging on v2ray-plugin, but no logs when trying to connect.
I guess could be related to something unique for this server. Since it's not related to Debian 10, I'll close this issue.
Some update: on the Linux server that's not working, after I switched from QUIC to TLS, it started working. I'll just use TLS going forward.
More update on this: found out that the culprit is load balancer in front of the VM. Only TCP was forwarded and QUIC needs UDP. This is related to your above firewall comment. Thanks!
When run the container on Debian 9 (Stretch), everything works fine. But if run the same container on Debian 10 (Buster), Android client cannot connect, there is no error in the container.
I also upgraded a working Debian 9 machine to 10, then the container will stop working.
Any suggestions or tips would be appreciated.