shadowsocks-libev icon indicating copy to clipboard operation
shadowsocks-libev copied to clipboard

How to fix error log 'remote recv: Connection reset by peer' and 'getpeername: Transport endpoint is not connected'?

Open SuperH-0630 opened this issue 2 years ago • 1 comments

What version of shadowsocks-libev are you using?

v3.3.5 (Installed by apt)

What operating system are you using?

Ubuntu 22.04.1 LTS

What did you do?

shadowsocks-libev as server. qv2ray as client. But there are some error log. Everything works fine when the service is started, the error log appears a minute after the client connects, but the proxy actually works.

What did you expect to see?

Not error log.

What did you see instead?

'remote recv: Connection reset by peer' and 'getpeername: Transport endpoint is not connected'

My shadowsocks log:

Aug 31 12:19:01 songzh-frp ss-server[144500]:  2022-08-31 12:19:01 INFO: using tcp fast open
Aug 31 12:19:01 songzh-frp ss-server[144500]:  2022-08-31 12:19:01 INFO: UDP relay enabled
Aug 31 12:19:01 songzh-frp ss-server[144500]:  2022-08-31 12:19:01 INFO: initializing ciphers... aes-256-gcm
Aug 31 12:19:01 songzh-frp ss-server[144500]:  2022-08-31 12:19:01 INFO: using nameserver: 8.8.8.8
Aug 31 12:19:01 songzh-frp ss-server[144500]:  2022-08-31 12:19:01 INFO: tcp server listening at 0.0.0.0:8395
Aug 31 12:19:01 songzh-frp ss-server[144500]:  2022-08-31 12:19:01 INFO: udp server listening at 0.0.0.0:8395
Aug 31 12:20:32 songzh-frp ss-server[144500]:  2022-08-31 12:20:32 ERROR: fast_open_connect: Network is unreachable
Aug 31 12:20:32 songzh-frp ss-server[144500]:  2022-08-31 12:20:32 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:11 songzh-frp ss-server[144500]:  2022-08-31 12:21:11 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:11 songzh-frp ss-server[144500]: message repeated 9 times: [  2022-08-31 12:21:11 ERROR: getpeername: Transport endpoint is not connected]
Aug 31 12:21:13 songzh-frp ss-server[144500]:  2022-08-31 12:21:13 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:13 songzh-frp ss-server[144500]: message repeated 3 times: [  2022-08-31 12:21:13 ERROR: getpeername: Transport endpoint is not connected]
Aug 31 12:21:15 songzh-frp ss-server[144500]:  2022-08-31 12:21:15 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:15 songzh-frp ss-server[144500]:  2022-08-31 12:21:15 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:17 songzh-frp ss-server[144500]:  2022-08-31 12:21:17 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:17 songzh-frp ss-server[144500]: message repeated 3 times: [  2022-08-31 12:21:17 ERROR: getpeername: Transport endpoint is not connected]
Aug 31 12:21:22 songzh-frp ss-server[144500]:  2022-08-31 12:21:22 ERROR: server recv: Connection reset by peer
Aug 31 12:21:22 songzh-frp ss-server[144500]: message repeated 8 times: [  2022-08-31 12:21:22 ERROR: server recv: Connection reset by peer]
Aug 31 12:21:23 songzh-frp ss-server[144500]:  2022-08-31 12:21:23 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:23 songzh-frp ss-server[144500]: message repeated 9 times: [  2022-08-31 12:21:23 ERROR: getpeername: Transport endpoint is not connected]
Aug 31 12:21:25 songzh-frp ss-server[144500]:  2022-08-31 12:21:25 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:25 songzh-frp ss-server[144500]: message repeated 7 times: [  2022-08-31 12:21:25 ERROR: getpeername: Transport endpoint is not connected]
Aug 31 12:21:30 songzh-frp ss-server[144500]:  2022-08-31 12:21:30 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:30 songzh-frp ss-server[144500]: message repeated 3 times: [  2022-08-31 12:21:30 ERROR: getpeername: Transport endpoint is not connected]
Aug 31 12:21:32 songzh-frp ss-server[144500]:  2022-08-31 12:21:32 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:32 songzh-frp ss-server[144500]: message repeated 5 times: [  2022-08-31 12:21:32 ERROR: getpeername: Transport endpoint is not connected]
Aug 31 12:21:34 songzh-frp ss-server[144500]:  2022-08-31 12:21:34 ERROR: getpeername: Transport endpoint is not connected
Aug 31 12:21:34 songzh-frp ss-server[144500]: message repeated 9 times: [  2022-08-31 12:21:34 ERROR: getpeername: Transport endpoint is not connected]

My client(qv2ray) log:

2022/08/31 12:21:13 [Warning] [3671756815] proxy/http: failed to read response from 91.108.56.105:80 > io: read/write on closed pipe
2022/08/31 12:21:13 [Warning] [3671756815] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:8889->127.0.0.1:54157: wsasend: An established connection was aborted by the software in your host machine.
2022/08/31 12:21:13 [Warning] [3298894028] proxy/http: failed to read response from 91.108.56.105:80 > io: read/write on closed pipe
2022/08/31 12:21:13 [Warning] [3298894028] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:8889->127.0.0.1:54159: wsasend: An established connection was aborted by the software in your host machine.

2022/08/31 12:21:15 [Warning] [1292743591] proxy/http: failed to read response from 91.108.56.110:80 > io: read/write on closed pipe
2022/08/31 12:21:15 [Warning] [1292743591] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:8889->127.0.0.1:54164: wsasend: An established connection was aborted by the software in your host machine.

2022/08/31 12:21:17 [Warning] [4198628810] proxy/http: failed to read response from 91.108.56.105:80 > io: read/write on closed pipe
2022/08/31 12:21:17 [Warning] [4198628810] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:8889->127.0.0.1:54169: wsasend: An established connection was aborted by the software in your host machine.
2022/08/31 12:21:17 [Warning] [652179474] proxy/http: failed to read response from 91.108.56.105:80 > io: read/write on closed pipe
2022/08/31 12:21:17 [Warning] [652179474] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:8889->127.0.0.1:54172: wsasend: An established connection was aborted by the software in your host machine.

What is your config in detail (with all sensitive info masked)?

{
    "server": "0.0.0.0",
    "server_port":8395,
    "local_port":1080,
    "mode":"tcp_and_udp",
    "password":"my-passwd",
    "timeout":86400,
    "method": "aes-256-gcm",
    "fast_open" :true,
    "nameserver": "8.8.8.8"
}

SuperH-0630 avatar Aug 31 '22 04:08 SuperH-0630

The same "ERROR: server recv: Connection reset by peer". Only 2 seconds successful connection

AlfredMoore avatar Oct 12 '22 00:10 AlfredMoore