上不了网,是不是封了
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
System and Shadowsocksx-NG version: (please complete the following information):
- OS Version: [e.g. 10.13.1]
- Version [e.g. 22]
Diagnoisis file:
Please first upgrade to the latest version. Then export the diagnosis file and upload it to here.
ss-local.log
Please upload the ss-local.log file here the file is in ~/Library/Logs
- Open 'Advanced Settings -> enable Verbose Mode'
- Continue run
Shadowsocksx-NGfor 5 minutes - Upload the
~/Library/Logs/ss-local.loghere (with or without compress)
Application log
Open the Console.app and search Shadowsocksx-NG
Copy paste the log here
Crash Log
If the app crashes and pop up a crash log, please copy and paste here
Additional context Add any other context about the problem here.
这几天突然就上不了。portal 主页也上不去
我也是- -连github desktop都用不了= =
七十周年来临,自建和不强劲的机场都会被封,过去这段时间就好了
2个小时被封2个IP
之前买的个人账户线路都被封了……这咋办
机场应该给你的有订阅链接吧,更新订阅,不行你可以用这个链接注册下,用赠送的1元买试用套餐去你的机场看下http://sssru.pw/auth/register?code=hiQaqXxaLaNiryDyOMNgMF8QhiQB07tN
ss的特征是不是已经被完全掌握了。感觉现在封的特别精准
更新了版本好像还是不行。
诶!
推荐板瓦工的ss服务,被封自动换IP,https://justmysocks1.net/members/aff.php?aff=4601
推荐板瓦工的ss服务,被封自动换IP,https://justmysocks1.net/members/aff.php?aff=4601
我也换了这家机场,不过这两天还是不行了,能ping通但就是连不上,要不就是好不容易连上了,过一会就挂掉了。。。
推荐板瓦工的ss服务,被封自动换IP,https://justmysocks1.net/members/aff.php?aff=4601
我也换了这家机场,不过这两天还是不行了,�能ping通但就是连不上,要不就是好不容易连上了,过一会就挂掉了。。。
我一直可以,用了好久了,最近封的比较严,前两个地址都是可以的,win上我一直用的高可用模式。mac上好像确实有问题,有时候需要清一下DNS缓存或者重启电脑和ss
今天发现可以用了,开心
@jackwish Windows上可用? 我在Mac 客户端和 服务器端尝试了各种各样的改变(换client socket listen port, server ss port, encryption method), ,没啥用。基本5分钟自动屏蔽端口,同一个IP被屏蔽了三个左右的端口,IP就ping不了。 发一个IP封了前的log记录,ss的密码不重要了。
root@fourth:~# go-shadowsocks2 -s 'ss://AES-256-CFB:passwordleo@:52888' -verbose
2019/09/26 05:01:40 udp.go:135: listening UDP on :52888
2019/09/26 05:01:40 tcp.go:101: listening TCP on :52888
2019/09/26 05:02:10 tcp.go:128: proxy 27.18.252.180:10147 <-> www.google.com:443
2019/09/26 05:02:11 tcp.go:128: proxy 27.18.252.180:10146 <-> www.google.com:443
2019/09/26 05:02:12 tcp.go:128: proxy 27.18.252.180:10148 <-> www.google.com:443
2019/09/26 05:02:13 tcp.go:128: proxy 27.18.252.180:10149 <-> www.gstatic.com:443
2019/09/26 05:02:14 tcp.go:128: proxy 27.18.252.180:10151 <-> clients4.google.com:443
2019/09/26 05:02:59 tcp.go:128: proxy 27.18.252.180:10170 <-> id.google.com:443
2019/09/26 05:03:01 tcp.go:128: proxy 27.18.252.180:10171 <-> apis.google.com:443
2019/09/26 05:03:12 tcp.go:128: proxy 27.18.252.180:10177 <-> adservice.google.com:443
2019/09/26 05:03:17 tcp.go:128: proxy 27.18.252.180:10179 <-> adservice.google.com.ph:443
2019/09/26 05:03:18 tcp.go:128: proxy 27.18.252.180:10186 <-> www.googleapis.com:443
2019/09/26 05:03:18 tcp.go:128: proxy 27.18.252.180:10182 <-> s3.amazonaws.com:443
2019/09/26 05:03:19 tcp.go:128: proxy 27.18.252.180:10183 <-> assets-kasa-dev.s3.amazonaws.com:443
2019/09/26 05:03:26 tcp.go:128: proxy 27.18.252.180:10193 <-> www.google.com:443
2019/09/26 05:03:27 tcp.go:128: proxy 27.224.136.239:40602 <-> www.google.com:443
2019/09/26 05:03:31 tcp.go:116: failed to get target address: SOCKS error: 8
2019/09/26 05:03:53 tcp.go:128: proxy 27.18.252.180:10220 <-> www.googleapis.com:443
2019/09/26 05:05:13 tcp.go:128: proxy 27.18.252.180:10286 <-> clients1.google.com:443
2019/09/26 05:05:17 tcp.go:128: proxy 27.18.252.180:10287 <-> assets-kasa-dev.s3.amazonaws.com:443
2019/09/26 05:09:03 tcp.go:128: proxy 27.18.252.180:10472 <-> www.google.com:443
2019/09/26 05:09:03 tcp.go:128: proxy 27.18.252.180:10475 <-> apis.google.com:443
2019/09/26 05:09:03 tcp.go:128: proxy 27.18.252.180:10473 <-> id.google.com:443
2019/09/26 05:09:03 tcp.go:128: proxy 27.18.252.180:10474 <-> www.gstatic.com:443
2019/09/26 05:09:06 tcp.go:128: proxy 124.225.41.128:50984 <-> www.google.com:443
2019/09/26 05:09:09 tcp.go:116: failed to get target address: SOCKS error: 8
2019/09/26 05:09:31 tcp.go:128: proxy 27.18.252.180:10547 <-> adservice.google.com:443
2019/09/26 05:09:34 tcp.go:116: failed to get target address: unexpected EOF
2019/09/26 05:09:49 tcp.go:128: proxy 27.18.252.180:10563 <-> assets-kasa-dev.s3.amazonaws.com:443
2019/09/26 05:09:49 tcp.go:128: proxy 27.18.252.180:10562 <-> assets-kasa-dev.s3.amazonaws.com:443
Timeout, server syd not responding.
why ping me...
实在不行就换个节点:https://github.com/Luis-X/Blog/issues/1
更新了版本好像还是不行。
我也是- -连github desktop都用不了= =
ssr基本上已经都不能用了,还是推荐使用v2ray进行代理
上面的老哥 推荐的地址实测可用。 http://ssru5.xyz/auth/register?code=At6654m5kWOfXeNeyaHvgUWT05uQDDDK
ping 错人,本来是要ping 前一个帖子楼上的,用自动补全时没注意看, 抱歉。 DO, Vultr都用过,日本,新加坡,悉尼,美国,英国都用过,看来我这边的网抓的是非常的严。
ss流量已经被识别了,目前tor配合ss,可以规避。已经ping不通的结点,通过tor可连上了。 教程链接:https://www.imtrq.com/archives/738
我重写了大部分功能。https://github.com/jack80342/ShadowsocksX-NG-R