LABERTY Help Center Contact support Log in

The bridge shows 401 or 403

What "LABERTY_TOKEN was rejected (401)" and "Laberty refused this key (403)" mean, and how to fix each one.

The bridge's log (docker logs laberty-bridge, or the container's Log in Synology Container Manager) says why Laberty turned it away.

401: the key was rejected

The log says:

LABERTY_TOKEN was rejected (401). It may have been revoked -- download your bridge again from Laberty under Print bridge.

Laberty doesn't recognise the key. Usually one of these:

  • The key was revoked. On Admin → API keys it shows "Revoked".
  • The key was pasted wrong. It must be lbk_ followed by 40 characters, with no spaces. In a .env file, don't put quotes around it.
  • The variable name is wrong. It must be exactly LABERTY_TOKEN.
  • The account isn't active any more. Contact support.

Fix it with a new key

  1. In Laberty, go to Admin → Print bridge and press Download for your kind of bridge. The new download has a new key inside.
  2. Put the new key in place:
    • Docker: unzip the new download over the old folder (or copy just its bridge.env), then run docker compose up -d --build in that folder.
    • Synology: stop the project, upload the new bridge.env into the project's folder, then build and start it again.
    • Windows: run Install-Laberty-Bridge.cmd from the new download.
  3. Check the log shows connected to https://laberty.app — waiting for print jobs.
  4. On Admin → API keys, revoke the old key if it's still listed as active.

On Home, you can have three keys at once. If Laberty says they're all in use, revoke one you no longer need first.

403: Laberty refused the key

The log says Laberty refused this key (403): followed by the reason.

The reason saysWhat it meansFix
This is a "Printing" key, which cannot call /api/agent/jobs… (or "Full access")The bridge was given an app key instead of a bridge keyDownload your bridge again from Admin → Print bridge: it comes with a bridge key. A bridge key is the safest choice: it can't do anything else
The print bridge needs a paid plan. See Billing.The account is on Free, or its subscription endedStart or renew Home or Business on Admin → Billing

A Full access key does work for the bridge on Business, but don't use one: if it leaks from the bridge machine, it can do far more than print. See API keys explained.

Other errors in the log

The log saysWhat it means
poll error: fetch failed (retrying in 5s)The bridge machine can't reach the internet, or can't look up laberty.app. Check its network. The bridge keeps retrying on its own
poll error: /agent/jobs: HTTP 500 (retrying in 5s)A problem on Laberty's side. The bridge keeps retrying. If it lasts more than a few minutes, contact support
LABERTY_URL and LABERTY_TOKEN are required.The container started without its settings. Add both and start it again
LABERTY_URL must start with http:// or https://Use https://laberty.app exactly

For everything else, see Nothing printed.

Still stuck?

Contact support and tell us what you tried. We reply by email, usually within 1–2 business days.