Shadowsocks-libev: 3.0.5服务器端运行一段时间后报错无法正常使用

Created on 25 Mar 2017  ·  5Comments  ·  Source: shadowsocks/shadowsocks-libev

service shadowsocks-libev status
● shadowsocks-libev.service - Shadowsocks-libev Default Server Service
Loaded: loaded (/lib/systemd/system/shadowsocks-libev.service; enabled)
Active: active (running) since Sat 2017-03-25 09:54:35 EDT; 1h 46min ago
Docs: man:shadowsocks-libev(8)
Main PID: 28815 (ss-server)
CGroup: /system.slice/shadowsocks-libev.service
├─28815 /usr/bin/ss-server -c /etc/shadowsocks-libev/config.json -u
└─28816 obfs-server

Mar 25 09:54:35 tragic ss-server[28815]: 2017-03-25 09:54:35 [simple-obfs] INFO: listening at 0.0.0.0:2017
Mar 25 09:54:48 tragic ss-server[28815]: 2017-03-25 09:54:48 ERROR: unable to resolve twoxahqgkdt
Mar 25 09:54:48 tragic ss-server[28815]: 2017-03-25 09:54:48 ERROR: unable to resolve xdbkunfmxgyddky
Mar 25 09:54:48 tragic ss-server[28815]: 2017-03-25 09:54:48 ERROR: unable to resolve rgngzpedx
Mar 25 10:15:21 tragic ss-server[28815]: 2017-03-25 10:15:21 ERROR: unable to resolve xsybcthylewukm
Mar 25 10:15:21 tragic ss-server[28815]: 2017-03-25 10:15:21 ERROR: unable to resolve sooikanoa
Mar 25 10:15:26 tragic ss-server[28815]: 2017-03-25 10:15:26 ERROR: unable to resolve eivfqnzkotnhi
Mar 25 10:54:24 tragic ss-server[28815]: 2017-03-25 10:54:24 ERROR: remote recv: Connection reset by peer
Mar 25 10:57:05 tragic ss-server[28815]: 2017-03-25 10:57:05 ERROR: remote recv: Connection reset by peer
Mar 25 11:09:51 tragic ss-server[28815]: 2017-03-25 11:09:51 ERROR: remote recv: Connection reset by peer

这时客户端无论用不用插件都无数据。

cannot reproduce

Most helpful comment

在server的config.json 里面加上 "nameserver":"8.8.8.8"
可以解决unable to resolve *的问题,至少对我是有用的

至于connection reset,这个大概是网络本身问题或者gfw吧

All 5 comments

unable to resolve twoxahqgkdt 无法解析此域名
remote recv: Connection reset by peer 连接被对方重置
你客户端访问的什么业务?

主要就手机上用,chrome和firefox就一般的网站啊。网站开得多的就nodequery.com和一些博客。

另外,obfs=tls, obfs-host=www.amazon.com,加密是aes-128-gcm, DNS远程转发,地址209.244.0.3或8.8.8.8.

在server的config.json 里面加上 "nameserver":"8.8.8.8"
可以解决unable to resolve *的问题,至少对我是有用的

至于connection reset,这个大概是网络本身问题或者gfw吧

@terrytw 谢谢。我加上试试。

加上很有效

Was this page helpful?
0 / 5 - 0 ratings