Shadowsocks doesn't work after migration
Linode
Linode Staff
There is a problem on my linode after I clicked the free storage plus(A kind of message like AD at the linode's main page). After I upgraded my storage(20 to 25GB), my shadowsocks started to break down. I can connect to my server but can't get access to the Internet. I have two Linode accounts. Two of the shadowsocks are broke down just right after the disk migration. I don't think the disk migration can cause GFW to detect or ban my IP address (cause migration didn't change my Linode's IP).
root@localhost:~# mtr -rwbzc100 $IP
Start: Mon Jun 4 09:27:59 2018
HOST: localhost Loss% Snt Last Avg Best Wrst StDev
1. AS63949 139.162.65.2 0.0% 100 0.8 0.9 0.4 18.4 1.9
2. AS63949 139.162.64.26 0.0% 100 4.6 3.8 0.3 32.8 5.8
3. AS2914 ae-15.r01.tokyjp08.jp.bb.gin.ntt.net (192.80.17.177) 0.0% 100 0.8 0.8 0.7 1.1 0.0
4. AS2914 ae-2.a00.tokyjp03.jp.bb.gin.ntt.net (129.250.5.55) 0.0% 100 1.0 3.2 0.8 36.0 5.3
5. AS2914 ae-0.pacnet-telstra.tokyjp03.jp.bb.gin.ntt.net (61.120.145.62) 0.0% 100 80.9 81.5 80.8 125.0 4.5
6. AS10026 xe-0-0-0.0.gw2.hkg9.10026.telstraglobal.net (61.14.158.67) 0.0% 100 75.6 76.2 75.5 92.8 3.0
7. AS4637 1002661.8.59.38 0.0% 100 76.9 78.0 76.8 117.9
5.5
8. AS4538 101.4.117.149 0.0% 100 244.7 260.2 214.3 308.3 25.8
9. AS4538 101.4.118.25 2.0% 100 242.4 260.8 213.4 301.7 25.4
10. AS4538 101.4.116.77 0.0% 100 239.0 261.7 209.6 369.5 28.8
11. AS4538 101.4.117.246 1.0% 100 248.5 275.2 218.7 374.3 33.8
12. AS4538 202.112.30.34 1.0% 100 245.7 268.4 217.6 307.9 25.0
13. AS??? ???
Please help me, thank you!
1 Reply
If shadowsocks isn't functioning following a migration, which requires a reboot, it's possible that your configuration, or your firewall configuration, failed to persist through the reboot.
I recommend revisiting your IP tables and shadowsock configurations and then restarting the service. Here is a helpful link to shadowsocks.json Breakdown that would be beneficial to check.
You can check your firewall rules with the following:
iptables-save
Feel free to share your output, configurations or any errors here to get extra eyes on the issue.