503 GET socket hang up with Websocket
See original GitHub issueHi,
I manage to proxy websocket with nginx but with CHP, it doesn’t work. I also try with http-proxy and I always obtain the same result.
I have a qemu VM with websocket option on 10.22.9.172:6740
. So on my proxy (10.22.9.119
), I use the following command : configurable-http-proxy --default-target=ws://10.22.9.172:6740 --port 81
On Firefox, I use vnc_auto.html file, from novnc projet with the following url : http://194.X.X.X:Y/vnc_auto.html?host=10.22.9.119&port=81
Thanks for you help
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
NodeJS - What does "socket hang up" actually mean?
It means that socket does not send connection end event within the timeout period. If you are getting the request for cheerio via...
Read more >[ConfigProxy] error: 503 socket hang up - JupyterHub
Installed jupyterhub in a docker container and trying to run in cloud. but i am getting this error.
Read more >jupyterhub/jupyterhub - Gitter
socket hangup is not generally a problem on its own - it only means that an endpoint (e.g. the Hub or single-user server)...
Read more >502 Bad Gateway - Socket hang up | Apigee Edge
The error code [socket hang up][ECONNRESET] indicates that the target server has closed the connection with Edge Microgateway. This can be ...
Read more >Troubleshooting connection issues | Socket.IO
anything between the user and the Socket. ... the WebSocket connection; the first HTTP long-polling request, which is closed once the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think you can close but, even if the http headers are case-insentitive, I think it will be better to avoid modify the header. But this modification is from http-proxy and so on, in CHP.
@krakydark and @minrk, Is this issue ready to close? It seems that this is out of the scope of CHP. Thanks.