You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have asked a question about this on Serverfault, but as I talk about your software, I wanted to let you the chance to answer the question by yourself if you can.
I also doubt that this can be fixed in Etherpad, but at least I wanted to let you know...
Imo this can happen if you have conflicting IPv4 and IPv6 priorities and your name server (if you don't hard code IP addresses in nginx) returns addresses for both families but node is listening on only one of them. So I would start debugging with tcpdump.
I have asked a question about this on Serverfault, but as I talk about your software, I wanted to let you the chance to answer the question by yourself if you can.
I also doubt that this can be fixed in Etherpad, but at least I wanted to let you know...
The full description is here: https://serverfault.com/questions/778814/websocket-proxy-with-nginx-error-about-post-request-in-server-log-but-works-in
So in short:
Connection refused
)In my view this is a very strange behaviour...
If you have no idea about why this might happen, you can of course close this issue.
The text was updated successfully, but these errors were encountered: