Unable to connect to the remote server - wss

Open
#43 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, gcp, node.js
Domain
networking

Research direction

Start by reproducing the connection to wss://scramblegram.bluemsoftware.com with the NativeWebSocket client and compare it with the working echo.websocket.org connection and websocket.org client. Inspect the library's connection and TLS/error-reporting entry points; done means identifying the server-specific incompatibility and documenting or fixing the client behavior with a reproducible test.

Written by the indexing model from the issue text.

Description

I have created a WebSocket server in NodeJs and hosted it on GCP. The URL for the server is wss://scramblegram.bluemsoftware.com

I created a client using this library

Here is my issue

If I connect to wss://scramblegram.bluemsoftware.com using this library I get "Unable to connect to the remote server"

If I connect to wss://scramblegram.bluemsoftware.com using https://www.websocket.org/echo.html it works perfectly.

If I connect to wss://echo.websocket.org using this library it works perfectly.

can someone explain what is going on and how I can debug and solve this? It makes no sense

Dominant language
C#
Stars
1.7k
Forks
206
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from endel/NativeWebSocket

All issues in endel/NativeWebSocket

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.