• webv4 MQTT pages (node spy) fail to connect in Firefox when the broker

    From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Saturday, November 21, 2026 10:16:36
    open https://gitlab.synchro.net/main/sbbs/-/work_items/1378

    Reported by nelgin in the Synchronet Sysops sub-board (DOVE-Net, 2026-11-21, "Firefox is pissing me off!"): the webv4 node spy stopped connecting in Firefox. His broker is the stock mosquitto package on Ubuntu 24.04.

    ## Cause

    Firefox opens WebSockets over HTTP/2 (RFC 8441 Extended CONNECT) when the server negotiates `h2`. mosquitto 2.0.x takes its WebSocket listener from libwebsockets, and distro builds of libwebsockets have HTTP/2 enabled, so the `wss://` listener negotiates HTTP/2 and the WebSocket upgrade then fails. Chrome uses HTTP/1.1 for WebSockets and is unaffected, so the page works in one browser and not the other.

    This is a Firefox/libwebsockets/mosquitto interaction, not a Synchronet defect:

    - https://bugzilla.mozilla.org/show_bug.cgi?id=1807474 (mosquitto 2.0.15 + libwebsockets 4.3.2; refers to eclipse/mosquitto#1211)
    - https://bugzilla.mozilla.org/show_bug.cgi?id=1815545
    - https://support.mozilla.org/en-US/questions/1324001

    Only `wss://` is affected (HTTP/2 is negotiated through TLS ALPN), which is what `webv4/root/js/mqtt.js` uses whenever the page itself is served over https.

    ## Workarounds

    - Sysop, broker side: terminate TLS in front of mosquitto with something that doesn't offer `h2` (nelgin used stunnel from the public wss port to a localhost ws/wss listener; HAProxy forwarding HTTP/1.1 also reported to work), or use a libwebsockets built without HTTP/2.
    - User, browser side: `about:config` → `network.http.http2.websockets` = `false`.

    ## Proposed changes

    1. `webv4/components/mqtt.xjs`: the `mqtt-wss-reconnecting-message` list of "common causes" doesn't mention this one. Add an entry (Firefox + a broker that negotiates HTTP/2 on its WebSocket listener), with the workarounds above or a link to the wiki.
    2. Wiki: document the problem and the stunnel setup on the MQTT / webv4 pages (nelgin offered to write this up).

    ## Open question

    nelgin also reported fTelnet failing to connect. fTelnet connects to Synchronet's own WebSocket services, not to mosquitto, and I found no ALPN/HTTP/2 support in the Synchronet servers, so those should always be reached over HTTP/1.1. That failure probably has a different cause, or there is a proxy in front of the WebSocket service port on his system. Needs details from nelgin.

    — *Authored by Claude (Claude Code), on behalf of @rswindell*
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)