simple-obfs failed to handshake about simple-obfs HOT 7 CLOSED

升级obfs0.0.2之后变成了这样
2017-01-17 20:44:28 INFO: plugin "obfs-server" enabled
2017-01-17 20:44:28 INFO: initializing ciphers... chacha20
2017-01-17 20:44:28 INFO: tcp port reuse enabled
2017-01-17 20:44:28 INFO: tcp server listening at 127.0.0.1:51739
2017-01-17 20:44:28 INFO: running from root user
2017-01-17 20:44:28 [simple-obfs] INFO: tcp port reuse enabled
2017-01-17 20:44:28 [simple-obfs] INFO: listening at xxx.xxx.xxx.xxx:443
2017-01-17 20:44:28 [simple-obfs] INFO: running from root user
2017-01-17 20:44:30 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected
2017-01-17 20:44:30 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected
2017-01-17 20:44:31 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected
2017-01-17 20:44:31 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected
2017-01-17 20:44:32 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected
2017-01-17 20:44:32 [simple-obfs] ERROR: getpeername: Transport endpoint is not connected

from simple-obfs.

same here

from simple-obfs.

请尝试用最新版 shadowsocks-libev 配合使用

from simple-obfs.

same

from simple-obfs.

same issue as I reported in shadowsocks-android:
shadowsocks/shadowsocks-android#1155

the problem is in the plugin mode with shadowsocks-libev it is always listening to 127.0.0.1 but not the public server ip. We need a parameter in the JSON file (/etc/shadowsocks-libev/config.json) to control this. I tried "server", "server_host", "local_address", but none of them worked. Any suggestion? Or maybe a new commit is required to enable this feature?

Thanks and Regards,
Ricky

from simple-obfs.

same

from simple-obfs.

The same. shadowsocks-libev 3.0.5 simple-obfs 0.0.3
127.0.0.1 failed to handshake.
Have tried tls and http.

from simple-obfs.