Brother QL bridge
Relays print jobs from browsers to Wi-Fi label printers. Jobs are rasterised in the browser; this page only decides who may print and to what.
Sign in
The admin token is set with ADMIN_TOKEN, or printed to the container log on first start.
Connecting a page
A page connects to the WebSocket endpoint below with a client token. From an HTTPS page the bridge must be reached over wss:// (a reverse proxy with TLS, or TLS_CERT_FILE/TLS_KEY_FILE), or served from localhost.
WebSocket endpoint:
Recent prints
No prints yet.
| When | Printer | Client | Labels | Size | Outcome | Faults |
|---|
The last few jobs, newest first. Client is the token's name and, after the dot, what the client called itself — a kiosk's name — if it said. Labels is what the client reported printing, or the pages it announced if it did not report; a tick means the printer itself confirmed them. Faults counts status packets with an error flag seen during the job. The page refreshes this every few seconds.
Client tokens
A token is shown once, when it is created. Revoking it disconnects nothing in flight but refuses the next connection.
| Name | Token | Created | Last used |
|---|
Printers
Each printer is reached at its host on port 9100. Status mode says how the bridge reads the printer's status: snmp for a QL-810W, QL-820NWB or QL-1110NWB (they do not answer status requests on port 9100), tcp for a printer known to answer there, none for fire-and-forget.
| Name | Address | Model | Status mode | State | Jobs | Labels | Faults |
|---|
Simulated printer
For debugging a page without a printer to hand. While it is enabled, Simulated QL-810W is listed to every client like a registered printer: it takes jobs, answers status the way a QL-810W does over SNMP, and keeps the last label it was sent. The switches are the faults a real printer has on a busy day; how a page recovers from each is what this is for. Disable it before anyone prints for real.
Last label
When something goes wrong
The bundle holds the bridge's configuration (without secrets), its printers and their counters, the recent prints, and the last couple of thousand log records including every frame and status packet — enough to diagnose a problem without reproducing it. Attach it to a bug report.