Settings

Inspect server ports and find which WebSocket ports are available to your devices.

This server

Bound port (PORT)

…

WS TCP port

disabled

ℹ
On Railway the bound port is exposed publicly as 443 (wss/https). Devices should connect to wss://<your-domain>/ws on port 443 — not the internal bound port.

Port Configuration

Configure WebSocket ports for your IoT devices

Active Ports

:3000Non-TLS (ws://)

ws://biorganize.xyz:3000 - Local/internal devices

:9000TLS (wss://)

wss://biorganize.xyz:9000 - External/production devices

Manual SSH Setup

Or copy & paste this command directly into your DigitalOcean droplet SSH terminal:

curl -fsSL https://raw.githubusercontent.com/cyberalphatech/v0-websocket-iot-protocol/main/scripts/setup-digitalocean.sh | bash -s -- --domain biorganize.xyz --email admin@biorganize.xyz PORT_NON-TLS=3000 PORT_TLS=9000

Port watch — incoming connections

Reconnecting…

Real-time feed of every WebSocket connection hitting this server — opens, inbound frames, device registrations, and disconnects. Point a device or the simulator at /ws and watch it appear here.

Connecting to live feed…

Showing the most recent 500 entries. The feed uses the same Server-Sent Events channel as the dashboard.

Find available WebSocket ports

Probes each port on the target host with a TCP connection. "Open" means the port is reachable and accepting connections — a candidate for device WebSocket traffic.

Note: External sites can only reach ports 80, 443, or custom TCP proxies. Port 3000 is only for local connections.

Tip: Port 3000 is internal only. Use 443 for production (TLS) or 8080 for plain WebSocket via Railway TCP proxy.