-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Can't connect to HTPPS Nginx reverse proxy serving a Meteor app #380
Comments
Yaeah same here |
I got this same error and it seems to be happening cause my cert was expired (but using version 1.3.0). Maybe the same for you guys? |
@h3adache the latest version is 1.3.4 |
Hi @marci4 it doesn't throw the BufferOverflow anymore but it doesn't give the correct error. It simply disconnects. The error message is actually swallowed by an exception block that only calls The linked source above is different because integrated wss support was added. It's L 232/233 in the 1.3.4 code. Something is wrong when looking it up by the version tag. It shows it on L257 but when looking at the code in the 1.3.4 jar it's L233. The actual exception message is correct it seems: |
Hello @h3adache, well at least the error should be displayed and then disconnect. Opening a seperat issue for this! |
I'm trying to connect to my Meteor backend. When connecting via https, I sometimes get this BufferOverflowException:
When the overflow doesn't happen, I can't connect to the server anyways. I get this .CLOSED message:
{msg=closed, reason=, code=-1, remote=true}
I analyzed the handshake with Wireshark and got this: https://drive.google.com/file/d/0B9cfrkkW62eIWHlzY2oyU0k5cDA/view?usp=sharing
I see the client gets the certificate, but then it doesn't respond with the handshake continuation, it sends a Hello again, and therefore the server resets the connection. I believe this is why the overflow happens, when the timing is right, the client tries to read from an empty socket.
But I'm obviously grasping at straws here, any help would be greatly appreciated. I can contribute with code if somebody pushes me in the right direction.
This is (some relevant part) of my nginx config, but I really doubt it'll do any difference:
The text was updated successfully, but these errors were encountered: