-
Notifications
You must be signed in to change notification settings - Fork 374
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
Prebuilt version fails on tls handshake #534
Comments
EDIT: Although this allows to connect it doesn't seem to be the issue at all |
I've been doing some more tests and i've found out that building locally and using that build allows to connect without any error
|
I believe the issue here is related to the setup on your websocket host. |
Yes, it does connect to the official clusters. The weird thing is that I tested other ws clients like |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you'd like this issue to stay open please leave a comment indicating how this issue is affecting you. Thank you. |
Better create a ticket on Pusher support, linking this issue there. Otherwise they won't look into issues. |
Thanks for reporting this. We supply our client libraries for connecting to the official Pusher service and do not guarantee support for custom websocket hosts. We are not able to provide a resolution to this issue for this reason. |
I'm trying to connect to a custom host from Node.js but i always get unavailable state
I found out that the client automatically closes the TCP session as soon as the TLS handshake finishes
No error is thrown on client and there are no logs at all on the server,
Here the wireshark capture of the tcp handshake and immediate disconnection (the ip ending in 40 corresponds to my device, being the leftmost column the destination address of the packet)
I've been able to connect to the same ws endpoint with the same uri using
pusher-client
andws
npm packages.The code i'm using right now:
Using
Client
Server
The text was updated successfully, but these errors were encountered: