Mobile App

traefik-manager-mobile is a React Native companion app for managing Traefik Manager from your phone.

Requires Traefik Manager v0.6.0 or higher

The mobile app authenticates via the API key feature introduced in v0.6.0. Earlier versions are not supported.

Using external auth (Authentik, Authelia, etc.)?

See connecting without an API key and external auth providers below.

Download

🤖 Download APK Release page

🧪 Sign up to beta test on Google Play

Setup

1. Generate an API key

In the Traefik Manager web UI go to Settings → Authentication → App / Mobile API Keys and click Add Key. Enter a device name (e.g. My Phone) and click Generate. Copy the full key - it is only shown once.

One key per device

Each device should have its own key. You can have up to 10 keys at once. Keys are identified by their device name in the settings list, so you can revoke a single device without affecting others.

2. Configure the app

Open the mobile app and enter:

Field	Value
Server URL	Base URL of your Traefik Manager instance, e.g. `https://traefik-manager.example.com`
API Key	The key generated in step 1

Tap Connect - the app connects immediately.

API key is optional when built-in auth is disabled

If you have disabled Traefik Manager's built-in authentication (e.g. you are using an external provider like Authentik), leave the API key field empty. The app will detect that auth is disabled and connect without a key.

If built-in auth is enabled, an API key is required.

Features

Routes

List all HTTP, TCP, and UDP routes with status, domain, target, and attached middlewares
Enable / disable routes with a toggle - configuration is preserved, Traefik stops routing until re-enabled
Add new routes via a form (name, host/domain, target IP, port, protocol, middlewares)
Edit existing routes
Delete routes with confirmation
Tap a domain to open it in the browser

Middlewares

List all middlewares with type, protocol, and YAML config preview

Add new middlewares - two-step flow: choose from 12 built-in templates then fill in the form

Template	Description
Blank	Start from scratch
HTTPS Redirect	Redirect HTTP to HTTPS
Basic Auth	Password protect your service
Security Headers	HSTS, X-Frame, XSS filter
Rate Limit	Limit requests per source IP
Forward Auth	Delegate auth to an external service
Strip Prefix	Remove a URL path prefix
Add Prefix	Prepend a URL path prefix
Compress	Enable gzip / brotli compression
IP Allowlist	Restrict access by IP range
Redirect Regex	Redirect using a regex pattern
Chain	Combine multiple middlewares

Edit existing middlewares (name + YAML)
Delete middlewares with confirmation

Services

Live service list with protocol badge, type badge, and status chip (Success / Warning / Error)
Server health fraction (e.g. 2/3 active)
Provider and linked router chips
Tap the info icon for a full detail sheet

Edit Mode

Tap the pencil icon in the top bar to enter edit mode. In edit mode, cards reveal:

Toggle (routes only) - enable or disable the route
Edit - open the edit form
Delete - remove with confirmation

Buttons are hidden when not in edit mode to keep the list clean.

Connecting without an API key

If Traefik Manager's built-in auth is disabled, leave the API Key field empty and tap Connect. The app will verify the server is reachable and connect without credentials.

No auth means no protection

If you disable built-in auth and expose Traefik Manager without any other protection, anyone who can reach your instance can use the mobile app with no credentials. Only disable built-in auth if you have an external auth provider (Authentik, Authelia, etc.) in front - and if so, read the external auth providers section to ensure the mobile app still works correctly.

External auth providers

If you use an external auth provider (Authentik, Authelia, Keycloak, etc.) via Traefik's forwardAuth middleware, the middleware intercepts all requests - including the mobile app's API calls - and redirects unauthenticated requests to the provider's login page. The mobile app cannot complete that OAuth/OIDC flow.

The solution is to split the Traefik route into two: one with forwardAuth for the web UI, and one without for /api/* that relies on Traefik Manager's own API key auth.

yaml

http:
  routers:
    traefik-manager-web:
      rule: Host(`manager.example.com`) && !PathPrefix(`/api`)
      middlewares: [authentik]
      entryPoints: [websecure]
      service: traefik-manager
      tls:
        certResolver: cloudflare

    traefik-manager-api:
      rule: Host(`manager.example.com`) && PathPrefix(`/api`)
      entryPoints: [websecure]
      service: traefik-manager
      tls:
        certResolver: cloudflare

  services:
    traefik-manager:
      loadBalancer:
        servers:
          - url: http://traefik-manager:5000

Keep built-in auth enabled

When using this split-route pattern, keep Traefik Manager's built-in auth enabled and generate API keys for your mobile devices. Without built-in auth, the /api/* route has no protection.

Requirements


Traefik Manager (server)	v0.6.0 or higher
Android	7.0+ (API 24+)
iOS	16+ (build from source required)

Tech Stack

Built with Expo SDK 54 / React Native 0.81, Expo Router, TanStack Query, and Zustand.

Mobile App ​

Download ​

Setup ​

1. Generate an API key ​

2. Configure the app ​

Features ​

Routes ​

Middlewares ​

Services ​

Edit Mode ​

Connecting without an API key ​

External auth providers ​

Requirements ​

Tech Stack ​