Petio Docs
  • Introduction
  • FAQ
  • Install Guides
    • Docker
    • Linux
      • Debian 10/Ubuntu 20.04
      • Red Hat/Cent OS
      • Updating Petio
    • FreeBSD
    • MacOS
    • UnRAID
    • Windows
  • Configuration
    • First Time Setup
    • General Settings
    • Radarr
    • Sonarr
    • Console
    • User Profiles
    • Filters
    • Notifications
  • Reverse Proxy
    • Reverse Proxy Basics
    • Caddy
    • NGINX
    • Traefik (v2)
  • Troubleshooting
    • FAQ
  • Staff & Testers Only
    • Petio Pre-Release Workflow For Testers
Powered by GitBook
On this page
  1. Reverse Proxy

Traefik (v2)

If you notice any mistakes that need to be corrected, please reach out on Discord!

PreviousNGINXNextFAQ

Last updated 4 years ago

Traefik Subdomain Example

Assuming a basic setup like where an entrypoint called websecure exists, adding these labels down below to the Petio service should be the minimum that's needed to reverse proxy Petio.

labels:
    - "traefik.enable=true"
    ## HTTP Routers
    - "traefik.http.routers.petio-rtr.entrypoints=websecure"
    - "traefik.http.routers.petio-rtr.rule=Host(`petio.mydomain.com`)"
    - "traefik.http.routers.petio-rtr.tls=true"
    ## HTTP Services
    - "traefik.http.routers.petio-rtr.service=petio-svc"
    - "traefik.http.services.petio-svc.loadbalancer.server.port=7777"
the one in the Traefik documentation