WebSocket-Sharp doesn't respond to public IP address

Question

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: ....

this [information](https://github.com/sta/websocket-sharp/issues/134) may be useful — gowridev, Oct 20 '20 at 07:09
Please make sure the ports are 10000% open! use an online port checker to see if they are open! — satyamedh, Oct 22 '20 at 18:11
@RobotRock: What is the output of the F12 debugger in your browser? Do you test this locally on your computer or on a server? Do you have a firewall active ? Double check port accessibility by listening with e.g. netcat. — sneusse, Oct 23 '20 at 12:21

RobotRock · Accepted Answer · 2020-10-24T20:10:07.850

0

The problem resides in the HttpServer provided with WebsScketSharp. The pure websocket variant (WebSocketServer.cs), instead of the HttpServer option with Get functionality, has an option to set AllowForwardedRequest to true so will be reachable from non localhost addresses. The HttpServer class doesn't support this. It is partially a solution as I gave up regular GET functionality, but thats fine by me.

edited Oct 24 '20 at 20:10

answered Oct 24 '20 at 20:04

RobotRock

4,211
6
46
86

score -1 · Answer 2 · answered Oct 23 '20 at 19:00

Ok, assuming your server with the public Ip addres is Linux:

Check what ports are listening and what program are listening in those

netstat -tulpn

Check your Firewall rules both in the provider and in the Server

sudo ufw status

See if connections are getting to your Server

sudo tcpdump

You can filter for the port of for origin Ip (if you use a proxy that will be different Ip).

sudo tcpdump | grep "80\|123.45.67.89"

That's the only way to see if the packets are getting into the server.

Let me know if you use Docker as thinks work a bit different.

You can create a tunnel and try like if it was local

ssh -L 80:123.45.67.89:80 ubuntu@yourserver.com

Cheers

WebSocket-Sharp doesn't respond to public IP address

2 Answers2