'Socket not connected' error behind reverse proxy

[fungs]

Hi,

I observed that, when running piping-server-rust behind HAProxy, I'm getting the following error after each (successful) transfer:

[ERROR piping_server] Failed to serve HTTP connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Socket not connected" })
[ERROR piping_server] Failed to serve HTTP connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Socket not connected" })

I'm not sure what this means, and if this might be related to the timeout parameters. However, I've set timeouts generously and the reverse proxy is running on the same local system as piping-server.

Any ideas?

[fungs]

Possibly related:

• TCP source: "Socket not connected" vectordotdev/vector#2731
• Socket not connected when behind proxy TotallyInformation/node-red-contrib-uibuilder#84

[nwtgck]

@fungs
Does HAProxy work with other HTTP server like nginx or nwtgck/pipng-server (not rust) instead of piping-server-rust?

[fungs]

@nwtgck I haven't tried piping-server instead of piping-server-rust, but HAProxy should work with any kind of HTTP server, it is one of the oldest reverse proxies around and part of many commercial cloud offerings. For me, the error and related issues are more likely pointing to the rust stack. Somehow the software loses the HTTP connection back to the reverse proxy. Then, HAProxy just terminates the connection after the configure timeout.

[nwtgck]

@fungs
Sorry. I missied "each (successful) transfer."

Does curl http://your-local-haproxy/version print the Piping Server version without errors?