Troubleshooting
The hub does not start
Section titled “The hub does not start”LABELYARD_SECRET_KEY must decode to exactly 32 bytes. Generate the key again withopenssl rand -base64 32 | tr '+/' '-_'.- A validation error about the log level.
LABELYARD_LOG_LEVELtakesDEBUG,INFO,WARNING,ERRORorCRITICAL, in capitals. - An unknown key in
.env. A.envkey with the hub’s prefix that matches no setting stops the start. Remove or rename it; the configuration reference lists every valid name.
I cannot sign in
Section titled “I cannot sign in”- “Sign in with an API key that has print or admin scope.” A
readkey cannot sign in. - The bootstrap key no longer works. It is rejected as soon as an admin key exists; sign in with that key, or create one in the container (see API keys).
- Sign-in works but the session is lost at once. The browser address differs from
LABELYARD_PUBLIC_URL, or the address ishttpwhile the public address ishttps. Open exactly the configured address.
Printers
Section titled “Printers”- No printers on the overview. Add them under Settings > Printers; printers are not configured through variables.
- The printer shows offline. Check from the Docker host:
nc -zv <printer-address> 9100, and SNMP as described under connecting printers. - A job stays in printing. The printer never reported the end of the job. Look at the printer: a cover may be open, or the tape ran out.
- Prints on a page printer are off by a few millimetres. Calibrate the tray (see connecting printers).
Live updates and webhooks
Section titled “Live updates and webhooks”- The status does not update without a reload. The proxy buffers the event stream; see the flush settings under reverse proxy.
- Webhooks answer 401. The
X-API-Keyheader does not matchLABELYARD_WEBHOOK_API_KEY. - Webhooks answer 503.
LABELYARD_WEBHOOK_API_KEYis not set.
Still stuck
Section titled “Still stuck”Search the existing issues or open a discussion. Include the version from the About page and the log lines around the problem; remove addresses and keys before posting.