Skip to content

Let mobile apps skip the login page (Auth Bypass)

How-toDeployrr v6.0+CurrentAuthenticationTraefikRemote access

Some mobile apps cannot show your login page. LunaSea and NZB360 are two examples. Auth Bypass lets such an app skip the login when it sends a secret key with each request. Everyone else still sees your login page.

This page shows how to set the key, add a bypass route to an app, and set up the mobile app. To limit an app to your LAN or VPN instead of skipping the login, see Allow only some IP addresses to reach an app.

  • Traefik Production is done and Traefik is running. See the Quick start if it is not.
  • You have a Plus or Pro license, all Prerequisites steps are done, and the Socket Proxy app is running. If something is missing, Deployrr shows a Requirements Not Met box that lists it.
  • The app has a file named app-NAME.yml in appdata/traefik3/rules/HOSTNAME/ inside your Docker folder. NAME is the app name and HOSTNAME is your server’s hostname. Deployrr creates this file when you use Traefikify.
  • The app has a login method set (for example Authelia or Basic HTTP Auth). If it has none, there is nothing to bypass. See Choose a login method.
  1. In Deployrr, go to Proxy > Traefik > Auth Bypass. Its description reads “Set Traefik Forward Auth Bypass Key”. It shows Set after you have saved a key.
  2. Read the Traefik Auth Bypass Key box and confirm that you want to proceed.
  3. In the Docker Environment Variables box, check the key. Deployrr suggests a random key of 16 letters and digits. You can use it as it is or type your own.
  4. Confirm. Deployrr saves the key in the .env file in your Docker folder.
  5. Wait for the Auth Bypass Key - Set box and close it.
  6. Check that Auth Bypass now shows Set in the menu. The success box can show even if you cancelled the key box.

To replace the key later, see Change the key.

Deployrr does not do this step for you, and the success box does not mention it.

  1. Open Traefik’s compose file in a text editor. It is compose/HOSTNAME/traefik.yml inside your Docker folder.

  2. Find this line in the environment list:

    # - TRAEFIK_AUTH_BYPASS_KEY
  3. Remove the # at the start so it reads like this. Keep the same indent. If the line already has no #, leave it.

    - TRAEFIK_AUTH_BYPASS_KEY
  4. Save the file.

  5. Recreate Traefik so it picks up the key:

    Terminal window
    dcrec traefik

    This uses a Deployrr alias. See Bash aliases.

Do step 5 again each time you change the key.

Traefikify does not ask about the bypass, and always creates a normal rules file. Add the bypass route to that file by hand.

  1. Open appdata/traefik3/rules/HOSTNAME/app-NAME.yml in a text editor.

  2. Find the app’s normal router. It is named NAME-rtr. Add this line under its rule: line, with the same indent:

    priority: 99

    Leave the rest of the normal router as it is.

  3. Add a second router under routers:, next to the first. Use the same indent as the first router.

    NAME-rtr-bypass:
    rule: "Host(`SUBDOMAIN.{{env "DOMAINNAME_1"}}`) && Header(`traefik-auth-bypass-key`, `{{env "TRAEFIK_AUTH_BYPASS_KEY"}}`)"
    priority: 100
    entryPoints:
    - websecure-external
    - websecure-internal
    middlewares:
    - chain-no-auth
    service: NAME-svc
    tls:
    certResolver: dns-cloudflare
    options: tls-opts@file
  4. Replace NAME with the app name from the file name. Replace SUBDOMAIN with the same subdomain the normal router uses.

  5. Make entryPoints match the normal router. If it lists only one, list only that one.

  6. Check that service: uses the same value as the normal router.

  7. Save the file. Traefik picks up changes in this folder on its own. You don’t need to restart it.

Don’t type your key into this file. The {{env "TRAEFIK_AUTH_BYPASS_KEY"}} part reads it from Traefik.

The higher priority (100 against 99) makes Traefik try the bypass route first. Requests without the right header fall through to the normal route and its login. To understand why this works, read UDMS part 28: Traefik conditional auth bypass (manual setup, background only; it puts rules files in a different folder than Deployrr v6, so follow the steps on this page).

LunaSea and NZB360 both set headers per service. Add the header to every service you connect, such as Sonarr, Radarr and SABnzbd. Each of those services also needs its own bypass route. See Add the bypass route to an app.

  1. In the mobile app, open the connection settings of one service:

    • LunaSea: in Settings > Configuration, open the module (for example Radarr). Its Connection Details have a Custom Headers setting. Choose Add Header, then Custom….
    • NZB360: open the settings of the service. Look for its custom headers setting.
  2. Set the header name (Header Key in LunaSea) to:

    traefik-auth-bypass-key
  3. Set the value (Header Value in LunaSea) to your key.

  4. Set the server address to the app’s normal address, for example https://SUBDOMAIN.YOUR_DOMAIN.

  5. Save, and repeat for the next service.

The labels in your app version can differ. LunaSea is no longer updated (its project was archived in April 2025), so it may stop working with newer versions of Sonarr, Radarr and similar apps.

Run these from a computer. Replace SUBDOMAIN.YOUR_DOMAIN with your app’s address and YOUR_BYPASS_KEY with your key.

  1. Request the app without the header:

    Terminal window
    curl -s -o /dev/null -w "%{http_code}\n" https://SUBDOMAIN.YOUR_DOMAIN

    You should get a redirect to your login page (such as 302) or 401.

  2. Request it with the header:

    Terminal window
    curl -s -o /dev/null -w "%{http_code}\n" -H "traefik-auth-bypass-key: YOUR_BYPASS_KEY" https://SUBDOMAIN.YOUR_DOMAIN

    You should get the app’s own response, such as 200, and no login redirect.

If both requests show the login redirect, check these:

  • The # is removed from the Traefik compose line, and you ran dcrec traefik after that.
  • The header name is spelled traefik-auth-bypass-key, in lowercase with hyphens.
  • The key in your request is the one you set in Auth Bypass.

Read the Traefik logs if the app does not load at all.

Change the key if it may have leaked: it showed in a screenshot or chat, a phone with the key was lost, or someone who had it should no longer get in. The old key keeps working until Traefik is recreated.

  1. Make a new random key on the server:

    Terminal window
    tr -cd '[:alnum:]' </dev/urandom | head -c 24; echo
  2. In Deployrr, go to Proxy > Traefik > Auth Bypass and confirm.

  3. The Docker Environment Variables box shows your current key. Replace it with the new one and confirm. Don’t leave the box empty. If you cancel the box, the old key stays.

  4. Recreate Traefik so it uses the new key:

    Terminal window
    dcrec traefik

    Your rules files don’t change. They read the key from Traefik.

  5. In each mobile app, change the traefik-auth-bypass-key header to the new key.

  6. Run the checks in Check it worked with the new key. Then run the second check with the old key. It should now show the login redirect.