Server addresses and connection environments
A web page URL and its messaging server URL are separate. A local workbench can serve HTTP on 8080, WebSocket on 7777, and Arduino TCP on 55488. A ready page does not prove the message server is running.
| Environment | Typical connection |
|---|---|
| Public HTTPS page | Public wss:// endpoint |
| Local development on the same computer | http://localhost:8080 with ws://localhost:7777 |
| Arduino on the LAN | Computer's LAN IP with TCP port 55488 |
| Phone on the LAN | Reachable computer LAN address and matching WebSocket host |
localhost always names the device running the client. It cannot name your PC from an Arduino or phone. The workbench's default local UI binding is 127.0.0.1; configure an appropriate LAN binding before expecting another device to reach it. Also check firewall rules and the server's listening interface.
HTTPS and WebSocket
Use HTTPS with WSS for public deployment. Browsers can block insecure WS from an HTTPS page as mixed content. Private-network and localhost access can additionally require browser permissions; behavior depends on browser and origin. Prefer a local development page for local WS experiments.
Changing a URL from ws:// to wss:// does not add TLS to a plain server. Configure TLS or a reverse proxy and a valid certificate. HTTP-to-HTTPS upgrades and HSTS may change the page origin; use a valid WSS endpoint or the intended localhost development origin rather than bypassing browser checks.
Compare the complete host, port, and WebSocket path on both clients. The public service URLs are listed in services. Home channels further depend on the server-observed network group; they are not authentication boundaries.