failed to get target address: cipher: message authentication failed about go-shadowsocks2

[riobard]

Should be fixed by #79

[zQueal]

I also just experienced this. It seems to happen any time I try to launch the server instance with anything other than the ss:// url schema. For example;

go-shadowsocks2 -s :8001 -cipher AEAD_AES_128_GCM -key $PASSWORD -verbose

failed consistently with the related error above. But;

go-shadowsocks2 -s ss://AEAD_AES_128_GCM:$PASSWORD@:8001 -verbose

worked fine. I'm guessing this might have something to do with -key. I generated a key using go-shadowsocks2 -keygen 16 and added it to the $PASSWORD environment variable. So both times the string was called from the environment variable--but only failed when using -key.

[riobard]

Insufficient information to reproduce.

[chenyangguang]

./go-shadowsocks2 -s ss://AEAD_CHACHA20_POLY1305:my-pwd@:9999 -verbose
2017/11/26 09:26:32 listening UDP on :9999
2017/11/26 09:26:32 listening TCP on :9999

 ./go-shadowsocks2 -c ss://AEAD_CHACHA20_POLY1305:my-pwd@[my-ip]:9999 \
     -verbose -socks :1080 -u -udptun :8053=8.8.8.8:53,:8054=8.8.4.4:53 \
                              -tcptun :8053=8.8.8.8:53,:8054=8.8.4.4:53

appear:
2017/11/26 09:34:13 failed to get target address: SOCKS error: 7