riobard/go-shadowsocks2

Error from my ss service, how to solve it

wpecker opened this issue · 1 comments

Open youtube, the following error occurs in the gap:

2018/11/14 02:19:16 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 02:19:16 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 04:28:50 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 04:46:52 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 06:46:12 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 06:46:13 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 06:46:13 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 10:54:29 tcp.go:116: failed to get target address: cipher: message authentication failed


After using it for one day, the error occurred is as follows:

2018/11/14 00:50:17 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 01:56:39 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:39 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:39 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:39 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:39 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:47 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:47 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:47 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:47 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 01:56:47 tcp.go:122: failed to connect to target: dial tcp 43.224.184.234:443: connect: connection timed out
2018/11/14 02:19:12 tcp.go:116: failed to get target address: EOF
2018/11/14 02:19:16 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 02:19:16 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 02:26:07 tcp.go:134: relay error: read tcp 182.32.12.245:51884->104.237.191.1:443: read: connection reset by peer
2018/11/14 04:28:50 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 04:46:52 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 06:42:21 tcp.go:116: failed to get target address: read tcp 182.32.12.245:51884:51884:44051->218.68.218.136:52050: read: connection timed out
2018/11/14 06:46:12 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 06:46:13 tcp.go:116: failed to get target address: cipher: message authentication failed
2018/11/14 06:46:13 tcp.go:116: failed to get target address: cipher: message authentication failed

Either you have configuration errors (in which case it won't work for you), or someone is sending you invalid traffic (most likely some kind of replay attack). But you're using AEAD ciphers so you should be fine.