Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nginx claims the websocket POST requests fail, but this seems to be wrong #2992

Closed
rugk opened this issue May 24, 2016 · 3 comments
Closed

Comments

@rugk
Copy link
Contributor

rugk commented May 24, 2016

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:

  • Nginx reports that the POST & Websocket requests fail (Connection refused)
  • In my browser I can see these requests to be successful
  • Everything with Etherpad seems to work
  • There are no errors with Etherdraw, because it seems Etherdraw does not use POST requests to Socket.io

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.

@webzwo0i
Copy link
Member

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.

@rugk
Copy link
Contributor Author

rugk commented May 25, 2016

Thanks for the tip. I'll try it out.

@rugk rugk closed this as completed Jun 1, 2016
@rugk
Copy link
Contributor Author

rugk commented Jun 1, 2016

BTW: It worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants