Shadowsocksx-ng: 服务器端升级shadowsocks-libev为最新的3.2.0版本后，MAC版Shadowsocks-NG开启之后不能科学上网

[siriusfinex]

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]

ss-local.log

Please upload the ss-local.log file here the file is in ~/Library/Logs
1) Open 'Advanced Settings -> enable Verbose Mode'
2) Continue run Shadowsocksx-NG for 5 minutes
3) Upload the ~/Library/Logs/ss-local.log here (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.

[siriusfinex]

问题解决了，我电脑的问题。

[vincenthou2016]

楼上怎么解决的？我的也是最新不能用了。

[oynix]

楼上的楼上怎么解决的？我的也不能了 我是Mac

[zhouxl]

楼上的楼上怎么解决的？我的也不能了 我是Mac

[oynix]

至今未解决，我提了一个新问题 #830 @zhouxl

[iROCKBUNNY]

@siriusfinex 请问您是怎么解决的？

● shadowsocks-libev.service - Shadowsocks-libev Default Server Service
   Loaded: loaded (/lib/systemd/system/shadowsocks-libev.service; disabled; vendor preset: enabled)
   Active: active (running) since Mon 2018-06-04 02:28:24 CST; 1min 50s ago
     Docs: man:shadowsocks-libev(8)
 Main PID: 3989 (ss-server)
   CGroup: /system.slice/shadowsocks-libev.service
           └─3989 /usr/bin/ss-server -c /etc/shadowsocks-libev/config.json -u

Jun 04 02:29:14 MY_HOST ss-server[3989]:  2018-06-04 02:29:14 ERROR: connect: Invalid argument
Jun 04 02:29:14 MY_HOST ss-server[3989]:  2018-06-04 02:29:14 ERROR: connect: Invalid argument
Jun 04 02:29:14 MY_HOST ss-server[3989]:  2018-06-04 02:29:14 ERROR: connect: Invalid argument
Jun 04 02:29:15 MY_HOST ss-server[3989]:  2018-06-04 02:29:15 ERROR: connect: Invalid argument
Jun 04 02:29:16 MY_HOST ss-server[3989]:  2018-06-04 02:29:16 ERROR: connect: Invalid argument
Jun 04 02:29:16 MY_HOST ss-server[3989]:  2018-06-04 02:29:16 ERROR: connect: Invalid argument
Jun 04 02:29:16 MY_HOST ss-server[3989]:  2018-06-04 02:29:16 ERROR: connect: Invalid argument
Jun 04 02:29:16 MY_HOST ss-server[3989]:  2018-06-04 02:29:16 ERROR: connect: Invalid argument
Jun 04 02:29:17 MY_HOST ss-server[3989]:  2018-06-04 02:29:17 ERROR: connect: Invalid argument
Jun 04 02:30:10 MY_HOST ss-server[3989]:  2018-06-04 02:30:10 ERROR: connect: Invalid argument

[iROCKBUNNY]

@qiuyuzhou Hi! This issue is quite critical. Could you please show up to make a quick patch for this?

[qiuyuzhou]

I have found the version 3.1 of shadowsocks-libev is too sensitive to block the ip which has failed connection from.
You could try to add your ip or all ip 0.0.0.0/0 in white list by --acl option on server side.

[iROCKBUNNY]

Thanks for you reply! @qiuyuzhou
3.1.3 worked. However, after upgrading to 3.2.0, shadowsocks-libev has kept raising those annoying Invalid argument errors. My server is using Ubuntu 16.04 LTS with no ufw configured. Could you please show me how to add my ip or all ip 0.0.0.0/0 in white list by --acl option on server side specifically?

[iROCKBUNNY]

@qiuyuzhou Hi! I've solved the issue. It turns out that shadowsocks-libev has upgraded its config.json file since 3.2.0. I will open another issue to address the work-around there.

[iROCKBUNNY]

Hi @vincenthou2016 @oynix @zhouxl @qiuyuzhou , the work-around is here #831 , which works perfect for me.

[zhouyong1d1]

@iROCKBUNNY 楼主，我这个问题很大，一直无法解决，你可以给我点指导吗，邮箱[email protected]

[iROCKBUNNY]

@zhouyong1d1 Sorry, I am not capable of fixing more specific issues other than this.

[zhouyong1d1]

@iROCKBUNNY 我能加你qq吗

[yangfeicheung]

試試這個版本哦，可以連接shadowsocks-libev 3.2版本的：

https://github.com/yangfeicheung/Shadowsocks-X/releases

[Zhang-Jack]

after upgraded to ss version 3.2.0, you need to
remove line
"local_address":"127.0.0.1",
in /etc/shadowsocks/config.json
then the ss will work
I don't know why but just this can establish the connection