Shadowsocks-libev: Shadowsocks won't open any webpage - server_recv close the connection

[SquirrelCoder]

What version of shadowsocks-libev are you using?

shadowsocks-libev 3.1.0

What operating system are you using?

Server: Debian 9 Linux IJK 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 GNU/Linux

Client: Windows 10 Version 1709

What did you do?

Today Shadowsocks wasn't able to open (almost) any webpage (sometimes halfway through but not complete) and after about 2 hours it wasn't able to open any page (not even halfway through).
I tried to use simple-obfs plugin, but even with that plugin, no webpage can be opened.

What did you expect to see?

To visit websites.

What did you see instead?

This site can’t be reached
www.google.com took too long to respond.
Try:

Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_TIMED_OUT

What is your config in detail (with all sensitive info masked)?

config.json

{
    "server":"A.B.C.D",
    "server_port":42000,
    "local_port":1080,
    "password":"my_password",
    "timeout":600,
    "method":"chacha20-ietf-poly1305",
    "fast_open":true,
    "plugin":"obfs-server",
    "plugin_opts":"obfs=http"
}

running Shadowsocks-libev in verbose mode, shows the following log ss-server -c config-1.json -v

 2018-01-01 05:01:16 INFO: using tcp fast open
 2018-01-01 05:01:16 INFO: plugin "obfs-server" enabled
 2018-01-01 05:01:16 INFO: UDP relay enabled
 2018-01-01 05:01:16 INFO: initializing ciphers... chacha20-ietf-poly1305
 2018-01-01 05:01:16 [simple-obfs] INFO: obfuscating enabled
 2018-01-01 05:01:16 [simple-obfs] INFO: tcp port reuse enabled
 2018-01-01 05:01:16 [simple-obfs] INFO: listening at A.B.C.D:42000
 2018-01-01 05:01:16 [simple-obfs] INFO: running from root user
 2018-01-01 05:01:16 INFO: tcp server listening at 127.0.0.1:58987
 2018-01-01 05:01:16 INFO: udp server listening at A.B.C.D:42000
 2018-01-01 05:01:16 INFO: running from root user
 2018-01-01 05:01:21 INFO: accept a connection
 2018-01-01 05:01:21 INFO: connect to www.google.com:443
 2018-01-01 05:01:21 INFO: found address name v4 address www.google.com
 2018-01-01 05:01:21 INFO: found address name v6 address www.google.com
 2018-01-01 05:01:21 INFO: successfully resolved www.google.com
 2018-01-01 05:01:21 INFO: remote connected
 2018-01-01 05:01:21 INFO: accept a connection
 2018-01-01 05:01:21 INFO: connect to coinmarketcap.com:443
 2018-01-01 05:01:21 INFO: found address name v6 address coinmarketcap.com
 2018-01-01 05:01:21 INFO: found address name v4 address coinmarketcap.com
 2018-01-01 05:01:21 INFO: successfully resolved coinmarketcap.com
 2018-01-01 05:01:21 INFO: remote connected
 2018-01-01 05:01:23 INFO: accept a connection
 2018-01-01 05:01:23 INFO: connect to clients4.google.com:443
 2018-01-01 05:01:24 INFO: found address name v6 address clients.l.google.com
 2018-01-01 05:01:24 INFO: found address name v4 address clients.l.google.com
 2018-01-01 05:01:24 INFO: successfully resolved clients4.google.com
 2018-01-01 05:01:24 INFO: remote connected
 2018-01-01 05:01:25 INFO: accept a connection
 2018-01-01 05:01:25 INFO: connect to play.google.com:443
 2018-01-01 05:01:25 INFO: found address name v6 address play.l.google.com
 2018-01-01 05:01:25 INFO: found address name v4 address play.l.google.com
 2018-01-01 05:01:25 INFO: successfully resolved play.google.com
 2018-01-01 05:01:25 INFO: remote connected
 2018-01-01 05:01:31 INFO: remote_recv close the connection
 2018-01-01 05:01:31 INFO: current remote connection: 3
 2018-01-01 05:01:31 INFO: current server connection: 3
 2018-01-01 05:01:34 INFO: remote_recv close the connection
 2018-01-01 05:01:34 INFO: current remote connection: 2
 2018-01-01 05:01:34 INFO: current server connection: 2
 2018-01-01 05:01:35 INFO: remote_recv close the connection
 2018-01-01 05:01:35 INFO: current remote connection: 1
 2018-01-01 05:01:35 INFO: current server connection: 1
 2018-01-01 05:01:36 INFO: remote_recv close the connection
 2018-01-01 05:01:36 INFO: current remote connection: 0
 2018-01-01 05:01:36 INFO: current server connection: 0
 2018-01-01 05:01:52 INFO: accept a connection
 2018-01-01 05:01:52 INFO: connect to api2.poperblocker.com:443
 2018-01-01 05:01:52 INFO: failed to lookup v6 address DNS server returned answer with no data
 2018-01-01 05:01:52 INFO: accept a connection
 2018-01-01 05:01:52 INFO: connect to coinmarketcap.com:443
 2018-01-01 05:01:52 INFO: found address name v4 address api2.poperblocker.com
 2018-01-01 05:01:52 INFO: successfully resolved api2.poperblocker.com
 2018-01-01 05:01:52 INFO: found address name v4 address coinmarketcap.com
 2018-01-01 05:01:52 INFO: found address name v6 address coinmarketcap.com
 2018-01-01 05:01:52 INFO: successfully resolved coinmarketcap.com
 2018-01-01 05:01:52 INFO: remote connected
 2018-01-01 05:01:52 INFO: remote connected
 2018-01-01 05:02:07 INFO: remote_recv close the connection
 2018-01-01 05:02:07 INFO: current remote connection: 1
 2018-01-01 05:02:07 INFO: current server connection: 1
 2018-01-01 05:02:10 INFO: accept a connection
 2018-01-01 05:02:10 INFO: connect to 91.108.56.113:443
 2018-01-01 05:02:10 INFO: accept a connection
 2018-01-01 05:02:10 INFO: connect to 149.154.167.91:443
 2018-01-01 05:02:10 INFO: remote connected
 2018-01-01 05:02:10 INFO: remote connected
 2018-01-01 05:02:12 INFO: accept a connection
 2018-01-01 05:02:12 INFO: connect to 149.154.175.50:443
 2018-01-01 05:02:13 INFO: remote connected
 2018-01-01 05:02:13 INFO: accept a connection
 2018-01-01 05:02:13 INFO: connect to 149.154.175.50:443
 2018-01-01 05:02:14 INFO: remote connected
 2018-01-01 05:02:14 INFO: accept a connection
 2018-01-01 05:02:14 INFO: connect to 149.154.167.91:443
 2018-01-01 05:02:14 INFO: remote connected
 2018-01-01 05:02:15 INFO: accept a connection
 2018-01-01 05:02:15 INFO: connect to 149.154.175.50:443
 2018-01-01 05:02:16 INFO: remote connected
 2018-01-01 05:02:18 INFO: accept a connection
 2018-01-01 05:02:18 INFO: connect to 149.154.167.91:443
 2018-01-01 05:02:18 INFO: remote connected
 2018-01-01 05:02:19 INFO: accept a connection
 2018-01-01 05:02:19 INFO: connect to 149.154.175.50:443
 2018-01-01 05:02:20 INFO: remote connected
 2018-01-01 05:02:20 INFO: accept a connection
 2018-01-01 05:02:20 INFO: connect to 149.154.167.51:443
 2018-01-01 05:02:20 INFO: remote connected
 2018-01-01 05:02:21 INFO: accept a connection
 2018-01-01 05:02:21 INFO: connect to 149.154.167.51:443
 2018-01-01 05:02:21 INFO: remote connected
 2018-01-01 05:02:22 INFO: server_recv close the connection
 2018-01-01 05:02:22 INFO: current remote connection: 10
 2018-01-01 05:02:22 INFO: current server connection: 10
 2018-01-01 05:02:22 INFO: accept a connection
 2018-01-01 05:02:22 INFO: connect to 149.154.167.91:443
 2018-01-01 05:02:22 INFO: remote connected
 2018-01-01 05:02:23 INFO: accept a connection
 2018-01-01 05:02:23 INFO: connect to 149.154.167.51:443
 2018-01-01 05:02:23 INFO: remote connected
 2018-01-01 05:02:26 INFO: accept a connection
 2018-01-01 05:02:26 INFO: connect to 149.154.167.91:443
 2018-01-01 05:02:26 INFO: remote connected
 2018-01-01 05:02:27 INFO: accept a connection
 2018-01-01 05:02:27 INFO: connect to coinmarketcap.com:443
 2018-01-01 05:02:27 INFO: found address name v4 address coinmarketcap.com
 2018-01-01 05:02:27 INFO: found address name v6 address coinmarketcap.com
 2018-01-01 05:02:27 INFO: successfully resolved coinmarketcap.com

my service file cat /lib/systemd/system/ss-libev-1.service

[Unit]
Description=Shadowsocks-libev Config-1
Documentation=man:ss-server(1)
After=network.target

[Service]
Type=simple
LimitNOFILE=32768
ExecStart=/usr/local/bin/ss-server -a nobody -c /etc/ss-libev/config-1.json -d 8.8.8.8 -u

[Install]
WantedBy=multi-user.target

On my client, on chrome, I use the extension SwitchyOmega
and the rule contains

Protocol: SOCKS5
Server: 127.0.0.1
Port: 1080

Thanks,

[madeye]

I cannot find anything useful from your log. In addition, it looks a network issue, caused by either your VPS provider or your ISP.

So, I don't think it's an issue of shadowsocks-libev. To verify this you can try other shadowsocks implementations, e.g. https://github.com/shadowsocks/go-shadowsocks2

[SquirrelCoder]

Thanks for answer.

So today I changed obfs=http;obfs-host=bing.com to obfs=tls;obfs-host=github.com and for now everything works good. I am not sure what exactly the problem was!

Does the obfs-host have anything to do with it? 😕

[madeye]

Maybe. If it's a QoS related issue, you can try different combinations of port number, obfs and obfs-host.

[SquirrelCoder]

Thanks a lot. so for now I close the issue 😃