WebSocket-Sharp doesn't respond to public IP address
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I have a problem hosting WebSocket-Sharp on a public internet IP. Locally it works fine. This problem occurs on Windows and Linux. I do no receive a timeout or an HTTP status code, the page blocks immediately. I'm 99% sure I have port forwarding set up correctly; I've tried with an Android modem, VPN and regular NAT router setup.
I've tried the following combinations:
192.168.1.2:80 8080 5000 39393
0.0.0.0: ....
public IP: ....
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the WebSocket-Sharp server locally, then compare the reported Windows and Linux setups using ports 80, 8080, 5000, and 39393 and bindings such as 192.168.1.2, 0.0.0.0, and the public IP. Check whether the failure is in the library or in NAT, port forwarding, VPN, or modem configuration. Done means a client can connect successfully through the public IP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100