dankhostself-host anything

Reverse-proxy settings for 100 self-hosted apps

You already run nginx, Nginx Proxy Manager, Caddy or Traefik, and one app misbehaves behind it: uploads die with 413, the page loads but never updates, the app logs every visitor as the proxy. For each of these one hundred apps, here is what its own documentation says the proxy and the app need, in all four proxies' terms, each line marked with the page it comes from and the day that page was read.

What it cannot do: it does not test your running proxy, and it only knows what each project wrote down. Projects change their docs and defaults between versions, so every block shows the date its sources were checked; when your version is newer, compare with the linked page.

The defaults that cause most of it

Names used in every block: <app>.example.org is your hostname, the upstream is the service name and port from the project's own compose file (replace it with the container name or LAN address your proxy can reach), and <proxy IP> is the address the app sees the proxy connect from.

Immich app page

Upstream immich-server:2283 · WebSockets: required [1] · Upload limit: 50000M [1] · Timeouts: 600s [1] · docs checked 2026-09-26

nginx

# Immich: nginx for photos.example.org
# App-specific lines are checked against Immich's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name photos.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name photos.example.org;
    ssl_certificate     /etc/letsencrypt/live/photos.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/photos.example.org/privkey.pem;

    client_max_body_size 50000M; # [1]
    proxy_read_timeout 600s; # [1]
    proxy_send_timeout 600s; # [1]
    proxy_request_buffering off; # [1]
    client_body_buffer_size 1024k; # [1]
    send_timeout 600s; # [1]
    proxy_redirect off; # [1]

    location / {
        proxy_pass http://immich-server:2283;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Immich
# Checked against Immich's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... photos.example.org
  Scheme ................ http
  Forward Hostname / IP . immich-server
  Forward Port .......... 2283
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 50000M; # [1]
proxy_read_timeout 600s; # [1]
proxy_send_timeout 600s; # [1]
proxy_request_buffering off; # [1]
client_body_buffer_size 1024k; # [1]
send_timeout 600s; # [1]
proxy_redirect off; # [1]

Caddyfile

# Immich: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Immich's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
photos.example.org {
	reverse_proxy immich-server:2283
}

Traefik labels

# Immich: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Immich's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  immich-server:
    labels:
      traefik.enable: "true"
      traefik.http.routers.immich.rule: "Host(`photos.example.org`)"
      traefik.http.routers.immich.entrypoints: "websecure"
      traefik.http.routers.immich.tls: "true"
      traefik.http.routers.immich.tls.certresolver: "letsencrypt"
      traefik.http.routers.immich.service: "immich"
      traefik.http.services.immich.loadbalancer.server.port: "2283"
      # [1] Immich's docs: Traefik's entrypoint readTimeout defaults to 60s, which stops video
      # uploads after a minute (error 499). Raise it in Traefik's static configuration:
      # entryPoints.websecure.transport.respondingTimeouts.readTimeout: 600s and idleTimeout:
      # 600s. (The dankhost builder sets readTimeout to 0, no limit.)

In Immich itself

  1. Immich docs: Reverse Proxy (nginx, Caddy and Traefik examples) checked 2026-09-26
  2. Immich docs: Environment Variables (IMMICH_TRUSTED_PROXIES) checked 2026-09-26

Nextcloud app page

Upstream app:80 · WebSockets: not in the docs · Upload limit: 512M [3] · Timeouts: defaults · docs checked 2026-09-26

nginx

# Nextcloud: nginx for cloud.example.org
# App-specific lines are checked against Nextcloud's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name cloud.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name cloud.example.org;
    ssl_certificate     /etc/letsencrypt/live/cloud.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/cloud.example.org/privkey.pem;

    client_max_body_size 512M; # [3]
    proxy_buffering off; # [2]

    location / {
        proxy_pass http://app:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    location /.well-known/carddav { # [1]
        return 301 $scheme://$host/remote.php/dav;
    }

    location /.well-known/caldav { # [1]
        return 301 $scheme://$host/remote.php/dav;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Nextcloud
# Checked against Nextcloud's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... cloud.example.org
  Scheme ................ http
  Forward Hostname / IP . app
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 512M; # [3]
proxy_buffering off; # [2]
proxy_hide_header Upgrade; # [1]
location /.well-known/carddav { # [1]
    return 301 $scheme://$host/remote.php/dav;
}
location /.well-known/caldav { # [1]
    return 301 $scheme://$host/remote.php/dav;
}
  • Nextcloud's manual: with Nginx Proxy Manager, add proxy_hide_header Upgrade; to the Custom Nginx Configuration, otherwise iPhones and iPads get 'Connection Closed'. [1]

Caddyfile

# Nextcloud: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Nextcloud's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
cloud.example.org {
	# [1]
	redir /.well-known/carddav /remote.php/dav/ 301
	# [1]
	redir /.well-known/caldav /remote.php/dav/ 301
	reverse_proxy app:80
}

Traefik labels

# Nextcloud: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Nextcloud's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.nextcloud.rule: "Host(`cloud.example.org`)"
      traefik.http.routers.nextcloud.entrypoints: "websecure"
      traefik.http.routers.nextcloud.tls: "true"
      traefik.http.routers.nextcloud.tls.certresolver: "letsencrypt"
      traefik.http.routers.nextcloud.service: "nextcloud"
      traefik.http.routers.nextcloud.middlewares: "nextcloud-dav-redirect"
      traefik.http.services.nextcloud.loadbalancer.server.port: "80"
      traefik.http.middlewares.nextcloud-dav-redirect.redirectregex.regex: "^https://cloud\\.example\\.org/\\.well-known/(?:card|cal)dav$$"
      traefik.http.middlewares.nextcloud-dav-redirect.redirectregex.replacement: "https://cloud.example.org/remote.php/dav/"
      traefik.http.middlewares.nextcloud-dav-redirect.redirectregex.permanent: "true"
      # [1] The dav-redirect middleware is the Traefik 2+ redirectregex the manual gives for
      # /.well-known/carddav and caldav, pointed at /remote.php/dav/.

In Nextcloud itself

  1. Nextcloud admin manual: Reverse proxy (trusted_proxies, overwrite parameters, CalDAV/CardDAV redirects, the NPM proxy_hide_header note) checked 2026-09-26
  2. Nextcloud admin manual: Uploading big files (client_max_body_size; downloads over 1 GB need proxy_buffering off on an nginx frontend; 100 MiB upload chunks) checked 2026-09-26
  3. Nextcloud admin manual: NGINX configuration (client_max_body_size 512M) checked 2026-09-26
  4. nextcloud/docker README: behind a reverse proxy (TRUSTED_PROXIES, OVERWRITEPROTOCOL, OVERWRITECLIURL, APACHE_DISABLE_REWRITE_IP) checked 2026-09-26

Home Assistant app page

Upstream host.docker.internal:8123 · WebSockets: required [2] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26

nginx

# Home Assistant: nginx for home.example.org
# App-specific lines are checked against Home Assistant's docs (2026-09-26); [n] = source n below.

# Home Assistant runs with host networking: host.docker.internal:8123 from nginx in a container
# (with an extra_hosts host-gateway entry), 127.0.0.1:8123 from nginx on the same machine.
upstream home-assistant {
    server host.docker.internal:8123;
}

# WebSocket map [2]. It belongs in the http {} context, which conf.d files are.
# Leave it out if your nginx already defines $connection_upgrade.
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen 80;
    listen [::]:80;
    server_name home.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name home.example.org;
    ssl_certificate     /etc/letsencrypt/live/home.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/home.example.org/privkey.pem;

    proxy_buffering off; # [2]

    location / {
        proxy_pass http://home-assistant;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [2]
        proxy_set_header Upgrade $http_upgrade; # [2]
        proxy_set_header Connection $connection_upgrade; # [2]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Home Assistant
# Checked against Home Assistant's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... home.example.org
  Scheme ................ http
  Forward Hostname / IP . host.docker.internal
  Forward Port .......... 8123
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [2]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_buffering off; # [2]

Caddyfile

# Home Assistant: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Home Assistant's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
home.example.org {
	reverse_proxy host.docker.internal:8123
}

Traefik labels

# Home Assistant: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Home Assistant's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
# Home Assistant uses host networking: Traefik reaches it at host.docker.internal:8123.
services:
  homeassistant:
    labels:
      traefik.enable: "true"
      traefik.http.routers.home-assistant.rule: "Host(`home.example.org`)"
      traefik.http.routers.home-assistant.entrypoints: "websecure"
      traefik.http.routers.home-assistant.tls: "true"
      traefik.http.routers.home-assistant.tls.certresolver: "letsencrypt"
      traefik.http.routers.home-assistant.service: "home-assistant"
      traefik.http.services.home-assistant.loadbalancer.server.port: "8123"

In Home Assistant itself

  1. Home Assistant: HTTP integration (Reverse proxies; settings moved to Settings > System > Network in 2026.8; migrating from YAML) checked 2026-09-26
  2. Home Assistant's official NGINX add-on: nginx.conf.gtpl (Upgrade/Connection via map, proxy_buffering off) checked 2026-09-26

Vaultwarden app page

Upstream vaultwarden:80 · WebSockets: required [1] · Upload limit: 525M [1] · Timeouts: defaults · docs checked 2026-09-26

nginx

# Vaultwarden: nginx for vault.example.org
# App-specific lines are checked against Vaultwarden's docs (2026-09-26); [n] = source n below.

# WebSocket map [1]. It belongs in the http {} context, which conf.d files are.
# Leave it out if your nginx already defines $connection_upgrade.
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      "";
}

server {
    listen 80;
    listen [::]:80;
    server_name vault.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name vault.example.org;
    ssl_certificate     /etc/letsencrypt/live/vault.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/vault.example.org/privkey.pem;

    client_max_body_size 525M; # [1]

    location / {
        proxy_pass http://vaultwarden:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $connection_upgrade; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Vaultwarden
# Checked against Vaultwarden's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... vault.example.org
  Scheme ................ http
  Forward Hostname / IP . vaultwarden
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 525M; # [1]

Caddyfile

# Vaultwarden: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Vaultwarden's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
vault.example.org {
	reverse_proxy vaultwarden:80 {
		# [1]
		header_up X-Real-IP {remote_host}
	}
}

Traefik labels

# Vaultwarden: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Vaultwarden's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  vaultwarden:
    labels:
      traefik.enable: "true"
      traefik.http.routers.vaultwarden.rule: "Host(`vault.example.org`)"
      traefik.http.routers.vaultwarden.entrypoints: "websecure"
      traefik.http.routers.vaultwarden.tls: "true"
      traefik.http.routers.vaultwarden.tls.certresolver: "letsencrypt"
      traefik.http.routers.vaultwarden.service: "vaultwarden"
      traefik.http.services.vaultwarden.loadbalancer.server.port: "80"

In Vaultwarden itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Vaultwarden wiki: Proxy examples (nginx with websocket map and client_max_body_size 525M; Caddy 2.x header_up X-Real-IP) checked 2026-09-26

Jellyfin app page

Upstream jellyfin:8096 · WebSockets: required on /socket [1] · Upload limit: 20M [1] · Timeouts: defaults · docs checked 2026-09-26

nginx

# Jellyfin: nginx for media.example.org
# App-specific lines are checked against Jellyfin's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name media.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name media.example.org;
    ssl_certificate     /etc/letsencrypt/live/media.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/media.example.org/privkey.pem;

    client_max_body_size 20M; # [1]

    location / {
        proxy_pass http://jellyfin:8096;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Protocol $scheme; # [1]
        proxy_set_header X-Forwarded-Host $http_host; # [1]
        proxy_buffering off; # [1]
    }

    # WebSocket traffic [1]
    location /socket {
        proxy_pass http://jellyfin:8096;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Protocol $scheme; # [1]
        proxy_set_header X-Forwarded-Host $http_host; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Jellyfin
# Checked against Jellyfin's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... media.example.org
  Scheme ................ http
  Forward Hostname / IP . jellyfin
  Forward Port .......... 8096
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 20M; # [1]
proxy_buffering off; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Protocol $scheme; # [1]
    proxy_set_header X-Forwarded-Host $http_host; # [1]
}

Caddyfile

# Jellyfin: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Jellyfin's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
media.example.org {
	reverse_proxy jellyfin:8096
}

Traefik labels

# Jellyfin: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Jellyfin's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  jellyfin:
    labels:
      traefik.enable: "true"
      traefik.http.routers.jellyfin.rule: "Host(`media.example.org`)"
      traefik.http.routers.jellyfin.entrypoints: "websecure"
      traefik.http.routers.jellyfin.tls: "true"
      traefik.http.routers.jellyfin.tls.certresolver: "letsencrypt"
      traefik.http.routers.jellyfin.service: "jellyfin"
      traefik.http.services.jellyfin.loadbalancer.server.port: "8096"

In Jellyfin itself

  1. Jellyfin docs: Reverse Proxy > Nginx (client_max_body_size 20M, proxy_buffering off, the /socket location) checked 2026-09-26
  2. Jellyfin docs: Reverse Proxy (Known Proxies, Websockets) checked 2026-09-26

Paperless-ngx app page

Upstream webserver:8000 · WebSockets: required [1] · Upload limit: 10M [1] · Timeouts: defaults · docs checked 2026-09-26

nginx

# Paperless-ngx: nginx for docs.example.org
# App-specific lines are checked against Paperless-ngx's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name docs.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name docs.example.org;
    ssl_certificate     /etc/letsencrypt/live/docs.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/docs.example.org/privkey.pem;

    client_max_body_size 10M; # [1]

    location / {
        proxy_pass http://webserver:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $server_name; # [1]
        proxy_redirect off; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Paperless-ngx
# Checked against Paperless-ngx's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... docs.example.org
  Scheme ................ http
  Forward Hostname / IP . webserver
  Forward Port .......... 8000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 10M; # [1]
proxy_redirect off; # [1]
proxy_send_timeout 600m; # [1]
proxy_read_timeout 600m; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Host $server_name; # [1]
}
  • The wiki: NPM's 90-second default timeout cuts the WebSocket when nothing changes for 90 seconds; raise it in the Custom Nginx Configuration. [1]

Caddyfile

# Paperless-ngx: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Paperless-ngx's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
docs.example.org {
	reverse_proxy webserver:8000
}

Traefik labels

# Paperless-ngx: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Paperless-ngx's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  webserver:
    labels:
      traefik.enable: "true"
      traefik.http.routers.paperless.rule: "Host(`docs.example.org`)"
      traefik.http.routers.paperless.entrypoints: "websecure"
      traefik.http.routers.paperless.tls: "true"
      traefik.http.routers.paperless.tls.certresolver: "letsencrypt"
      traefik.http.routers.paperless.service: "paperless"
      traefik.http.services.paperless.loadbalancer.server.port: "8000"

In Paperless-ngx itself

  1. Paperless-ngx wiki: Using a Reverse Proxy with Paperless-ngx (nginx, Nginx Proxy Manager) checked 2026-09-26
  2. Paperless-ngx docs source: configuration.md (PAPERLESS_URL) checked 2026-09-26

Uptime Kuma app page

Upstream uptime-kuma:3001 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26

nginx

# Uptime Kuma: nginx for status.example.org
# App-specific lines are checked against Uptime Kuma's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name status.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name status.example.org;
    ssl_certificate     /etc/letsencrypt/live/status.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/status.example.org/privkey.pem;

    location / {
        proxy_pass http://uptime-kuma:3001;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Uptime Kuma
# Checked against Uptime Kuma's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... status.example.org
  Scheme ................ http
  Forward Hostname / IP . uptime-kuma
  Forward Port .......... 3001
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Uptime Kuma's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Uptime Kuma: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Uptime Kuma's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
status.example.org {
	reverse_proxy uptime-kuma:3001
}

Traefik labels

# Uptime Kuma: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Uptime Kuma's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  uptime-kuma:
    labels:
      traefik.enable: "true"
      traefik.http.routers.uptime-kuma.rule: "Host(`status.example.org`)"
      traefik.http.routers.uptime-kuma.entrypoints: "websecure"
      traefik.http.routers.uptime-kuma.tls: "true"
      traefik.http.routers.uptime-kuma.tls.certresolver: "letsencrypt"
      traefik.http.routers.uptime-kuma.service: "uptime-kuma"
      traefik.http.services.uptime-kuma.loadbalancer.server.port: "3001"

In Uptime Kuma itself

  1. Uptime Kuma wiki: Reverse Proxy (nginx, Nginx Proxy Manager, Trust Proxy) checked 2026-09-26

Audiobookshelf app page

Upstream audiobookshelf:80 · WebSockets: required [1] · Upload limit: 10240M [2] · Timeouts: defaults · docs checked 2026-09-26

nginx

# Audiobookshelf: nginx for books.example.org
# App-specific lines are checked against Audiobookshelf's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name books.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name books.example.org;
    ssl_certificate     /etc/letsencrypt/live/books.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/books.example.org/privkey.pem;

    client_max_body_size 10240M; # [2]

    location / {
        proxy_pass http://audiobookshelf:80;
        proxy_set_header Host $http_host; # [2]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_redirect http:// https://; # [2]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Audiobookshelf
# Checked against Audiobookshelf's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... books.example.org
  Scheme ................ http
  Forward Hostname / IP . audiobookshelf
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 10240M; # [2]
proxy_redirect http:// https://; # [2]
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.
  • The docs: only if NPM listens on a non-standard port (not 443) does the Host header need changing, with a custom location '/' carrying proxy_set_header Host $http_host. On 443 NPM's own Host $host is the same value. [3]

Caddyfile

# Audiobookshelf: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Audiobookshelf's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
books.example.org {
	reverse_proxy audiobookshelf:80
}

Traefik labels

# Audiobookshelf: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Audiobookshelf's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  audiobookshelf:
    labels:
      traefik.enable: "true"
      traefik.http.routers.audiobookshelf.rule: "Host(`books.example.org`)"
      traefik.http.routers.audiobookshelf.entrypoints: "websecure"
      traefik.http.routers.audiobookshelf.tls: "true"
      traefik.http.routers.audiobookshelf.tls.certresolver: "letsencrypt"
      traefik.http.routers.audiobookshelf.service: "audiobookshelf"
      traefik.http.services.audiobookshelf.loadbalancer.server.port: "80"

In Audiobookshelf itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Audiobookshelf README: Reverse Proxy Set Up ('Audiobookshelf requires a websocket connection') checked 2026-09-26
  2. Audiobookshelf docs: Reverse proxy > NGINX (client_max_body_size 10240M, Host $http_host, proxy_redirect) checked 2026-09-26
  3. Audiobookshelf docs: Reverse proxy > NPM (websockets on; Host header for non-standard ports) checked 2026-09-26

PhotoPrism app page

Upstream photoprism:2342 · WebSockets: required [1] · Upload limit: 512M [1] · Timeouts: 600s [1] · docs checked 2026-09-26

nginx

# PhotoPrism: nginx for gallery.example.org
# App-specific lines are checked against PhotoPrism's docs (2026-09-26); [n] = source n below.

# WebSocket map [1]. It belongs in the http {} context, which conf.d files are.
# Leave it out if your nginx already defines $connection_upgrade.
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen 80;
    listen [::]:80;
    server_name gallery.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name gallery.example.org;
    ssl_certificate     /etc/letsencrypt/live/gallery.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/gallery.example.org/privkey.pem;

    client_max_body_size 512M; # [1]
    proxy_read_timeout 600s; # [1]
    proxy_send_timeout 600s; # [1]
    proxy_buffering off; # [1]

    location / {
        proxy_pass http://photoprism:2342;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $host; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $connection_upgrade; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for PhotoPrism
# Checked against PhotoPrism's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... gallery.example.org
  Scheme ................ http
  Forward Hostname / IP . photoprism
  Forward Port .......... 2342
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 512M; # [1]
proxy_read_timeout 600s; # [1]
proxy_send_timeout 600s; # [1]
proxy_buffering off; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Host $host; # [1]
}

Caddyfile

# PhotoPrism: Caddyfile site block, the same one the dankhost builder writes.
# Checked against PhotoPrism's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
gallery.example.org {
	# [2]
	encode zstd gzip
	reverse_proxy photoprism:2342 {
		# [2]
		flush_interval -1
	}
}

Traefik labels

# PhotoPrism: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against PhotoPrism's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  photoprism:
    labels:
      traefik.enable: "true"
      traefik.http.routers.photoprism.rule: "Host(`gallery.example.org`)"
      traefik.http.routers.photoprism.entrypoints: "websecure"
      traefik.http.routers.photoprism.tls: "true"
      traefik.http.routers.photoprism.tls.certresolver: "letsencrypt"
      traefik.http.routers.photoprism.service: "photoprism"
      traefik.http.routers.photoprism.middlewares: "photoprism-compress"
      traefik.http.services.photoprism.loadbalancer.server.port: "2342"
      traefik.http.services.photoprism.loadbalancer.responseforwarding.flushinterval: "-1ms"
      traefik.http.middlewares.photoprism-compress.compress.encodings: "zstd,gzip"
      # [2] The compress middleware (zstd, gzip) and responseForwarding.flushInterval=-1ms are
      # Traefik's form of the Caddy example's encode and flush_interval -1.

In PhotoPrism itself

  1. PhotoPrism docs: Using NGINX as Reverse Proxy (client_max_body_size 512M, proxy_buffering off, 600s timeouts, websocket map, PHOTOPRISM_TRUSTED_PROXY) checked 2026-09-26
  2. PhotoPrism docs: Caddy 2 (encode zstd gzip, flush_interval -1) checked 2026-09-26

Syncthing app page

Upstream syncthing:8384 · WebSockets: not in the docs · Upload limit: not given · Timeouts: 600s [1] · docs checked 2026-09-26

nginx

# Syncthing: nginx for sync.example.org
# App-specific lines are checked against Syncthing's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name sync.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name sync.example.org;
    ssl_certificate     /etc/letsencrypt/live/sync.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/sync.example.org/privkey.pem;

    proxy_read_timeout 600s; # [1]
    proxy_send_timeout 600s; # [1]

    location / {
        proxy_pass http://syncthing:8384;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Syncthing
# Checked against Syncthing's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... sync.example.org
  Scheme ................ http
  Forward Hostname / IP . syncthing
  Forward Port .......... 8384
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_read_timeout 600s; # [1]
proxy_send_timeout 600s; # [1]

Caddyfile

# Syncthing: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Syncthing's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
sync.example.org {
	reverse_proxy syncthing:8384 {
		# [1]
		header_up Host {upstream_hostport}
	}
}

Traefik labels

# Syncthing: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Syncthing's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  syncthing:
    labels:
      traefik.enable: "true"
      traefik.http.routers.syncthing.rule: "Host(`sync.example.org`)"
      traefik.http.routers.syncthing.entrypoints: "websecure"
      traefik.http.routers.syncthing.tls: "true"
      traefik.http.routers.syncthing.tls.certresolver: "letsencrypt"
      traefik.http.routers.syncthing.service: "syncthing"
      traefik.http.services.syncthing.loadbalancer.server.port: "8384"
      traefik.http.services.syncthing.loadbalancer.passhostheader: "false"
      # [1] passHostHeader=false is Traefik's form of the Caddy example's header_up Host
      # {upstream_hostport}: Syncthing receives its own address as Host.

In Syncthing itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Syncthing docs: Reverse Proxy Setup (nginx with 600s timeouts; Caddy v2 header_up Host {upstream_hostport}) checked 2026-09-26

n8n app page

Upstream n8n:5678 · WebSockets: required [2] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26

nginx

# n8n: nginx for n8n.example.org
# App-specific lines are checked against n8n's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name n8n.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name n8n.example.org;
    ssl_certificate     /etc/letsencrypt/live/n8n.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/n8n.example.org/privkey.pem;

    location / {
        proxy_pass http://n8n:5678;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $host; # [1]
        proxy_http_version 1.1; # [2]
        proxy_set_header Upgrade $http_upgrade; # [2]
        proxy_set_header Connection "upgrade"; # [2]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for n8n
# Checked against n8n's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... n8n.example.org
  Scheme ................ http
  Forward Hostname / IP . n8n
  Forward Port .......... 5678
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [2]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Host $host; # [1]
}

Caddyfile

# n8n: Caddyfile site block, the same one the dankhost builder writes.
# Checked against n8n's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
n8n.example.org {
	reverse_proxy n8n:5678
}

Traefik labels

# n8n: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against n8n's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  n8n:
    labels:
      traefik.enable: "true"
      traefik.http.routers.n8n.rule: "Host(`n8n.example.org`)"
      traefik.http.routers.n8n.entrypoints: "websecure"
      traefik.http.routers.n8n.tls: "true"
      traefik.http.routers.n8n.tls.certresolver: "letsencrypt"
      traefik.http.routers.n8n.service: "n8n"
      traefik.http.services.n8n.loadbalancer.server.port: "5678"

In n8n itself

  1. n8n docs: Configure webhook URLs with reverse proxy (N8N_WEBHOOK_URL, N8N_PROXY_HOPS=1, X-Forwarded-For/-Host/-Proto) checked 2026-09-26
  2. n8n docs: Deployment environment variables (N8N_PUSH_BACKEND defaults to websocket) checked 2026-09-26

Open WebUI app page

Upstream open-webui:8080 · WebSockets: required [1] · Upload limit: 20M [1] · Timeouts: 10m [1] · docs checked 2026-09-26

nginx

# Open WebUI: nginx for chat.example.org
# App-specific lines are checked against Open WebUI's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name chat.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name chat.example.org;
    ssl_certificate     /etc/letsencrypt/live/chat.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/chat.example.org/privkey.pem;

    client_max_body_size 20M; # [1]
    proxy_read_timeout 10m; # [1]
    proxy_buffering off; # [1]
    proxy_cache off; # [1]

    location / {
        proxy_pass http://open-webui:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Open WebUI
# Checked against Open WebUI's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... chat.example.org
  Scheme ................ http
  Forward Hostname / IP . open-webui
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 20M; # [1]
proxy_read_timeout 10m; # [1]
proxy_buffering off; # [1]
proxy_cache off; # [1]
  • The docs give 30-minute timeouts for very long completions in NPM (proxy_read_timeout 1800; proxy_send_timeout 1800; proxy_connect_timeout 1800;). If you use them, replace the proxy_read_timeout line above rather than adding a second one: nginx refuses a duplicate. [1]

Caddyfile

# Open WebUI: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Open WebUI's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
chat.example.org {
	reverse_proxy open-webui:8080
}

Traefik labels

# Open WebUI: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Open WebUI's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  open-webui:
    labels:
      traefik.enable: "true"
      traefik.http.routers.open-webui.rule: "Host(`chat.example.org`)"
      traefik.http.routers.open-webui.entrypoints: "websecure"
      traefik.http.routers.open-webui.tls: "true"
      traefik.http.routers.open-webui.tls.certresolver: "letsencrypt"
      traefik.http.routers.open-webui.service: "open-webui"
      traefik.http.services.open-webui.loadbalancer.server.port: "8080"

In Open WebUI itself

  1. Open WebUI docs: HTTPS with Nginx (WebSocket headers, proxy_buffering off for streaming, timeouts, client_max_body_size 20M, CORS_ALLOW_ORIGIN, Nginx Proxy Manager) checked 2026-09-26

Grafana app page

Upstream grafana:3000 · WebSockets: required on /api/live/ [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26

nginx

# Grafana: nginx for grafana.example.org
# App-specific lines are checked against Grafana's docs (2026-09-26); [n] = source n below.

# WebSocket map [1]. It belongs in the http {} context, which conf.d files are.
# Leave it out if your nginx already defines $connection_upgrade.
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen 80;
    listen [::]:80;
    server_name grafana.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name grafana.example.org;
    ssl_certificate     /etc/letsencrypt/live/grafana.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/grafana.example.org/privkey.pem;

    location / {
        proxy_pass http://grafana:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # WebSocket traffic [1]
    location /api/live/ {
        proxy_pass http://grafana:3000;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $connection_upgrade; # [1]
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Grafana
# Checked against Grafana's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... grafana.example.org
  Scheme ................ http
  Forward Hostname / IP . grafana
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Grafana's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Grafana: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Grafana's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
grafana.example.org {
	reverse_proxy grafana:3000
}

Traefik labels

# Grafana: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Grafana's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  grafana:
    labels:
      traefik.enable: "true"
      traefik.http.routers.grafana.rule: "Host(`grafana.example.org`)"
      traefik.http.routers.grafana.entrypoints: "websecure"
      traefik.http.routers.grafana.tls: "true"
      traefik.http.routers.grafana.tls.certresolver: "letsencrypt"
      traefik.http.routers.grafana.service: "grafana"
      traefik.http.services.grafana.loadbalancer.server.port: "3000"

In Grafana itself

  1. Grafana tutorial: Run Grafana behind a reverse proxy (domain, root_url, the /api/live/ WebSocket location) checked 2026-09-26

Forgejo app page

Upstream server:3000 · WebSockets: required [1] · Upload limit: 512M [1] · Timeouts: defaults · docs checked 2026-09-26

nginx

# Forgejo: nginx for git.example.org
# App-specific lines are checked against Forgejo's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name git.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name git.example.org;
    ssl_certificate     /etc/letsencrypt/live/git.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/git.example.org/privkey.pem;

    client_max_body_size 512M; # [1]
    merge_slashes off; # [1]

    location / {
        proxy_pass http://server:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $http_connection; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Forgejo
# Checked against Forgejo's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... git.example.org
  Scheme ................ http
  Forward Hostname / IP . server
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 512M; # [1]
merge_slashes off; # [1]

Caddyfile

# Forgejo: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Forgejo's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
git.example.org {
	reverse_proxy server:3000
}

Traefik labels

# Forgejo: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Forgejo's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  server:
    labels:
      traefik.enable: "true"
      traefik.http.routers.forgejo.rule: "Host(`git.example.org`)"
      traefik.http.routers.forgejo.entrypoints: "websecure"
      traefik.http.routers.forgejo.tls: "true"
      traefik.http.routers.forgejo.tls.certresolver: "letsencrypt"
      traefik.http.routers.forgejo.service: "forgejo"
      traefik.http.services.forgejo.loadbalancer.server.port: "3000"

In Forgejo itself

  1. Forgejo docs: Reverse proxy (nginx: merge_slashes off, client_max_body_size 512M, Upgrade/Connection; ROOT_URL) checked 2026-09-26

Frigate app page

Upstream frigate:8971 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26

nginx

# Frigate: nginx for nvr.example.org
# App-specific lines are checked against Frigate's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name nvr.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name nvr.example.org;
    ssl_certificate     /etc/letsencrypt/live/nvr.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/nvr.example.org/privkey.pem;

    location / {
        proxy_pass http://frigate:8971;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $http_connection; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Frigate
# Checked against Frigate's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... nvr.example.org
  Scheme ................ http
  Forward Hostname / IP . frigate
  Forward Port .......... 8971
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Frigate's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Frigate: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Frigate's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
nvr.example.org {
	reverse_proxy frigate:8971
}

Traefik labels

# Frigate: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Frigate's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  frigate:
    labels:
      traefik.enable: "true"
      traefik.http.routers.frigate.rule: "Host(`nvr.example.org`)"
      traefik.http.routers.frigate.entrypoints: "websecure"
      traefik.http.routers.frigate.tls: "true"
      traefik.http.routers.frigate.tls.certresolver: "letsencrypt"
      traefik.http.routers.frigate.service: "frigate"
      traefik.http.services.frigate.loadbalancer.server.port: "8971"
      # No https server scheme label here: with Frigate's own TLS turned off (see "In Frigate
      # itself") Traefik talks plain HTTP to port 8971, and nothing here skips certificate
      # checks.

In Frigate itself

  1. Frigate docs: Setting up a reverse proxy (disable Frigate's TLS first; WebSocket support; NPM's Websockets Support toggle) checked 2026-09-26
  2. Frigate docs: TLS (self-signed certificate on 8971 by default; tls: enabled: False, or Settings > System > TLS) checked 2026-09-26

Portainer CE app page

Upstream portainer:9000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26

nginx

# Portainer CE: nginx for portainer.example.org
# App-specific lines are checked against Portainer CE's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name portainer.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name portainer.example.org;
    ssl_certificate     /etc/letsencrypt/live/portainer.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/portainer.example.org/privkey.pem;

    location / {
        proxy_pass http://portainer:9000;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Portainer CE
# Checked against Portainer CE's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... portainer.example.org
  Scheme ................ http
  Forward Hostname / IP . portainer
  Forward Port .......... 9000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.
  • NPM sends Host $host, which equals $http_host while NPM listens on the standard port 443; on another port Portainer's CSRF check rejects requests with 403 unless you add the public origin with --trusted-origins. [1]

Caddyfile

# Portainer CE: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Portainer CE's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
portainer.example.org {
	reverse_proxy portainer:9000
}

Traefik labels

# Portainer CE: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Portainer CE's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  portainer:
    labels:
      traefik.enable: "true"
      traefik.http.routers.portainer.rule: "Host(`portainer.example.org`)"
      traefik.http.routers.portainer.entrypoints: "websecure"
      traefik.http.routers.portainer.tls: "true"
      traefik.http.routers.portainer.tls.certresolver: "letsencrypt"
      traefik.http.routers.portainer.service: "portainer"
      traefik.http.services.portainer.loadbalancer.server.port: "9000"

In Portainer CE itself

  1. Portainer docs: Using Portainer with reverse proxies (X-Forwarded-Proto and Secure cookies, Host $http_host for the CSRF check, --trusted-origins, --trusted-proxies) checked 2026-09-26

AdGuard Home app page

Upstream adguardhome:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26

nginx

# AdGuard Home: nginx for adguard.example.org
# App-specific lines are checked against AdGuard Home's docs (2026-09-26); [n] = source n below.
# AdGuard Home's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name adguard.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name adguard.example.org;
    ssl_certificate     /etc/letsencrypt/live/adguard.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/adguard.example.org/privkey.pem;

    location / {
        proxy_pass http://adguardhome:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for AdGuard Home
# Checked against AdGuard Home's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... adguard.example.org
  Scheme ................ http
  Forward Hostname / IP . adguardhome
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: AdGuard Home's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# AdGuard Home: Caddyfile site block, the same one the dankhost builder writes.
# Checked against AdGuard Home's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
adguard.example.org {
	reverse_proxy adguardhome:3000
}

Traefik labels

# AdGuard Home: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against AdGuard Home's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  adguardhome:
    labels:
      traefik.enable: "true"
      traefik.http.routers.adguard-home.rule: "Host(`adguard.example.org`)"
      traefik.http.routers.adguard-home.entrypoints: "websecure"
      traefik.http.routers.adguard-home.tls: "true"
      traefik.http.routers.adguard-home.tls.certresolver: "letsencrypt"
      traefik.http.routers.adguard-home.service: "adguard-home"
      traefik.http.services.adguard-home.loadbalancer.server.port: "3000"

In AdGuard Home itself

  1. AdGuard Home FAQ: How do I configure a reverse proxy server for AdGuard Home? (nginx, Caddy, DoH without TLS, trusted_proxies) checked 2026-09-26
  2. AdGuard Home wiki: Configuration (dns.trusted_proxies; http.doh.insecure_enabled since v0.107.74) checked 2026-09-26

ntfy app page

Upstream ntfy:80 · WebSockets: required [1] · Upload limit: 0 [1] · Timeouts: 3m [1] · docs checked 2026-09-26

nginx

# ntfy: nginx for ntfy.example.org
# App-specific lines are checked against ntfy's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name ntfy.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name ntfy.example.org;
    ssl_certificate     /etc/letsencrypt/live/ntfy.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/ntfy.example.org/privkey.pem;

    client_max_body_size 0; # [1]
    proxy_connect_timeout 3m; # [1]
    proxy_read_timeout 3m; # [1]
    proxy_send_timeout 3m; # [1]
    proxy_buffering off; # [1]
    proxy_request_buffering off; # [1]
    proxy_redirect off; # [1]

    location / {
        proxy_pass http://ntfy:80;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for ntfy
# Checked against ntfy's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... ntfy.example.org
  Scheme ................ http
  Forward Hostname / IP . ntfy
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 0; # [1]
proxy_connect_timeout 3m; # [1]
proxy_read_timeout 3m; # [1]
proxy_send_timeout 3m; # [1]
proxy_buffering off; # [1]
proxy_request_buffering off; # [1]
proxy_redirect off; # [1]
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.

Caddyfile

# ntfy: Caddyfile site block, the same one the dankhost builder writes.
# Checked against ntfy's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
ntfy.example.org {
	reverse_proxy ntfy:80
}

Traefik labels

# ntfy: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against ntfy's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  ntfy:
    labels:
      traefik.enable: "true"
      traefik.http.routers.ntfy.rule: "Host(`ntfy.example.org`)"
      traefik.http.routers.ntfy.entrypoints: "websecure"
      traefik.http.routers.ntfy.tls: "true"
      traefik.http.routers.ntfy.tls.certresolver: "letsencrypt"
      traefik.http.routers.ntfy.service: "ntfy"
      traefik.http.services.ntfy.loadbalancer.server.port: "80"

In ntfy itself

  1. ntfy docs: Configuring the ntfy server, 'Behind a proxy (TLS, etc.)' and the nginx example checked 2026-09-26

Gotify app page

Upstream gotify:80 · WebSockets: required [1] · Upload limit: not given · Timeouts: 1m [1] · docs checked 2026-09-26

nginx

# Gotify: nginx for gotify.example.org
# App-specific lines are checked against Gotify's docs (2026-09-26); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name gotify.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name gotify.example.org;
    ssl_certificate     /etc/letsencrypt/live/gotify.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/gotify.example.org/privkey.pem;

    proxy_connect_timeout 1m; # [1]
    proxy_read_timeout 1m; # [1]
    proxy_send_timeout 1m; # [1]

    location / {
        proxy_pass http://gotify:80;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_redirect http:// $scheme://; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Gotify
# Checked against Gotify's docs (2026-09-26); [n] = source n below.

Details tab
  Domain Names .......... gotify.example.org
  Scheme ................ http
  Forward Hostname / IP . gotify
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_connect_timeout 1m; # [1]
proxy_read_timeout 1m; # [1]
proxy_send_timeout 1m; # [1]
proxy_redirect http:// $scheme://; # [1]
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.

Caddyfile

# Gotify: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Gotify's docs (2026-09-26); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
gotify.example.org {
	reverse_proxy gotify:80
}

Traefik labels

# Gotify: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Gotify's docs (2026-09-26); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  gotify:
    labels:
      traefik.enable: "true"
      traefik.http.routers.gotify.rule: "Host(`gotify.example.org`)"
      traefik.http.routers.gotify.entrypoints: "websecure"
      traefik.http.routers.gotify.tls: "true"
      traefik.http.routers.gotify.tls.certresolver: "letsencrypt"
      traefik.http.routers.gotify.service: "gotify"
      traefik.http.services.gotify.loadbalancer.server.port: "80"

In Gotify itself

  1. Gotify docs: nginx (WebSocket headers, Host $http_host, 1m timeouts) checked 2026-09-26
  2. Gotify docs: Configuration (GOTIFY_SERVER_TRUSTEDPROXIES, GOTIFY_SERVER_SECURECOOKIE) checked 2026-09-26

Pi-hole app page

Upstream pihole:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29

nginx

# Pi-hole: nginx for pihole.example.org
# App-specific lines are checked against Pi-hole's docs (2026-09-29); [n] = source n below.
# Pi-hole's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name pihole.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name pihole.example.org;
    ssl_certificate     /etc/letsencrypt/live/pihole.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/pihole.example.org/privkey.pem;

    location / {
        proxy_pass http://pihole:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Pi-hole
# Checked against Pi-hole's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... pihole.example.org
  Scheme ................ http
  Forward Hostname / IP . pihole
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Pi-hole's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Pi-hole: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Pi-hole's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
pihole.example.org {
	reverse_proxy pihole:80
}

Traefik labels

# Pi-hole: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Pi-hole's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  pihole:
    labels:
      traefik.enable: "true"
      traefik.http.routers.pi-hole.rule: "Host(`pihole.example.org`)"
      traefik.http.routers.pi-hole.entrypoints: "websecure"
      traefik.http.routers.pi-hole.tls: "true"
      traefik.http.routers.pi-hole.tls.certresolver: "letsencrypt"
      traefik.http.routers.pi-hole.service: "pi-hole"
      traefik.http.services.pi-hole.loadbalancer.server.port: "80"

In Pi-hole itself

  1. Pi-hole docs: Docker (the compose example: port 80 is the "Default HTTP Port" of the web interface) checked 2026-09-29
  2. Pi-hole docs: Docker configuration (FTLCONF_ variables, the web interface password) checked 2026-09-29

Plex Media Server app page

Upstream plex:32400 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29

nginx

# Plex Media Server: nginx for plex.example.org
# App-specific lines are checked against Plex Media Server's docs (2026-09-29); [n] = source n below.
# Plex Media Server's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name plex.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name plex.example.org;
    ssl_certificate     /etc/letsencrypt/live/plex.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/plex.example.org/privkey.pem;

    location / {
        proxy_pass http://plex:32400;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Plex Media Server
# Checked against Plex Media Server's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... plex.example.org
  Scheme ................ http
  Forward Hostname / IP . plex
  Forward Port .......... 32400
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Plex Media Server's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Plex Media Server: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Plex Media Server's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
plex.example.org {
	reverse_proxy plex:32400
}

Traefik labels

# Plex Media Server: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Plex Media Server's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  plex:
    labels:
      traefik.enable: "true"
      traefik.http.routers.plex.rule: "Host(`plex.example.org`)"
      traefik.http.routers.plex.entrypoints: "websecure"
      traefik.http.routers.plex.tls: "true"
      traefik.http.routers.plex.tls.certresolver: "letsencrypt"
      traefik.http.routers.plex.service: "plex"
      traefik.http.services.plex.loadbalancer.server.port: "32400"

In Plex Media Server itself

  1. Plex support: Network settings (Custom server access URLs, for a reverse proxy in front of the media server) checked 2026-09-29
  2. plexinc/pms-docker README (32400 is the primary port; ADVERTISE_IP) checked 2026-09-29

Node-RED app page

Upstream node-red:1880 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29

nginx

# Node-RED: nginx for nodered.example.org
# App-specific lines are checked against Node-RED's docs (2026-09-29); [n] = source n below.
# Node-RED's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name nodered.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name nodered.example.org;
    ssl_certificate     /etc/letsencrypt/live/nodered.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/nodered.example.org/privkey.pem;

    location / {
        proxy_pass http://node-red:1880;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Node-RED
# Checked against Node-RED's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... nodered.example.org
  Scheme ................ http
  Forward Hostname / IP . node-red
  Forward Port .......... 1880
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Node-RED's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Node-RED: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Node-RED's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
nodered.example.org {
	reverse_proxy node-red:1880
}

Traefik labels

# Node-RED: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Node-RED's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  node-red:
    labels:
      traefik.enable: "true"
      traefik.http.routers.node-red.rule: "Host(`nodered.example.org`)"
      traefik.http.routers.node-red.entrypoints: "websecure"
      traefik.http.routers.node-red.tls: "true"
      traefik.http.routers.node-red.tls.certresolver: "letsencrypt"
      traefik.http.routers.node-red.service: "node-red"
      traefik.http.services.node-red.loadbalancer.server.port: "1880"

In Node-RED itself

  1. Node-RED docs: Securing Node-RED (the editor is not secured by default; adminAuth; hash-pw) checked 2026-09-29
  2. Node-RED docs: Running under Docker (port 1880, /data) checked 2026-09-29

Mosquitto app page

Upstream mosquitto:9001 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29

nginx

# Mosquitto: nginx for mqtt.example.org
# App-specific lines are checked against Mosquitto's docs (2026-09-29); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name mqtt.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name mqtt.example.org;
    ssl_certificate     /etc/letsencrypt/live/mqtt.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/mqtt.example.org/privkey.pem;

    location / {
        proxy_pass http://mosquitto:9001;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Mosquitto
# Checked against Mosquitto's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... mqtt.example.org
  Scheme ................ http
  Forward Hostname / IP . mosquitto
  Forward Port .......... 9001
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Mosquitto's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Mosquitto: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Mosquitto's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
mqtt.example.org {
	reverse_proxy mosquitto:9001
}

Traefik labels

# Mosquitto: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Mosquitto's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  mosquitto:
    labels:
      traefik.enable: "true"
      traefik.http.routers.mosquitto.rule: "Host(`mqtt.example.org`)"
      traefik.http.routers.mosquitto.entrypoints: "websecure"
      traefik.http.routers.mosquitto.tls: "true"
      traefik.http.routers.mosquitto.tls.certresolver: "letsencrypt"
      traefik.http.routers.mosquitto.service: "mosquitto"
      traefik.http.services.mosquitto.loadbalancer.server.port: "9001"

In Mosquitto itself

  1. Mosquitto docs: mosquitto.conf man page (listener, protocol websockets) checked 2026-09-29

Zigbee2MQTT app page

Upstream zigbee2mqtt:8080 · WebSockets: required on /api [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29

nginx

# Zigbee2MQTT: nginx for zigbee.example.org
# App-specific lines are checked against Zigbee2MQTT's docs (2026-09-29); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name zigbee.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name zigbee.example.org;
    ssl_certificate     /etc/letsencrypt/live/zigbee.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/zigbee.example.org/privkey.pem;

    location / {
        proxy_pass http://zigbee2mqtt:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # WebSocket traffic [1]
    location /api {
        proxy_pass http://zigbee2mqtt:8080;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Zigbee2MQTT
# Checked against Zigbee2MQTT's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... zigbee.example.org
  Scheme ................ http
  Forward Hostname / IP . zigbee2mqtt
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Zigbee2MQTT's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Zigbee2MQTT: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Zigbee2MQTT's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
zigbee.example.org {
	reverse_proxy zigbee2mqtt:8080
}

Traefik labels

# Zigbee2MQTT: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Zigbee2MQTT's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  zigbee2mqtt:
    labels:
      traefik.enable: "true"
      traefik.http.routers.zigbee2mqtt.rule: "Host(`zigbee.example.org`)"
      traefik.http.routers.zigbee2mqtt.entrypoints: "websecure"
      traefik.http.routers.zigbee2mqtt.tls: "true"
      traefik.http.routers.zigbee2mqtt.tls.certresolver: "letsencrypt"
      traefik.http.routers.zigbee2mqtt.service: "zigbee2mqtt"
      traefik.http.services.zigbee2mqtt.loadbalancer.server.port: "8080"

In Zigbee2MQTT itself

  1. Zigbee2MQTT docs: Frontend (Nginx proxy configuration, auth_token) checked 2026-09-29

Umami app page

Upstream umami:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29

nginx

# Umami: nginx for umami.example.org
# App-specific lines are checked against Umami's docs (2026-09-29); [n] = source n below.
# Umami's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name umami.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name umami.example.org;
    ssl_certificate     /etc/letsencrypt/live/umami.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/umami.example.org/privkey.pem;

    location / {
        proxy_pass http://umami:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Umami
# Checked against Umami's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... umami.example.org
  Scheme ................ http
  Forward Hostname / IP . umami
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Umami's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Umami: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Umami's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
umami.example.org {
	reverse_proxy umami:3000
}

Traefik labels

# Umami: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Umami's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  umami:
    labels:
      traefik.enable: "true"
      traefik.http.routers.umami.rule: "Host(`umami.example.org`)"
      traefik.http.routers.umami.entrypoints: "websecure"
      traefik.http.routers.umami.tls: "true"
      traefik.http.routers.umami.tls.certresolver: "letsencrypt"
      traefik.http.routers.umami.service: "umami"
      traefik.http.services.umami.loadbalancer.server.port: "3000"

In Umami itself

  1. Umami docs: Environment variables (CLIENT_IP_HEADER for a proxy with non-standard headers) checked 2026-09-29

Calibre-Web app page

Upstream calibre-web:8083 · WebSockets: not in the docs · Upload limit: 20M [1] · Timeouts: defaults · docs checked 2026-09-29

nginx

# Calibre-Web: nginx for ebooks.example.org
# App-specific lines are checked against Calibre-Web's docs (2026-09-29); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name ebooks.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name ebooks.example.org;
    ssl_certificate     /etc/letsencrypt/live/ebooks.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/ebooks.example.org/privkey.pem;

    client_max_body_size 20M; # [1]

    location / {
        proxy_pass http://calibre-web:8083;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Scheme $scheme; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Calibre-Web
# Checked against Calibre-Web's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... ebooks.example.org
  Scheme ................ http
  Forward Hostname / IP . calibre-web
  Forward Port .......... 8083
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 20M; # [1]
proxy_buffer_size 128k; # [1]
proxy_buffers 4 256k; # [1]
proxy_busy_buffers_size 256k; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    include conf.d/include/proxy.conf;
    proxy_set_header X-Scheme $scheme; # [1]
}
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.
  • The wiki's Nginx Proxy Manager section adds larger proxy buffers in the Advanced tab. [1]

Caddyfile

# Calibre-Web: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Calibre-Web's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
ebooks.example.org {
	reverse_proxy calibre-web:8083 {
		# [1]
		header_up X-Scheme https
	}
}

Traefik labels

# Calibre-Web: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Calibre-Web's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  calibre-web:
    labels:
      traefik.enable: "true"
      traefik.http.routers.calibre-web.rule: "Host(`ebooks.example.org`)"
      traefik.http.routers.calibre-web.entrypoints: "websecure"
      traefik.http.routers.calibre-web.tls: "true"
      traefik.http.routers.calibre-web.tls.certresolver: "letsencrypt"
      traefik.http.routers.calibre-web.service: "calibre-web"
      traefik.http.routers.calibre-web.middlewares: "calibre-web-scheme"
      traefik.http.services.calibre-web.loadbalancer.server.port: "8083"
      traefik.http.middlewares.calibre-web-scheme.headers.customrequestheaders.X-Scheme: "https"

In Calibre-Web itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Calibre-Web wiki: Setup Reverse Proxy (nginx: client_max_body_size 20M, Host $http_host, X-Scheme; Caddy: header_up X-Scheme https) checked 2026-09-29

Gitea app page

Upstream server:3000 · WebSockets: required [1] · Upload limit: 512M [1] · Timeouts: defaults · docs checked 2026-09-29

nginx

# Gitea: nginx for gitea.example.org
# App-specific lines are checked against Gitea's docs (2026-09-29); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name gitea.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name gitea.example.org;
    ssl_certificate     /etc/letsencrypt/live/gitea.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/gitea.example.org/privkey.pem;

    client_max_body_size 512M; # [1]

    location / {
        proxy_pass http://server:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $http_connection; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Gitea
# Checked against Gitea's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... gitea.example.org
  Scheme ................ http
  Forward Hostname / IP . server
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 512M; # [1]

Caddyfile

# Gitea: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Gitea's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
gitea.example.org {
	reverse_proxy server:3000
}

Traefik labels

# Gitea: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Gitea's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  server:
    labels:
      traefik.enable: "true"
      traefik.http.routers.gitea.rule: "Host(`gitea.example.org`)"
      traefik.http.routers.gitea.entrypoints: "websecure"
      traefik.http.routers.gitea.tls: "true"
      traefik.http.routers.gitea.tls.certresolver: "letsencrypt"
      traefik.http.routers.gitea.service: "gitea"
      traefik.http.services.gitea.loadbalancer.server.port: "3000"

In Gitea itself

  1. Gitea docs: Reverse Proxies (ROOT_URL, no URI decoding, nginx: client_max_body_size 512M, Connection $http_connection) checked 2026-09-29

Dozzle app page

Upstream dozzle:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29

nginx

# Dozzle: nginx for logs.example.org
# App-specific lines are checked against Dozzle's docs (2026-09-29); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name logs.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name logs.example.org;
    ssl_certificate     /etc/letsencrypt/live/logs.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/logs.example.org/privkey.pem;

    location / {
        proxy_pass http://dozzle:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        chunked_transfer_encoding off; # [1]
        proxy_buffering off; # [1]
        proxy_cache off; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Dozzle
# Checked against Dozzle's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... logs.example.org
  Scheme ................ http
  Forward Hostname / IP . dozzle
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

chunked_transfer_encoding off; # [1]
proxy_buffering off; # [1]
proxy_cache off; # [1]

Caddyfile

# Dozzle: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Dozzle's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
logs.example.org {
	reverse_proxy dozzle:8080 {
		# [1]
		flush_interval -1
	}
}

Traefik labels

# Dozzle: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Dozzle's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  dozzle:
    labels:
      traefik.enable: "true"
      traefik.http.routers.dozzle.rule: "Host(`logs.example.org`)"
      traefik.http.routers.dozzle.entrypoints: "websecure"
      traefik.http.routers.dozzle.tls: "true"
      traefik.http.routers.dozzle.tls.certresolver: "letsencrypt"
      traefik.http.routers.dozzle.service: "dozzle"
      traefik.http.services.dozzle.loadbalancer.server.port: "8080"
      # [1] Dozzle's page: Traefik handles the WebSocket upgrade itself, but a compress
      # middleware breaks the log stream; if you add one, exclude text/event-stream.

In Dozzle itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Dozzle docs: Reverse Proxy & Base Path (SSE needs buffering off; WebSocket for shells; nginx, Traefik and Caddy examples) checked 2026-09-29

Homarr app page

Upstream homarr:7575 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29

nginx

# Homarr: nginx for homarr.example.org
# App-specific lines are checked against Homarr's docs (2026-09-29); [n] = source n below.
# Homarr's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name homarr.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name homarr.example.org;
    ssl_certificate     /etc/letsencrypt/live/homarr.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/homarr.example.org/privkey.pem;

    location / {
        proxy_pass http://homarr:7575;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Homarr
# Checked against Homarr's docs (2026-09-29); [n] = source n below.

Details tab
  Domain Names .......... homarr.example.org
  Scheme ................ http
  Forward Hostname / IP . homarr
  Forward Port .......... 7575
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Homarr's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Homarr: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Homarr's docs (2026-09-29); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
homarr.example.org {
	reverse_proxy homarr:7575
}

Traefik labels

# Homarr: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Homarr's docs (2026-09-29); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  homarr:
    labels:
      traefik.enable: "true"
      traefik.http.routers.homarr.rule: "Host(`homarr.example.org`)"
      traefik.http.routers.homarr.entrypoints: "websecure"
      traefik.http.routers.homarr.tls: "true"
      traefik.http.routers.homarr.tls.certresolver: "letsencrypt"
      traefik.http.routers.homarr.service: "homarr"
      traefik.http.services.homarr.loadbalancer.server.port: "7575"

In Homarr itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Homarr docs: Proxies and Certificates (Caddy: reverse_proxy homarr:7575; Traefik: port 7575) checked 2026-09-29

SearXNG app page

Upstream core:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# SearXNG: nginx for search.example.org
# App-specific lines are checked against SearXNG's docs (2026-09-30); [n] = source n below.
# SearXNG's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name search.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name search.example.org;
    ssl_certificate     /etc/letsencrypt/live/search.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/search.example.org/privkey.pem;

    location / {
        proxy_pass http://core:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for SearXNG
# Checked against SearXNG's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... search.example.org
  Scheme ................ http
  Forward Hostname / IP . core
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: SearXNG's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# SearXNG: Caddyfile site block, the same one the dankhost builder writes.
# Checked against SearXNG's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
search.example.org {
	reverse_proxy core:8080
}

Traefik labels

# SearXNG: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against SearXNG's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  core:
    labels:
      traefik.enable: "true"
      traefik.http.routers.searxng.rule: "Host(`search.example.org`)"
      traefik.http.routers.searxng.entrypoints: "websecure"
      traefik.http.routers.searxng.tls: "true"
      traefik.http.routers.searxng.tls.certresolver: "letsencrypt"
      traefik.http.routers.searxng.service: "searxng"
      traefik.http.services.searxng.loadbalancer.server.port: "8080"

In SearXNG itself

  1. SearXNG docs: NGINX (proxy_pass example; X-Real-IP and X-Forwarded-For for bot detection; X-Script-Name for a sub-path) checked 2026-09-30
  2. SearXNG docs: settings.yml server: (base_url, $SEARXNG_BASE_URL) checked 2026-09-30

code-server app page

Upstream code-server:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# code-server: nginx for code.example.org
# App-specific lines are checked against code-server's docs (2026-09-30); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name code.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name code.example.org;
    ssl_certificate     /etc/letsencrypt/live/code.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/code.example.org/privkey.pem;

    location / {
        proxy_pass http://code-server:8080;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Accept-Encoding gzip; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection upgrade; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for code-server
# Checked against code-server's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... code.example.org
  Scheme ................ http
  Forward Hostname / IP . code-server
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    include conf.d/include/proxy.conf;
    proxy_set_header Accept-Encoding gzip; # [1]
}
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.

Caddyfile

# code-server: Caddyfile site block, the same one the dankhost builder writes.
# Checked against code-server's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
code.example.org {
	reverse_proxy code-server:8080
}

Traefik labels

# code-server: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against code-server's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  code-server:
    labels:
      traefik.enable: "true"
      traefik.http.routers.code-server.rule: "Host(`code.example.org`)"
      traefik.http.routers.code-server.entrypoints: "websecure"
      traefik.http.routers.code-server.tls: "true"
      traefik.http.routers.code-server.tls.certresolver: "letsencrypt"
      traefik.http.routers.code-server.service: "code-server"
      traefik.http.services.code-server.loadbalancer.server.port: "8080"

In code-server itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. code-server docs: Setup and configuration guide (Caddy and NGINX with Let's Encrypt) checked 2026-09-30
  2. code-server docs: Requirements ("Your environment must have WebSockets enabled") checked 2026-09-30

PrivateBin app page

Upstream privatebin:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# PrivateBin: nginx for paste.example.org
# App-specific lines are checked against PrivateBin's docs (2026-09-30); [n] = source n below.
# PrivateBin's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name paste.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name paste.example.org;
    ssl_certificate     /etc/letsencrypt/live/paste.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/paste.example.org/privkey.pem;

    location / {
        proxy_pass http://privatebin:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for PrivateBin
# Checked against PrivateBin's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... paste.example.org
  Scheme ................ http
  Forward Hostname / IP . privatebin
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: PrivateBin's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# PrivateBin: Caddyfile site block, the same one the dankhost builder writes.
# Checked against PrivateBin's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
paste.example.org {
	reverse_proxy privatebin:8080
}

Traefik labels

# PrivateBin: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against PrivateBin's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  privatebin:
    labels:
      traefik.enable: "true"
      traefik.http.routers.privatebin.rule: "Host(`paste.example.org`)"
      traefik.http.routers.privatebin.entrypoints: "websecure"
      traefik.http.routers.privatebin.tls: "true"
      traefik.http.routers.privatebin.tls.certresolver: "letsencrypt"
      traefik.http.routers.privatebin.service: "privatebin"
      traefik.http.services.privatebin.loadbalancer.server.port: "8080"

In PrivateBin itself

  1. PrivateBin image README (port 8080, reverse proxy for HTTPS, custom conf.php, 10 MiB upload default) checked 2026-09-30
  2. PrivateBin repository: cfg/conf.sample.php ([traffic] header for a reverse proxy) checked 2026-09-30

authentik app page

Upstream server:9000 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# authentik: nginx for sso.example.org
# App-specific lines are checked against authentik's docs (2026-09-30); [n] = source n below.

# WebSocket map [1]. It belongs in the http {} context, which conf.d files are.
# Leave it out if your nginx already defines $connection_upgrade.
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      "";
}

server {
    listen 80;
    listen [::]:80;
    server_name sso.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name sso.example.org;
    ssl_certificate     /etc/letsencrypt/live/sso.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/sso.example.org/privkey.pem;

    location / {
        proxy_pass http://server:9000;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $connection_upgrade; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for authentik
# Checked against authentik's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... sso.example.org
  Scheme ................ http
  Forward Hostname / IP . server
  Forward Port .......... 9000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.

Caddyfile

# authentik: Caddyfile site block, the same one the dankhost builder writes.
# Checked against authentik's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
sso.example.org {
	reverse_proxy server:9000
}

Traefik labels

# authentik: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against authentik's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  server:
    labels:
      traefik.enable: "true"
      traefik.http.routers.authentik.rule: "Host(`sso.example.org`)"
      traefik.http.routers.authentik.entrypoints: "websecure"
      traefik.http.routers.authentik.tls: "true"
      traefik.http.routers.authentik.tls.certresolver: "letsencrypt"
      traefik.http.routers.authentik.service: "authentik"
      traefik.http.services.authentik.loadbalancer.server.port: "9000"

In authentik itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. authentik docs: Reverse proxy (required headers, WebSockets, trusted proxy networks, nginx and Traefik examples) checked 2026-09-30

Radicale app page

Upstream radicale:5232 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# Radicale: nginx for dav.example.org
# App-specific lines are checked against Radicale's docs (2026-09-30); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name dav.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name dav.example.org;
    ssl_certificate     /etc/letsencrypt/live/dav.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/dav.example.org/privkey.pem;

    location / {
        proxy_pass http://radicale:5232;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $host; # [1]
        proxy_set_header X-Forwarded-Port $server_port; # [1]
        proxy_pass_header Authorization; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Radicale
# Checked against Radicale's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... dav.example.org
  Scheme ................ http
  Forward Hostname / IP . radicale
  Forward Port .......... 5232
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_pass_header Authorization; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Host $host; # [1]
    proxy_set_header X-Forwarded-Port $server_port; # [1]
}
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.

Caddyfile

# Radicale: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Radicale's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
dav.example.org {
	reverse_proxy radicale:5232
}

Traefik labels

# Radicale: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Radicale's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  radicale:
    labels:
      traefik.enable: "true"
      traefik.http.routers.radicale.rule: "Host(`dav.example.org`)"
      traefik.http.routers.radicale.entrypoints: "websecure"
      traefik.http.routers.radicale.tls: "true"
      traefik.http.routers.radicale.tls.certresolver: "letsencrypt"
      traefik.http.routers.radicale.service: "radicale"
      traefik.http.services.radicale.loadbalancer.server.port: "5232"

In Radicale itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Radicale documentation: Reverse Proxy (nginx example, X-Script-Name, proxy_pass_header Authorization) checked 2026-09-30

Karakeep app page

Upstream web:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# Karakeep: nginx for karakeep.example.org
# App-specific lines are checked against Karakeep's docs (2026-09-30); [n] = source n below.
# Karakeep's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name karakeep.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name karakeep.example.org;
    ssl_certificate     /etc/letsencrypt/live/karakeep.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/karakeep.example.org/privkey.pem;

    location / {
        proxy_pass http://web:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Karakeep
# Checked against Karakeep's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... karakeep.example.org
  Scheme ................ http
  Forward Hostname / IP . web
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Karakeep's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Karakeep: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Karakeep's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
karakeep.example.org {
	reverse_proxy web:3000
}

Traefik labels

# Karakeep: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Karakeep's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  web:
    labels:
      traefik.enable: "true"
      traefik.http.routers.karakeep.rule: "Host(`karakeep.example.org`)"
      traefik.http.routers.karakeep.entrypoints: "websecure"
      traefik.http.routers.karakeep.tls: "true"
      traefik.http.routers.karakeep.tls.certresolver: "letsencrypt"
      traefik.http.routers.karakeep.service: "karakeep"
      traefik.http.services.karakeep.loadbalancer.server.port: "3000"

In Karakeep itself

  1. Karakeep docs: Environment variables (NEXTAUTH_URL) checked 2026-09-30

wallabag app page

Upstream wallabag:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# wallabag: nginx for read.example.org
# App-specific lines are checked against wallabag's docs (2026-09-30); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name read.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name read.example.org;
    ssl_certificate     /etc/letsencrypt/live/read.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/read.example.org/privkey.pem;

    location / {
        proxy_pass http://wallabag:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $remote_addr; # [1]
        proxy_set_header X-Forwarded-Proto https; # [1]
        proxy_set_header X-Forwarded-Host $server_name; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for wallabag
# Checked against wallabag's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... read.example.org
  Scheme ................ http
  Forward Hostname / IP . wallabag
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Host $server_name; # [1]
    proxy_set_header X-Forwarded-Proto https; # [1]
    proxy_set_header X-Forwarded-For $remote_addr; # [1]
}

Caddyfile

# wallabag: Caddyfile site block, the same one the dankhost builder writes.
# Checked against wallabag's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
read.example.org {
	reverse_proxy wallabag:80
}

Traefik labels

# wallabag: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against wallabag's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  wallabag:
    labels:
      traefik.enable: "true"
      traefik.http.routers.wallabag.rule: "Host(`read.example.org`)"
      traefik.http.routers.wallabag.entrypoints: "websecure"
      traefik.http.routers.wallabag.tls: "true"
      traefik.http.routers.wallabag.tls.certresolver: "letsencrypt"
      traefik.http.routers.wallabag.service: "wallabag"
      traefik.http.services.wallabag.loadbalancer.server.port: "80"

In wallabag itself

  1. wallabag Docker image README: nginx (X-Forwarded-Host, X-Forwarded-Proto, X-Forwarded-For) and SYMFONY__ENV__DOMAIN_NAME checked 2026-09-30

IT-Tools app page

Upstream it-tools:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# IT-Tools: nginx for tools.example.org
# App-specific lines are checked against IT-Tools's docs (2026-09-30); [n] = source n below.
# IT-Tools's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name tools.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name tools.example.org;
    ssl_certificate     /etc/letsencrypt/live/tools.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/tools.example.org/privkey.pem;

    location / {
        proxy_pass http://it-tools:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for IT-Tools
# Checked against IT-Tools's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... tools.example.org
  Scheme ................ http
  Forward Hostname / IP . it-tools
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: IT-Tools's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# IT-Tools: Caddyfile site block, the same one the dankhost builder writes.
# Checked against IT-Tools's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
tools.example.org {
	reverse_proxy it-tools:80
}

Traefik labels

# IT-Tools: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against IT-Tools's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  it-tools:
    labels:
      traefik.enable: "true"
      traefik.http.routers.it-tools.rule: "Host(`tools.example.org`)"
      traefik.http.routers.it-tools.entrypoints: "websecure"
      traefik.http.routers.it-tools.tls: "true"
      traefik.http.routers.it-tools.tls.certresolver: "letsencrypt"
      traefik.http.routers.it-tools.service: "it-tools"
      traefik.http.services.it-tools.loadbalancer.server.port: "80"

In IT-Tools itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. IT-Tools README (Self host: docker run, port 80 in the container) checked 2026-09-30

HedgeDoc app page

Upstream app:3000 · WebSockets: required on /socket.io/ [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# HedgeDoc: nginx for pad.example.org
# App-specific lines are checked against HedgeDoc's docs (2026-09-30); [n] = source n below.

# WebSocket map [1]. It belongs in the http {} context, which conf.d files are.
# Leave it out if your nginx already defines $connection_upgrade.
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen 80;
    listen [::]:80;
    server_name pad.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name pad.example.org;
    ssl_certificate     /etc/letsencrypt/live/pad.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/pad.example.org/privkey.pem;

    location / {
        proxy_pass http://app:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # WebSocket traffic [1]
    location /socket.io/ {
        proxy_pass http://app:3000;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $connection_upgrade; # [1]
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for HedgeDoc
# Checked against HedgeDoc's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... pad.example.org
  Scheme ................ http
  Forward Hostname / IP . app
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: HedgeDoc's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# HedgeDoc: Caddyfile site block, the same one the dankhost builder writes.
# Checked against HedgeDoc's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
pad.example.org {
	reverse_proxy app:3000
}

Traefik labels

# HedgeDoc: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against HedgeDoc's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.hedgedoc.rule: "Host(`pad.example.org`)"
      traefik.http.routers.hedgedoc.entrypoints: "websecure"
      traefik.http.routers.hedgedoc.tls: "true"
      traefik.http.routers.hedgedoc.tls.certresolver: "letsencrypt"
      traefik.http.routers.hedgedoc.service: "hedgedoc"
      traefik.http.services.hedgedoc.loadbalancer.server.port: "3000"

In HedgeDoc itself

  1. HedgeDoc docs: Using a Reverse Proxy (CMD_DOMAIN, CMD_PROTOCOL_USESSL, CMD_URL_ADDPORT; nginx with /socket.io/) checked 2026-09-30

Seerr app page

Upstream seerr:5055 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30

nginx

# Seerr: nginx for requests.example.org
# App-specific lines are checked against Seerr's docs (2026-09-30); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name requests.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name requests.example.org;
    ssl_certificate     /etc/letsencrypt/live/requests.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/requests.example.org/privkey.pem;

    location / {
        proxy_pass http://seerr:5055;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Referer $http_referer; # [1]
        proxy_set_header X-Real-Port $remote_port; # [1]
        proxy_set_header X-Forwarded-Host $host:$remote_port; # [1]
        proxy_set_header X-Forwarded-Server $host; # [1]
        proxy_set_header X-Forwarded-Port $remote_port; # [1]
        proxy_set_header X-Forwarded-Ssl on; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Seerr
# Checked against Seerr's docs (2026-09-30); [n] = source n below.

Details tab
  Domain Names .......... requests.example.org
  Scheme ................ http
  Forward Hostname / IP . seerr
  Forward Port .......... 5055
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    include conf.d/include/proxy.conf;
    proxy_set_header Referer $http_referer; # [1]
    proxy_set_header X-Real-Port $remote_port; # [1]
    proxy_set_header X-Forwarded-Host $host:$remote_port; # [1]
    proxy_set_header X-Forwarded-Server $host; # [1]
    proxy_set_header X-Forwarded-Port $remote_port; # [1]
    proxy_set_header X-Forwarded-Ssl on; # [1]
}

Caddyfile

# Seerr: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Seerr's docs (2026-09-30); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
requests.example.org {
	reverse_proxy seerr:5055
}

Traefik labels

# Seerr: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Seerr's docs (2026-09-30); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  seerr:
    labels:
      traefik.enable: "true"
      traefik.http.routers.seerr.rule: "Host(`requests.example.org`)"
      traefik.http.routers.seerr.entrypoints: "websecure"
      traefik.http.routers.seerr.tls: "true"
      traefik.http.routers.seerr.tls.certresolver: "letsencrypt"
      traefik.http.routers.seerr.service: "seerr"
      traefik.http.services.seerr.loadbalancer.server.port: "5055"

In Seerr itself

  1. Seerr docs: Reverse Proxy (subdomain only; nginx headers) checked 2026-09-30
  2. Seerr docs: Network settings (Enable Proxy Support, off by default) checked 2026-09-30

FreshRSS app page

Upstream freshrss:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: 90 [1] · docs checked 2026-10-01

nginx

# FreshRSS: nginx for rss.example.org
# App-specific lines are checked against FreshRSS's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name rss.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name rss.example.org;
    ssl_certificate     /etc/letsencrypt/live/rss.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/rss.example.org/privkey.pem;

    proxy_read_timeout 90; # [1]

    location / {
        proxy_pass http://freshrss:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Port $server_port; # [1]
        proxy_set_header Authorization $http_authorization; # [1]
        proxy_redirect off; # [1]
        proxy_buffering off; # [1]
        proxy_pass_header Authorization; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for FreshRSS
# Checked against FreshRSS's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... rss.example.org
  Scheme ................ http
  Forward Hostname / IP . freshrss
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_read_timeout 90; # [1]
proxy_redirect off; # [1]
proxy_buffering off; # [1]
proxy_pass_header Authorization; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Port $server_port; # [1]
    proxy_set_header Authorization $http_authorization; # [1]
}

Caddyfile

# FreshRSS: Caddyfile site block, the same one the dankhost builder writes.
# Checked against FreshRSS's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
rss.example.org {
	reverse_proxy freshrss:80
}

Traefik labels

# FreshRSS: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against FreshRSS's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  freshrss:
    labels:
      traefik.enable: "true"
      traefik.http.routers.freshrss.rule: "Host(`rss.example.org`)"
      traefik.http.routers.freshrss.entrypoints: "websecure"
      traefik.http.routers.freshrss.tls: "true"
      traefik.http.routers.freshrss.tls.certresolver: "letsencrypt"
      traefik.http.routers.freshrss.service: "freshrss"
      traefik.http.services.freshrss.loadbalancer.server.port: "80"

In FreshRSS itself

  1. FreshRSS repository: Docker/README.md (nginx reverse proxy as domain root; TRUSTED_PROXY; Træfik Host() rule) checked 2026-10-01

Mealie app page

Upstream mealie:9000 · WebSockets: not in the docs · Upload limit: 0 [2] · Timeouts: defaults · docs checked 2026-10-01

nginx

# Mealie: nginx for recipes.example.org
# App-specific lines are checked against Mealie's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name recipes.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name recipes.example.org;
    ssl_certificate     /etc/letsencrypt/live/recipes.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/recipes.example.org/privkey.pem;

    client_max_body_size 0; # [2]

    location / {
        proxy_pass http://mealie:9000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Mealie
# Checked against Mealie's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... recipes.example.org
  Scheme ................ http
  Forward Hostname / IP . mealie
  Forward Port .......... 9000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 0; # [2]

Caddyfile

# Mealie: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Mealie's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
recipes.example.org {
	reverse_proxy mealie:9000
}

Traefik labels

# Mealie: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Mealie's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  mealie:
    labels:
      traefik.enable: "true"
      traefik.http.routers.mealie.rule: "Host(`recipes.example.org`)"
      traefik.http.routers.mealie.entrypoints: "websecure"
      traefik.http.routers.mealie.tls: "true"
      traefik.http.routers.mealie.tls.certresolver: "letsencrypt"
      traefik.http.routers.mealie.service: "mealie"
      traefik.http.services.mealie.loadbalancer.server.port: "9000"

In Mealie itself

  1. Mealie docs: Backend Configuration (BASE_URL, used for notifications and the OIDC callback URL; default http://localhost:8080) checked 2026-10-01
  2. Mealie docs, community guide: Reverse Proxy (SWAG) (client_max_body_size 0) checked 2026-10-01

Actual Budget app page

Upstream actual-server:5006 · WebSockets: not in the docs · Upload limit: 0 [1] · Timeouts: defaults · docs checked 2026-10-01

nginx

# Actual Budget: nginx for budget.example.org
# App-specific lines are checked against Actual Budget's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name budget.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name budget.example.org;
    ssl_certificate     /etc/letsencrypt/live/budget.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/budget.example.org/privkey.pem;

    client_max_body_size 0; # [1]

    location / {
        proxy_pass http://actual-server:5006;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Actual Budget
# Checked against Actual Budget's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... budget.example.org
  Scheme ................ http
  Forward Hostname / IP . actual-server
  Forward Port .......... 5006
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 0; # [1]

Caddyfile

# Actual Budget: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Actual Budget's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
budget.example.org {
	# [1]
	encode gzip zstd
	reverse_proxy actual-server:5006
}

Traefik labels

# Actual Budget: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Actual Budget's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  actual-server:
    labels:
      traefik.enable: "true"
      traefik.http.routers.actual.rule: "Host(`budget.example.org`)"
      traefik.http.routers.actual.entrypoints: "websecure"
      traefik.http.routers.actual.tls: "true"
      traefik.http.routers.actual.tls.certresolver: "letsencrypt"
      traefik.http.routers.actual.service: "actual"
      traefik.http.routers.actual.middlewares: "actual-compress"
      traefik.http.services.actual.loadbalancer.server.port: "5006"
      traefik.http.middlewares.actual-compress.compress.encodings: "gzip,zstd"

In Actual Budget itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Actual Budget docs: Using a Reverse Proxy (Caddy, Traefik and NGINX examples; COOP/COEP header note) checked 2026-10-01

Stirling-PDF app page

Upstream stirling-pdf:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Stirling-PDF: nginx for pdf.example.org
# App-specific lines are checked against Stirling-PDF's docs (2026-10-01); [n] = source n below.
# Stirling-PDF's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name pdf.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name pdf.example.org;
    ssl_certificate     /etc/letsencrypt/live/pdf.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/pdf.example.org/privkey.pem;

    location / {
        proxy_pass http://stirling-pdf:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Stirling-PDF
# Checked against Stirling-PDF's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... pdf.example.org
  Scheme ................ http
  Forward Hostname / IP . stirling-pdf
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Stirling-PDF's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Stirling-PDF: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Stirling-PDF's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
pdf.example.org {
	reverse_proxy stirling-pdf:8080
}

Traefik labels

# Stirling-PDF: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Stirling-PDF's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  stirling-pdf:
    labels:
      traefik.enable: "true"
      traefik.http.routers.stirling-pdf.rule: "Host(`pdf.example.org`)"
      traefik.http.routers.stirling-pdf.entrypoints: "websecure"
      traefik.http.routers.stirling-pdf.tls: "true"
      traefik.http.routers.stirling-pdf.tls.certresolver: "letsencrypt"
      traefik.http.routers.stirling-pdf.service: "stirling-pdf"
      traefik.http.services.stirling-pdf.loadbalancer.server.port: "8080"

In Stirling-PDF itself

  1. Stirling-PDF docs: Production Deployment Guide (Step 5, Reverse proxy integration; File Upload Limits) checked 2026-10-01

linkding app page

Upstream linkding:9090 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# linkding: nginx for bookmarks.example.org
# App-specific lines are checked against linkding's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name bookmarks.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name bookmarks.example.org;
    ssl_certificate     /etc/letsencrypt/live/bookmarks.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/bookmarks.example.org/privkey.pem;

    location / {
        proxy_pass http://linkding:9090;
        proxy_set_header Host $host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for linkding
# Checked against linkding's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... bookmarks.example.org
  Scheme ................ http
  Forward Hostname / IP . linkding
  Forward Port .......... 9090
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.

Caddyfile

# linkding: Caddyfile site block, the same one the dankhost builder writes.
# Checked against linkding's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
bookmarks.example.org {
	reverse_proxy linkding:9090
}

Traefik labels

# linkding: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against linkding's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  linkding:
    labels:
      traefik.enable: "true"
      traefik.http.routers.linkding.rule: "Host(`bookmarks.example.org`)"
      traefik.http.routers.linkding.entrypoints: "websecure"
      traefik.http.routers.linkding.tls: "true"
      traefik.http.routers.linkding.tls.certresolver: "letsencrypt"
      traefik.http.routers.linkding.service: "linkding"
      traefik.http.services.linkding.loadbalancer.server.port: "9090"

In linkding itself

  1. linkding repository: docs, Installation (Reverse Proxy Setup: Nginx needs Host $host and X-Forwarded-Proto $scheme) checked 2026-10-01
  2. linkding repository: docs, Options (LD_CSRF_TRUSTED_ORIGINS, LD_USE_X_FORWARDED_HOST) checked 2026-10-01

Miniflux app page

Upstream miniflux:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Miniflux: nginx for feeds.example.org
# App-specific lines are checked against Miniflux's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name feeds.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name feeds.example.org;
    ssl_certificate     /etc/letsencrypt/live/feeds.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/feeds.example.org/privkey.pem;

    location / {
        proxy_pass http://miniflux:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_redirect off; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Miniflux
# Checked against Miniflux's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... feeds.example.org
  Scheme ................ http
  Forward Hostname / IP . miniflux
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_redirect off; # [1]

Caddyfile

# Miniflux: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Miniflux's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
feeds.example.org {
	reverse_proxy miniflux:8080
}

Traefik labels

# Miniflux: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Miniflux's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  miniflux:
    labels:
      traefik.enable: "true"
      traefik.http.routers.miniflux.rule: "Host(`feeds.example.org`)"
      traefik.http.routers.miniflux.entrypoints: "websecure"
      traefik.http.routers.miniflux.tls: "true"
      traefik.http.routers.miniflux.tls.certresolver: "letsencrypt"
      traefik.http.routers.miniflux.service: "miniflux"
      traefik.http.services.miniflux.loadbalancer.server.port: "8080"

In Miniflux itself

  1. Miniflux docs: How-to, Reverse-Proxy Configuration (nginx example) checked 2026-10-01
  2. Miniflux docs: Configuration Parameters (BASE_URL, TRUSTED_REVERSE_PROXY_NETWORKS) checked 2026-10-01

Kavita app page

Upstream kavita:5000 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Kavita: nginx for library.example.org
# App-specific lines are checked against Kavita's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name library.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name library.example.org;
    ssl_certificate     /etc/letsencrypt/live/library.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/library.example.org/privkey.pem;

    location / {
        proxy_pass http://kavita:5000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "Upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Kavita
# Checked against Kavita's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... library.example.org
  Scheme ................ http
  Forward Hostname / IP . kavita
  Forward Port .......... 5000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Kavita's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Kavita: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Kavita's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
library.example.org {
	reverse_proxy kavita:5000
}

Traefik labels

# Kavita: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Kavita's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  kavita:
    labels:
      traefik.enable: "true"
      traefik.http.routers.kavita.rule: "Host(`library.example.org`)"
      traefik.http.routers.kavita.entrypoints: "websecure"
      traefik.http.routers.kavita.tls: "true"
      traefik.http.routers.kavita.tls.certresolver: "letsencrypt"
      traefik.http.routers.kavita.service: "kavita"
      traefik.http.services.kavita.loadbalancer.server.port: "5000"

In Kavita itself

  1. Kavita wiki: NGINX Example (Host and X headers, WebSocket headers) checked 2026-10-01
  2. Kavita wiki: NGINX Proxy Manager (Docker) example (Websockets Support enabled) checked 2026-10-01
  3. Kavita wiki: Remote Access (Additional Setup for Proxies Hosted Externally: KnownProxies) checked 2026-10-01

Ghost app page

Upstream ghost:2368 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Ghost: nginx for blog.example.org
# App-specific lines are checked against Ghost's docs (2026-10-01); [n] = source n below.
# Ghost's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name blog.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name blog.example.org;
    ssl_certificate     /etc/letsencrypt/live/blog.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/blog.example.org/privkey.pem;

    location / {
        proxy_pass http://ghost:2368;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Ghost
# Checked against Ghost's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... blog.example.org
  Scheme ................ http
  Forward Hostname / IP . ghost
  Forward Port .......... 2368
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Ghost's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Ghost: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Ghost's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
blog.example.org {
	# [2]
	encode gzip
	reverse_proxy ghost:2368
}

Traefik labels

# Ghost: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Ghost's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  ghost:
    labels:
      traefik.enable: "true"
      traefik.http.routers.ghost.rule: "Host(`blog.example.org`)"
      traefik.http.routers.ghost.entrypoints: "websecure"
      traefik.http.routers.ghost.tls: "true"
      traefik.http.routers.ghost.tls.certresolver: "letsencrypt"
      traefik.http.routers.ghost.service: "ghost"
      traefik.http.routers.ghost.middlewares: "ghost-compress"
      traefik.http.services.ghost.loadbalancer.server.port: "2368"
      traefik.http.middlewares.ghost-compress.compress.encodings: "gzip"

In Ghost itself

  1. Ghost docs: Configuration (url, required in production; always with https:// when using SSL) checked 2026-10-01
  2. ghost-docker repository: caddy/Caddyfile.example (reverse_proxy ghost:2368; optional encode gzip) checked 2026-10-01

BookStack app page

Upstream bookstack:80 · WebSockets: not in the docs · Upload limit: 100m [1] · Timeouts: defaults · docs checked 2026-10-01

nginx

# BookStack: nginx for bookstack.example.org
# App-specific lines are checked against BookStack's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name bookstack.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name bookstack.example.org;
    ssl_certificate     /etc/letsencrypt/live/bookstack.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/bookstack.example.org/privkey.pem;

    client_max_body_size 100m; # [1]
    client_body_timeout 120s; # [1]

    location / {
        proxy_pass http://bookstack:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for BookStack
# Checked against BookStack's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... bookstack.example.org
  Scheme ................ http
  Forward Hostname / IP . bookstack
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 100m; # [1]
client_body_timeout 120s; # [1]

Caddyfile

# BookStack: Caddyfile site block, the same one the dankhost builder writes.
# Checked against BookStack's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
bookstack.example.org {
	reverse_proxy bookstack:80
}

Traefik labels

# BookStack: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against BookStack's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  bookstack:
    labels:
      traefik.enable: "true"
      traefik.http.routers.bookstack.rule: "Host(`bookstack.example.org`)"
      traefik.http.routers.bookstack.entrypoints: "websecure"
      traefik.http.routers.bookstack.tls: "true"
      traefik.http.routers.bookstack.tls.certresolver: "letsencrypt"
      traefik.http.routers.bookstack.service: "bookstack"
      traefik.http.services.bookstack.loadbalancer.server.port: "80"

In BookStack itself

  1. BookStack docs: Upload Configuration (NGINX client_max_body_size 100m, client_body_timeout 120s) checked 2026-10-01
  2. BookStack docs: Security (APP_URL; Trusted Proxies, APP_PROXIES) checked 2026-10-01

Wiki.js app page

Upstream wiki:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Wiki.js: nginx for wiki.example.org
# App-specific lines are checked against Wiki.js's docs (2026-10-01); [n] = source n below.
# Wiki.js's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name wiki.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name wiki.example.org;
    ssl_certificate     /etc/letsencrypt/live/wiki.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/wiki.example.org/privkey.pem;

    location / {
        proxy_pass http://wiki:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Wiki.js
# Checked against Wiki.js's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... wiki.example.org
  Scheme ................ http
  Forward Hostname / IP . wiki
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Wiki.js's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Wiki.js: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Wiki.js's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
wiki.example.org {
	reverse_proxy wiki:3000
}

Traefik labels

# Wiki.js: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Wiki.js's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  wiki:
    labels:
      traefik.enable: "true"
      traefik.http.routers.wikijs.rule: "Host(`wiki.example.org`)"
      traefik.http.routers.wikijs.entrypoints: "websecure"
      traefik.http.routers.wikijs.tls: "true"
      traefik.http.routers.wikijs.tls.certresolver: "letsencrypt"
      traefik.http.routers.wikijs.service: "wikijs"
      traefik.http.services.wikijs.loadbalancer.server.port: "3000"

In Wiki.js itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Wiki.js docs: Docker (HTTPS section: built-in Let's Encrypt on port 3443) checked 2026-10-01
  2. Wiki.js repository: config.sample.yml (SSL/TLS settings: "Consider using a reverse proxy (e.g. nginx)") checked 2026-10-01

Memos app page

Upstream memos:5230 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Memos: nginx for memos.example.org
# App-specific lines are checked against Memos's docs (2026-10-01); [n] = source n below.
# Memos's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name memos.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name memos.example.org;
    ssl_certificate     /etc/letsencrypt/live/memos.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/memos.example.org/privkey.pem;

    location / {
        proxy_pass http://memos:5230;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Memos
# Checked against Memos's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... memos.example.org
  Scheme ................ http
  Forward Hostname / IP . memos
  Forward Port .......... 5230
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Memos's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Memos: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Memos's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
memos.example.org {
	reverse_proxy memos:5230
}

Traefik labels

# Memos: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Memos's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  memos:
    labels:
      traefik.enable: "true"
      traefik.http.routers.memos.rule: "Host(`memos.example.org`)"
      traefik.http.routers.memos.entrypoints: "websecure"
      traefik.http.routers.memos.tls: "true"
      traefik.http.routers.memos.tls.certresolver: "letsencrypt"
      traefik.http.routers.memos.service: "memos"
      traefik.http.services.memos.loadbalancer.server.port: "5230"

In Memos itself

  1. Memos docs: Reverse Proxy (MEMOS_INSTANCE_URL; forward Host, X-Forwarded-Proto and X-Forwarded-For) checked 2026-10-01

Vikunja app page

Upstream vikunja:3456 · WebSockets: required [1] · Upload limit: 20M [1] · Timeouts: defaults · docs checked 2026-10-01

nginx

# Vikunja: nginx for tasks.example.org
# App-specific lines are checked against Vikunja's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name tasks.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name tasks.example.org;
    ssl_certificate     /etc/letsencrypt/live/tasks.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/tasks.example.org/privkey.pem;

    client_max_body_size 20M; # [1]

    location / {
        proxy_pass http://vikunja:3456;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $http_connection; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Vikunja
# Checked against Vikunja's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... tasks.example.org
  Scheme ................ http
  Forward Hostname / IP . vikunja
  Forward Port .......... 3456
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 20M; # [1]

Caddyfile

# Vikunja: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Vikunja's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
tasks.example.org {
	reverse_proxy vikunja:3456
}

Traefik labels

# Vikunja: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Vikunja's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  vikunja:
    labels:
      traefik.enable: "true"
      traefik.http.routers.vikunja.rule: "Host(`tasks.example.org`)"
      traefik.http.routers.vikunja.entrypoints: "websecure"
      traefik.http.routers.vikunja.tls: "true"
      traefik.http.routers.vikunja.tls.certresolver: "letsencrypt"
      traefik.http.routers.vikunja.service: "vikunja"
      traefik.http.services.vikunja.loadbalancer.server.port: "3456"

In Vikunja itself

  1. Vikunja docs: Setup behind a reverse proxy (NGINX client_max_body_size 20M; NGINX Proxy Manager fields; Caddy) checked 2026-10-01

changedetection.io app page

Upstream changedetection:5000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# changedetection.io: nginx for watch.example.org
# App-specific lines are checked against changedetection.io's docs (2026-10-01); [n] = source n below.
# changedetection.io's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name watch.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name watch.example.org;
    ssl_certificate     /etc/letsencrypt/live/watch.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/watch.example.org/privkey.pem;

    location / {
        proxy_pass http://changedetection:5000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for changedetection.io
# Checked against changedetection.io's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... watch.example.org
  Scheme ................ http
  Forward Hostname / IP . changedetection
  Forward Port .......... 5000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: changedetection.io's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# changedetection.io: Caddyfile site block, the same one the dankhost builder writes.
# Checked against changedetection.io's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
watch.example.org {
	reverse_proxy changedetection:5000
}

Traefik labels

# changedetection.io: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against changedetection.io's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  changedetection:
    labels:
      traefik.enable: "true"
      traefik.http.routers.changedetection.rule: "Host(`watch.example.org`)"
      traefik.http.routers.changedetection.entrypoints: "websecure"
      traefik.http.routers.changedetection.tls: "true"
      traefik.http.routers.changedetection.tls.certresolver: "letsencrypt"
      traefik.http.routers.changedetection.service: "changedetection"
      traefik.http.services.changedetection.loadbalancer.server.port: "5000"

In changedetection.io itself

  1. changedetection.io wiki: Running changedetection.io behind a reverse proxy (USE_X_SETTINGS; nginx, Apache and Caddy examples) checked 2026-10-01
  2. changedetection.io repository: docker-compose.yml (BASE_URL, added to notification alerts; USE_X_SETTINGS) checked 2026-10-01

Authelia app page

Upstream authelia:9091 · WebSockets: not in the docs · Upload limit: not given · Timeouts: 360 [1] · docs checked 2026-10-01

nginx

# Authelia: nginx for auth.example.org
# App-specific lines are checked against Authelia's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name auth.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name auth.example.org;
    ssl_certificate     /etc/letsencrypt/live/auth.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/auth.example.org/privkey.pem;

    proxy_connect_timeout 360; # [1]
    proxy_read_timeout 360; # [1]
    proxy_send_timeout 360; # [1]
    client_body_buffer_size 128k; # [1]
    send_timeout 5m; # [1]

    location / {
        proxy_pass http://authelia:9091;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $remote_addr; # [1]
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Original-URL $scheme://$host$request_uri; # [1]
        proxy_set_header X-Forwarded-Host $host; # [1]
        proxy_set_header X-Forwarded-URI $request_uri; # [1]
        proxy_set_header X-Forwarded-Ssl on; # [1]
        proxy_http_version 1.1; # [1]
        proxy_redirect http:// $scheme://; # [1]
        proxy_cache_bypass $cookie_session; # [1]
        proxy_no_cache $cookie_session; # [1]
        proxy_buffers 64 256k; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Authelia
# Checked against Authelia's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... auth.example.org
  Scheme ................ http
  Forward Hostname / IP . authelia
  Forward Port .......... 9091
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_connect_timeout 360; # [1]
proxy_read_timeout 360; # [1]
proxy_send_timeout 360; # [1]
client_body_buffer_size 128k; # [1]
send_timeout 5m; # [1]
proxy_http_version 1.1; # [1]
proxy_redirect http:// $scheme://; # [1]
proxy_cache_bypass $cookie_session; # [1]
proxy_no_cache $cookie_session; # [1]
proxy_buffers 64 256k; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-For $remote_addr; # [1]
    proxy_set_header X-Original-URL $scheme://$host$request_uri; # [1]
    proxy_set_header X-Forwarded-Host $host; # [1]
    proxy_set_header X-Forwarded-URI $request_uri; # [1]
    proxy_set_header X-Forwarded-Ssl on; # [1]
}

Caddyfile

# Authelia: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Authelia's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
auth.example.org {
	reverse_proxy authelia:9091
}

Traefik labels

# Authelia: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Authelia's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  authelia:
    labels:
      traefik.enable: "true"
      traefik.http.routers.authelia.rule: "Host(`auth.example.org`)"
      traefik.http.routers.authelia.entrypoints: "websecure"
      traefik.http.routers.authelia.tls: "true"
      traefik.http.routers.authelia.tls.certresolver: "letsencrypt"
      traefik.http.routers.authelia.service: "authelia"
      traefik.http.services.authelia.loadbalancer.server.port: "9091"
      traefik.http.middlewares.authelia.forwardAuth.address: "http://authelia:9091/api/authz/forward-auth"
      traefik.http.middlewares.authelia.forwardAuth.trustForwardHeader: "true"
      traefik.http.middlewares.authelia.forwardAuth.maxResponseBodySize: "8192"
      traefik.http.middlewares.authelia.forwardAuth.authResponseHeaders: "Remote-User,Remote-Groups,Remote-Email,Remote-Name"

In Authelia itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Authelia docs: Integration, NGINX (auth.conf for the portal; proxy.conf Standard Variant; Trusted Proxies) checked 2026-10-01

wg-easy app page

Upstream wg-easy:51821 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# wg-easy: nginx for vpn.example.org
# App-specific lines are checked against wg-easy's docs (2026-10-01); [n] = source n below.
# wg-easy's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name vpn.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name vpn.example.org;
    ssl_certificate     /etc/letsencrypt/live/vpn.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/vpn.example.org/privkey.pem;

    location / {
        proxy_pass http://wg-easy:51821;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for wg-easy
# Checked against wg-easy's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... vpn.example.org
  Scheme ................ http
  Forward Hostname / IP . wg-easy
  Forward Port .......... 51821
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: wg-easy's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# wg-easy: Caddyfile site block, the same one the dankhost builder writes.
# Checked against wg-easy's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
vpn.example.org {
	reverse_proxy wg-easy:51821
}

Traefik labels

# wg-easy: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against wg-easy's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  wg-easy:
    labels:
      traefik.enable: "true"
      traefik.http.routers.wg-easy.rule: "Host(`vpn.example.org`)"
      traefik.http.routers.wg-easy.entrypoints: "websecure"
      traefik.http.routers.wg-easy.tls: "true"
      traefik.http.routers.wg-easy.tls.certresolver: "letsencrypt"
      traefik.http.routers.wg-easy.service: "wg-easy"
      traefik.http.services.wg-easy.loadbalancer.server.port: "51821"

In wg-easy itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. wg-easy docs: Traefik tutorial (loadbalancer.server.port=51821) checked 2026-10-01
  2. wg-easy docs: Caddy tutorial (reverse_proxy wg-easy:80 with PORT=80) checked 2026-10-01

Firefly III app page

Upstream app:8080 · WebSockets: not in the docs · Upload limit: 64M [1] · Timeouts: 300s [1] · docs checked 2026-10-01

nginx

# Firefly III: nginx for money.example.org
# App-specific lines are checked against Firefly III's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name money.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name money.example.org;
    ssl_certificate     /etc/letsencrypt/live/money.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/money.example.org/privkey.pem;

    client_max_body_size 64M; # [1]
    proxy_read_timeout 300s; # [1]
    proxy_buffer_size 128k; # [1]
    proxy_buffers 4 256k; # [1]
    proxy_busy_buffers_size 256k; # [1]

    location / {
        proxy_pass http://app:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $host; # [1]
        proxy_set_header X-Forwarded-Server $host; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Firefly III
# Checked against Firefly III's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... money.example.org
  Scheme ................ http
  Forward Hostname / IP . app
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 64M; # [1]
proxy_read_timeout 300s; # [1]
proxy_buffer_size 128k; # [1]
proxy_buffers 4 256k; # [1]
proxy_busy_buffers_size 256k; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Host $host; # [1]
    proxy_set_header X-Forwarded-Server $host; # [1]
}

Caddyfile

# Firefly III: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Firefly III's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
money.example.org {
	reverse_proxy app:8080
}

Traefik labels

# Firefly III: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Firefly III's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.firefly-iii.rule: "Host(`money.example.org`)"
      traefik.http.routers.firefly-iii.entrypoints: "websecure"
      traefik.http.routers.firefly-iii.tls: "true"
      traefik.http.routers.firefly-iii.tls.certresolver: "letsencrypt"
      traefik.http.routers.firefly-iii.service: "firefly-iii"
      traefik.http.services.firefly-iii.loadbalancer.server.port: "8080"

In Firefly III itself

  1. Firefly III docs: Installation FAQ (How do I set TLS: the nginx lines; reverse proxy in Docker: TRUSTED_PROXIES; 502 Bad Gateway: proxy buffers; 431 errors) checked 2026-10-01
  2. Firefly III docs: Docker FAQ (CSP errors and http links without TRUSTED_PROXIES; running under a subdirectory) checked 2026-10-01
  3. Firefly III repository: .env.example (TRUSTED_PROXIES, APP_URL) checked 2026-10-01

Tandoor Recipes app page

Upstream web_recipes:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Tandoor Recipes: nginx for tandoor.example.org
# App-specific lines are checked against Tandoor Recipes's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name tandoor.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name tandoor.example.org;
    ssl_certificate     /etc/letsencrypt/live/tandoor.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/tandoor.example.org/privkey.pem;

    location / {
        proxy_pass http://web_recipes:80;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Tandoor Recipes
# Checked against Tandoor Recipes's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... tandoor.example.org
  Scheme ................ http
  Forward Hostname / IP . web_recipes
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.

Caddyfile

# Tandoor Recipes: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Tandoor Recipes's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
tandoor.example.org {
	reverse_proxy web_recipes:80
}

Traefik labels

# Tandoor Recipes: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Tandoor Recipes's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  web_recipes:
    labels:
      traefik.enable: "true"
      traefik.http.routers.tandoor.rule: "Host(`tandoor.example.org`)"
      traefik.http.routers.tandoor.entrypoints: "websecure"
      traefik.http.routers.tandoor.tls: "true"
      traefik.http.routers.tandoor.tls.certresolver: "letsencrypt"
      traefik.http.routers.tandoor.service: "tandoor"
      traefik.http.services.tandoor.loadbalancer.server.port: "80"

In Tandoor Recipes itself

  1. Tandoor docs: Docker (Reverse Proxy; Required Headers: nginx Host $http_host and X-Forwarded-Proto) checked 2026-10-01
  2. Tandoor docs: FAQ (required headers and /system/ check, ALLAUTH_TRUSTED_PROXY_COUNT, CSRF errors) checked 2026-10-01
  3. Tandoor docs: Configuration (ALLOWED_HOSTS) checked 2026-10-01

Grocy app page

Upstream grocy:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Grocy: nginx for grocy.example.org
# App-specific lines are checked against Grocy's docs (2026-10-01); [n] = source n below.
# Grocy's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name grocy.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name grocy.example.org;
    ssl_certificate     /etc/letsencrypt/live/grocy.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/grocy.example.org/privkey.pem;

    location / {
        proxy_pass http://grocy:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Grocy
# Checked against Grocy's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... grocy.example.org
  Scheme ................ http
  Forward Hostname / IP . grocy
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Grocy's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Grocy: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Grocy's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
grocy.example.org {
	reverse_proxy grocy:80
}

Traefik labels

# Grocy: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Grocy's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  grocy:
    labels:
      traefik.enable: "true"
      traefik.http.routers.grocy.rule: "Host(`grocy.example.org`)"
      traefik.http.routers.grocy.entrypoints: "websecure"
      traefik.http.routers.grocy.tls: "true"
      traefik.http.routers.grocy.tls.certresolver: "letsencrypt"
      traefik.http.routers.grocy.service: "grocy"
      traefik.http.services.grocy.loadbalancer.server.port: "80"

In Grocy itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Grocy repository: config-dist.php (BASE_PATH, BASE_URL, ReverseProxyAuthMiddleware) checked 2026-10-01

Homepage app page

Upstream homepage:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Homepage: nginx for dash.example.org
# App-specific lines are checked against Homepage's docs (2026-10-01); [n] = source n below.
# Homepage's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name dash.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name dash.example.org;
    ssl_certificate     /etc/letsencrypt/live/dash.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/dash.example.org/privkey.pem;

    location / {
        proxy_pass http://homepage:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Homepage
# Checked against Homepage's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... dash.example.org
  Scheme ................ http
  Forward Hostname / IP . homepage
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Homepage's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Homepage: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Homepage's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
dash.example.org {
	reverse_proxy homepage:3000
}

Traefik labels

# Homepage: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Homepage's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  homepage:
    labels:
      traefik.enable: "true"
      traefik.http.routers.homepage.rule: "Host(`dash.example.org`)"
      traefik.http.routers.homepage.entrypoints: "websecure"
      traefik.http.routers.homepage.tls: "true"
      traefik.http.routers.homepage.tls.certresolver: "letsencrypt"
      traefik.http.routers.homepage.service: "homepage"
      traefik.http.services.homepage.loadbalancer.server.port: "3000"

In Homepage itself

  1. Homepage docs: Installation (HOMEPAGE_ALLOWED_HOSTS; Security & Authentication: HOMEPAGE_EXTERNAL_URL, rate limiting at the proxy) checked 2026-10-01

Kopia app page

Upstream kopia:51515 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Kopia: nginx for backup.example.org
# App-specific lines are checked against Kopia's docs (2026-10-01); [n] = source n below.
# Kopia's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name backup.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name backup.example.org;
    ssl_certificate     /etc/letsencrypt/live/backup.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/backup.example.org/privkey.pem;

    location / {
        proxy_pass http://kopia:51515;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Kopia
# Checked against Kopia's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... backup.example.org
  Scheme ................ http
  Forward Hostname / IP . kopia
  Forward Port .......... 51515
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Kopia's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Kopia: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Kopia's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
backup.example.org {
	reverse_proxy kopia:51515
}

Traefik labels

# Kopia: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Kopia's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  kopia:
    labels:
      traefik.enable: "true"
      traefik.http.routers.kopia.rule: "Host(`backup.example.org`)"
      traefik.http.routers.kopia.entrypoints: "websecure"
      traefik.http.routers.kopia.tls: "true"
      traefik.http.routers.kopia.tls.certresolver: "letsencrypt"
      traefik.http.routers.kopia.service: "kopia"
      traefik.http.services.kopia.loadbalancer.server.port: "51515"

In Kopia itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Kopia docs: Repository Server (Kopia behind a reverse proxy: nginx grpc_pass, TLS required) checked 2026-10-01

SiYuan app page

Upstream main:6806 · WebSockets: required on /ws [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# SiYuan: nginx for siyuan.example.org
# App-specific lines are checked against SiYuan's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name siyuan.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name siyuan.example.org;
    ssl_certificate     /etc/letsencrypt/live/siyuan.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/siyuan.example.org/privkey.pem;

    location / {
        proxy_pass http://main:6806;
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # WebSocket traffic [1]
    location /ws {
        proxy_pass http://main:6806;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
        proxy_set_header Host $http_host; # [1]
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for SiYuan
# Checked against SiYuan's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... siyuan.example.org
  Scheme ................ http
  Forward Hostname / IP . main
  Forward Port .......... 6806
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.

Caddyfile

# SiYuan: Caddyfile site block, the same one the dankhost builder writes.
# Checked against SiYuan's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
siyuan.example.org {
	reverse_proxy main:6806
}

Traefik labels

# SiYuan: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against SiYuan's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  main:
    labels:
      traefik.enable: "true"
      traefik.http.routers.siyuan.rule: "Host(`siyuan.example.org`)"
      traefik.http.routers.siyuan.entrypoints: "websecure"
      traefik.http.routers.siyuan.tls: "true"
      traefik.http.routers.siyuan.tls.certresolver: "letsencrypt"
      traefik.http.routers.siyuan.service: "siyuan"
      traefik.http.services.siyuan.loadbalancer.server.port: "6806"

In SiYuan itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. SiYuan README: Docker Hosting (Hidden port: NGINX reverse proxy, WebSocket on /ws, Host $http_host; Note: no URL rewriting) checked 2026-10-01

Reactive Resume app page

Upstream reactive-resume:3000 · WebSockets: required [1] · Upload limit: 10M [1] · Timeouts: 60s [1] · docs checked 2026-10-01

nginx

# Reactive Resume: nginx for resume.example.org
# App-specific lines are checked against Reactive Resume's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name resume.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name resume.example.org;
    ssl_certificate     /etc/letsencrypt/live/resume.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/resume.example.org/privkey.pem;

    client_max_body_size 10M; # [1]
    proxy_connect_timeout 60s; # [1]
    proxy_read_timeout 60s; # [1]
    proxy_send_timeout 60s; # [1]

    location / {
        proxy_pass http://reactive-resume:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_cache_bypass $http_upgrade; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Reactive Resume
# Checked against Reactive Resume's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... resume.example.org
  Scheme ................ http
  Forward Hostname / IP . reactive-resume
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 10M; # [1]
proxy_connect_timeout 60s; # [1]
proxy_read_timeout 60s; # [1]
proxy_send_timeout 60s; # [1]
proxy_cache_bypass $http_upgrade; # [1]

Caddyfile

# Reactive Resume: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Reactive Resume's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
resume.example.org {
	reverse_proxy reactive-resume:3000
}

Traefik labels

# Reactive Resume: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Reactive Resume's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  reactive-resume:
    labels:
      traefik.enable: "true"
      traefik.http.routers.reactive-resume.rule: "Host(`resume.example.org`)"
      traefik.http.routers.reactive-resume.entrypoints: "websecure"
      traefik.http.routers.reactive-resume.tls: "true"
      traefik.http.routers.reactive-resume.tls.certresolver: "letsencrypt"
      traefik.http.routers.reactive-resume.service: "reactive-resume"
      traefik.http.services.reactive-resume.loadbalancer.server.port: "3000"

In Reactive Resume itself

  1. Reactive Resume docs: Docker Compose examples (Docker with nginx: WebSocket headers, 60s timeouts, client_max_body_size 10M) checked 2026-10-01
  2. Reactive Resume docs: Self-hosting with Docker (APP_URL behind a reverse proxy) checked 2026-10-01

ToolJet app page

Upstream tooljet:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# ToolJet: nginx for tooljet.example.org
# App-specific lines are checked against ToolJet's docs (2026-10-01); [n] = source n below.
# ToolJet's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name tooljet.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name tooljet.example.org;
    ssl_certificate     /etc/letsencrypt/live/tooljet.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/tooljet.example.org/privkey.pem;

    location / {
        proxy_pass http://tooljet:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for ToolJet
# Checked against ToolJet's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... tooljet.example.org
  Scheme ................ http
  Forward Hostname / IP . tooljet
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: ToolJet's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# ToolJet: Caddyfile site block, the same one the dankhost builder writes.
# Checked against ToolJet's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
tooljet.example.org {
	reverse_proxy tooljet:80
}

Traefik labels

# ToolJet: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against ToolJet's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  tooljet:
    labels:
      traefik.enable: "true"
      traefik.http.routers.tooljet.rule: "Host(`tooljet.example.org`)"
      traefik.http.routers.tooljet.entrypoints: "websecure"
      traefik.http.routers.tooljet.tls: "true"
      traefik.http.routers.tooljet.tls.certresolver: "letsencrypt"
      traefik.http.routers.tooljet.service: "tooljet"
      traefik.http.services.tooljet.loadbalancer.server.port: "80"

In ToolJet itself

  1. ToolJet docs: Deploying ToolJet using Docker Compose (TOOLJET_HOST: public IP or custom domain, starting with http or https) checked 2026-10-01
  2. ToolJet docs: Connecting via HTTP proxy (TOOLJET_HTTP_PROXY, for outgoing requests) checked 2026-10-01

Appsmith app page

Upstream appsmith:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Appsmith: nginx for appsmith.example.org
# App-specific lines are checked against Appsmith's docs (2026-10-01); [n] = source n below.
# Appsmith's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name appsmith.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name appsmith.example.org;
    ssl_certificate     /etc/letsencrypt/live/appsmith.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/appsmith.example.org/privkey.pem;

    location / {
        proxy_pass http://appsmith:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Appsmith
# Checked against Appsmith's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... appsmith.example.org
  Scheme ................ http
  Forward Hostname / IP . appsmith
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Appsmith's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Appsmith: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Appsmith's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
appsmith.example.org {
	reverse_proxy appsmith:80
}

Traefik labels

# Appsmith: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Appsmith's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  appsmith:
    labels:
      traefik.enable: "true"
      traefik.http.routers.appsmith.rule: "Host(`appsmith.example.org`)"
      traefik.http.routers.appsmith.entrypoints: "websecure"
      traefik.http.routers.appsmith.tls: "true"
      traefik.http.routers.appsmith.tls.certresolver: "letsencrypt"
      traefik.http.routers.appsmith.service: "appsmith"
      traefik.http.services.appsmith.loadbalancer.server.port: "80"

In Appsmith itself

  1. Appsmith docs: Custom Domain and SSL (the internal Caddy; a certificate for the Custom Domain) checked 2026-10-01
  2. Appsmith docs: Environment variables (APPSMITH_BASE_URL, APPSMITH_CUSTOM_DOMAIN) checked 2026-10-01

Trilium Notes app page

Upstream trilium:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: 90 [1] · docs checked 2026-10-01

nginx

# Trilium Notes: nginx for trilium.example.org
# App-specific lines are checked against Trilium Notes's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name trilium.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name trilium.example.org;
    ssl_certificate     /etc/letsencrypt/live/trilium.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/trilium.example.org/privkey.pem;

    proxy_read_timeout 90; # [1]

    location / {
        proxy_pass http://trilium:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Trilium Notes
# Checked against Trilium Notes's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... trilium.example.org
  Scheme ................ http
  Forward Hostname / IP . trilium
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_read_timeout 90; # [1]

Caddyfile

# Trilium Notes: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Trilium Notes's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
trilium.example.org {
	reverse_proxy trilium:8080
}

Traefik labels

# Trilium Notes: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Trilium Notes's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  trilium:
    labels:
      traefik.enable: "true"
      traefik.http.routers.trilium.rule: "Host(`trilium.example.org`)"
      traefik.http.routers.trilium.entrypoints: "websecure"
      traefik.http.routers.trilium.tls: "true"
      traefik.http.routers.trilium.tls.certresolver: "letsencrypt"
      traefik.http.routers.trilium.service: "trilium"
      traefik.http.services.trilium.loadbalancer.server.port: "8080"
      # [4] Traefik 3.6.4 rejects some percent-encoded URLs Trilium uses (such as
      # search/%23workspace) with HTTP 400. Use Traefik 3.6.7 or later, or allow encoded slash
      # and hash on the entrypoint in the static configuration
      # (http.encodedCharacters.allowEncodedSlash and allowEncodedHash: true).

In Trilium Notes itself

  1. Trilium docs: Reverse proxy, Nginx (WebSocket headers, proxy_read_timeout 90) checked 2026-10-01
  2. Trilium docs: Reverse proxy (applies to every proxy; authentication proxies and the sync endpoints) checked 2026-10-01
  3. Trilium docs: Trusted proxy (trustedReverseProxy) checked 2026-10-01
  4. Trilium docs: Reverse proxy, Traefik (Traefik 3.6.4 and encoded characters; TRILIUM_NETWORK_TRUSTEDREVERSEPROXY) checked 2026-10-01

Khoj app page

Upstream server:42110 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Khoj: nginx for khoj.example.org
# App-specific lines are checked against Khoj's docs (2026-10-01); [n] = source n below.
# Khoj's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name khoj.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name khoj.example.org;
    ssl_certificate     /etc/letsencrypt/live/khoj.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/khoj.example.org/privkey.pem;

    location / {
        proxy_pass http://server:42110;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Khoj
# Checked against Khoj's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... khoj.example.org
  Scheme ................ http
  Forward Hostname / IP . server
  Forward Port .......... 42110
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Khoj's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Khoj: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Khoj's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
khoj.example.org {
	reverse_proxy server:42110
}

Traefik labels

# Khoj: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Khoj's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  server:
    labels:
      traefik.enable: "true"
      traefik.http.routers.khoj.rule: "Host(`khoj.example.org`)"
      traefik.http.routers.khoj.entrypoints: "websecure"
      traefik.http.routers.khoj.tls: "true"
      traefik.http.routers.khoj.tls.certresolver: "letsencrypt"
      traefik.http.routers.khoj.service: "khoj"
      traefik.http.services.khoj.loadbalancer.server.port: "42110"

In Khoj itself

  1. Khoj: docker-compose.yml (KHOJ_DOMAIN; KHOJ_ALLOWED_DOMAIN behind a reverse proxy; KHOJ_NO_HTTPS) checked 2026-10-01
  2. Khoj docs: Remote Access (KHOJ_DOMAIN, use HTTPS) checked 2026-10-01

Glance app page

Upstream glance:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Glance: nginx for glance.example.org
# App-specific lines are checked against Glance's docs (2026-10-01); [n] = source n below.
# Glance's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name glance.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name glance.example.org;
    ssl_certificate     /etc/letsencrypt/live/glance.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/glance.example.org/privkey.pem;

    location / {
        proxy_pass http://glance:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Glance
# Checked against Glance's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... glance.example.org
  Scheme ................ http
  Forward Hostname / IP . glance
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Glance's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Glance: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Glance's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
glance.example.org {
	reverse_proxy glance:8080
}

Traefik labels

# Glance: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Glance's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  glance:
    labels:
      traefik.enable: "true"
      traefik.http.routers.glance.rule: "Host(`glance.example.org`)"
      traefik.http.routers.glance.entrypoints: "websecure"
      traefik.http.routers.glance.tls: "true"
      traefik.http.routers.glance.tls.certresolver: "letsencrypt"
      traefik.http.routers.glance.service: "glance"
      traefik.http.services.glance.loadbalancer.server.port: "8080"

In Glance itself

  1. Glance docs: Configuration (server: proxied, base-url; Preventing brute-force attacks) checked 2026-10-01

QwenPaw app page

Upstream qwenpaw:8088 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# QwenPaw: nginx for qwenpaw.example.org
# App-specific lines are checked against QwenPaw's docs (2026-10-01); [n] = source n below.
# QwenPaw's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name qwenpaw.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name qwenpaw.example.org;
    ssl_certificate     /etc/letsencrypt/live/qwenpaw.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/qwenpaw.example.org/privkey.pem;

    location / {
        proxy_pass http://qwenpaw:8088;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for QwenPaw
# Checked against QwenPaw's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... qwenpaw.example.org
  Scheme ................ http
  Forward Hostname / IP . qwenpaw
  Forward Port .......... 8088
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: QwenPaw's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# QwenPaw: Caddyfile site block, the same one the dankhost builder writes.
# Checked against QwenPaw's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
qwenpaw.example.org {
	reverse_proxy qwenpaw:8088
}

Traefik labels

# QwenPaw: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against QwenPaw's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  qwenpaw:
    labels:
      traefik.enable: "true"
      traefik.http.routers.qwenpaw.rule: "Host(`qwenpaw.example.org`)"
      traefik.http.routers.qwenpaw.entrypoints: "websecure"
      traefik.http.routers.qwenpaw.tls: "true"
      traefik.http.routers.qwenpaw.tls.certresolver: "letsencrypt"
      traefik.http.routers.qwenpaw.service: "qwenpaw"
      traefik.http.services.qwenpaw.loadbalancer.server.port: "8088"

In QwenPaw itself

  1. QwenPaw docs: Security, Web Authentication (off by default; localhost bypass) checked 2026-10-01
  2. QwenPaw docs: Config (QWENPAW_AUTH_ENABLED; allow_no_auth_hosts) checked 2026-10-01
  3. QwenPaw docs: Quick start (POST /api/console/chat with SSE streaming) checked 2026-10-01

Langfuse app page

Upstream langfuse-web:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Langfuse: nginx for langfuse.example.org
# App-specific lines are checked against Langfuse's docs (2026-10-01); [n] = source n below.
# Langfuse's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name langfuse.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name langfuse.example.org;
    ssl_certificate     /etc/letsencrypt/live/langfuse.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/langfuse.example.org/privkey.pem;

    location / {
        proxy_pass http://langfuse-web:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Langfuse
# Checked against Langfuse's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... langfuse.example.org
  Scheme ................ http
  Forward Hostname / IP . langfuse-web
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Langfuse's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Langfuse: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Langfuse's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
langfuse.example.org {
	reverse_proxy langfuse-web:3000
}

Traefik labels

# Langfuse: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Langfuse's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  langfuse-web:
    labels:
      traefik.enable: "true"
      traefik.http.routers.langfuse.rule: "Host(`langfuse.example.org`)"
      traefik.http.routers.langfuse.entrypoints: "websecure"
      traefik.http.routers.langfuse.tls: "true"
      traefik.http.routers.langfuse.tls.certresolver: "letsencrypt"
      traefik.http.routers.langfuse.service: "langfuse"
      traefik.http.services.langfuse.loadbalancer.server.port: "3000"

In Langfuse itself

  1. Langfuse docs: Configuration (NEXTAUTH_URL; LANGFUSE_MCP_ALLOWED_HOSTS: prefer preserving the public host at the proxy) checked 2026-10-01
  2. Langfuse docs: Networking (only langfuse-web needs to be reachable; TLS at a load balancer) checked 2026-10-01
  3. Langfuse FAQ: Intermittent 502 and 504 network errors (KEEP_ALIVE_TIMEOUT) checked 2026-10-01
  4. Langfuse: docker-compose.yml (inbound ports 3000 and 9090; LANGFUSE_S3_MEDIA_UPLOAD_ENDPOINT) checked 2026-10-01

Plausible CE app page

Upstream plausible:8000 · WebSockets: required on /live/websocket [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01

nginx

# Plausible CE: nginx for plausible.example.org
# App-specific lines are checked against Plausible CE's docs (2026-10-01); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name plausible.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name plausible.example.org;
    ssl_certificate     /etc/letsencrypt/live/plausible.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/plausible.example.org/privkey.pem;

    location / {
        proxy_pass http://plausible:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # WebSocket traffic [1]
    location /live/websocket {
        proxy_pass http://plausible:8000;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "Upgrade"; # [1]
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Plausible CE
# Checked against Plausible CE's docs (2026-10-01); [n] = source n below.

Details tab
  Domain Names .......... plausible.example.org
  Scheme ................ http
  Forward Hostname / IP . plausible
  Forward Port .......... 8000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Plausible CE's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Plausible CE: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Plausible CE's docs (2026-10-01); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
plausible.example.org {
	reverse_proxy plausible:8000
}

Traefik labels

# Plausible CE: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Plausible CE's docs (2026-10-01); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  plausible:
    labels:
      traefik.enable: "true"
      traefik.http.routers.plausible.rule: "Host(`plausible.example.org`)"
      traefik.http.routers.plausible.entrypoints: "websecure"
      traefik.http.routers.plausible.tls: "true"
      traefik.http.routers.plausible.tls.certresolver: "letsencrypt"
      traefik.http.routers.plausible.service: "plausible"
      traefik.http.services.plausible.loadbalancer.server.port: "8000"

In Plausible CE itself

  1. Plausible CE wiki: Reverse proxy (HTTP_PORT; Caddy and Nginx examples, /live/websocket) checked 2026-10-01
  2. Plausible CE README at v3.2.1 (BASE_URL; HTTP_PORT=80 and HTTPS_PORT=443 turn on its own Let's Encrypt) checked 2026-10-01

ArchiveBox app page

Upstream archivebox:5797 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03

nginx

# ArchiveBox: nginx for archive.example.org
# App-specific lines are checked against ArchiveBox's docs (2026-10-03); [n] = source n below.
# ArchiveBox's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name archive.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name archive.example.org;
    ssl_certificate     /etc/letsencrypt/live/archive.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/archive.example.org/privkey.pem;

    location / {
        proxy_pass http://archivebox:5797;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for ArchiveBox
# Checked against ArchiveBox's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... archive.example.org
  Scheme ................ http
  Forward Hostname / IP . archivebox
  Forward Port .......... 5797
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: ArchiveBox's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# ArchiveBox: Caddyfile site block, the same one the dankhost builder writes.
# Checked against ArchiveBox's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
archive.example.org {
	reverse_proxy archivebox:5797
}

Traefik labels

# ArchiveBox: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against ArchiveBox's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  archivebox:
    labels:
      traefik.enable: "true"
      traefik.http.routers.archivebox.rule: "Host(`archive.example.org`)"
      traefik.http.routers.archivebox.entrypoints: "websecure"
      traefik.http.routers.archivebox.tls: "true"
      traefik.http.routers.archivebox.tls.certresolver: "letsencrypt"
      traefik.http.routers.archivebox.service: "archivebox"
      traefik.http.services.archivebox.loadbalancer.server.port: "5797"

In ArchiveBox itself

  1. ArchiveBox wiki: Docker (public HTTPS: single-domain mode, one certificate for the BASE_URL host, proxied to port 5797) checked 2026-10-03
  2. ArchiveBox wiki: Configuration (BASE_URL, SERVER_SECURITY_MODE and its five modes) checked 2026-10-03

Dashy app page

Upstream dashy:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03

nginx

# Dashy: nginx for dashy.example.org
# App-specific lines are checked against Dashy's docs (2026-10-03); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name dashy.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name dashy.example.org;
    ssl_certificate     /etc/letsencrypt/live/dashy.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/dashy.example.org/privkey.pem;

    location / {
        proxy_pass http://dashy:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_redirect off; # [1]
        proxy_buffering off; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Dashy
# Checked against Dashy's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... dashy.example.org
  Scheme ................ http
  Forward Hostname / IP . dashy
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_redirect off; # [1]
proxy_buffering off; # [1]

Caddyfile

# Dashy: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Dashy's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
dashy.example.org {
	reverse_proxy dashy:8080
}

Traefik labels

# Dashy: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Dashy's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  dashy:
    labels:
      traefik.enable: "true"
      traefik.http.routers.dashy.rule: "Host(`dashy.example.org`)"
      traefik.http.routers.dashy.entrypoints: "websecure"
      traefik.http.routers.dashy.tls: "true"
      traefik.http.routers.dashy.tls.certresolver: "letsencrypt"
      traefik.http.routers.dashy.service: "dashy"
      traefik.http.services.dashy.loadbalancer.server.port: "8080"

In Dashy itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Dashy docs: App Management (Custom Domain with an NGINX example and a Caddyfile; Network Exposure; Healthchecks) checked 2026-10-03

Beszel app page

Upstream beszel:8090 · WebSockets: required [1] · Upload limit: 10M [1] · Timeouts: 360s [1] · docs checked 2026-10-03

nginx

# Beszel: nginx for beszel.example.org
# App-specific lines are checked against Beszel's docs (2026-10-03); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name beszel.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name beszel.example.org;
    ssl_certificate     /etc/letsencrypt/live/beszel.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/beszel.example.org/privkey.pem;

    client_max_body_size 10M; # [1]
    proxy_read_timeout 360s; # [1]

    location / {
        proxy_pass http://beszel:8090;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Beszel
# Checked against Beszel's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... beszel.example.org
  Scheme ................ http
  Forward Hostname / IP . beszel
  Forward Port .......... 8090
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 10M; # [1]
proxy_read_timeout 360s; # [1]

Caddyfile

# Beszel: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Beszel's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
beszel.example.org {
	request_body {
		# [1]
		max_size 10MB
	}
	reverse_proxy beszel:8090 {
		transport http {
			# [1]
			read_timeout 360s
		}
	}
}

Traefik labels

# Beszel: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Beszel's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  beszel:
    labels:
      traefik.enable: "true"
      traefik.http.routers.beszel.rule: "Host(`beszel.example.org`)"
      traefik.http.routers.beszel.entrypoints: "websecure"
      traefik.http.routers.beszel.tls: "true"
      traefik.http.routers.beszel.tls.certresolver: "letsencrypt"
      traefik.http.routers.beszel.service: "beszel"
      traefik.http.services.beszel.loadbalancer.server.port: "8090"
      # [1] Beszel's own Traefik example sets no body-size or timeout label, so none is added
      # here; Traefik passes WebSocket connections without extra labels.

In Beszel itself

  1. Beszel docs: Reverse Proxy (WebSocket for agents with a universal token; APP_URL; Caddy and Nginx examples) checked 2026-10-03

NocoBase app page

Upstream app:80 · WebSockets: required [1] · Upload limit: not given · Timeouts: 600 [1] · docs checked 2026-10-03

nginx

# NocoBase: nginx for nocobase.example.org
# App-specific lines are checked against NocoBase's docs (2026-10-03); [n] = source n below.

# WebSocket map [1]. It belongs in the http {} context, which conf.d files are.
# Leave it out if your nginx already defines $connection_upgrade.
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen 80;
    listen [::]:80;
    server_name nocobase.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name nocobase.example.org;
    ssl_certificate     /etc/letsencrypt/live/nocobase.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/nocobase.example.org/privkey.pem;

    proxy_connect_timeout 600; # [1]
    proxy_read_timeout 600; # [1]
    proxy_send_timeout 600; # [1]

    location / {
        proxy_pass http://app:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        send_timeout 600; # [1]
        proxy_buffering off; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $connection_upgrade; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for NocoBase
# Checked against NocoBase's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... nocobase.example.org
  Scheme ................ http
  Forward Hostname / IP . app
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_connect_timeout 600; # [1]
proxy_read_timeout 600; # [1]
proxy_send_timeout 600; # [1]
send_timeout 600; # [1]
proxy_buffering off; # [1]

Caddyfile

# NocoBase: Caddyfile site block, the same one the dankhost builder writes.
# Checked against NocoBase's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
nocobase.example.org {
	reverse_proxy app:80
}

Traefik labels

# NocoBase: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against NocoBase's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.nocobase.rule: "Host(`nocobase.example.org`)"
      traefik.http.routers.nocobase.entrypoints: "websecure"
      traefik.http.routers.nocobase.tls: "true"
      traefik.http.routers.nocobase.tls.certresolver: "letsencrypt"
      traefik.http.routers.nocobase.service: "nocobase"
      traefik.http.services.nocobase.loadbalancer.server.port: "80"

In NocoBase itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. NocoBase docs: Docker Installation, Production deployment (Proxy the root path with Nginx) checked 2026-10-03

listmonk app page

Upstream app:9000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03

nginx

# listmonk: nginx for lists.example.org
# App-specific lines are checked against listmonk's docs (2026-10-03); [n] = source n below.
# listmonk's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name lists.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name lists.example.org;
    ssl_certificate     /etc/letsencrypt/live/lists.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/lists.example.org/privkey.pem;

    location / {
        proxy_pass http://app:9000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for listmonk
# Checked against listmonk's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... lists.example.org
  Scheme ................ http
  Forward Hostname / IP . app
  Forward Port .......... 9000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: listmonk's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# listmonk: Caddyfile site block, the same one the dankhost builder writes.
# Checked against listmonk's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
lists.example.org {
	reverse_proxy app:9000
}

Traefik labels

# listmonk: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against listmonk's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.listmonk.rule: "Host(`lists.example.org`)"
      traefik.http.routers.listmonk.entrypoints: "websecure"
      traefik.http.routers.listmonk.tls: "true"
      traefik.http.routers.listmonk.tls.certresolver: "letsencrypt"
      traefik.http.routers.listmonk.service: "listmonk"
      traefik.http.services.listmonk.loadbalancer.server.port: "9000"

In listmonk itself

  1. listmonk docs: Configuration (HTTP routes: private admin endpoints and public endpoints to expose to the internet) checked 2026-10-03
  2. listmonk: i18n/en.json (Settings > General > Root URL: "Public URL of the installation (no trailing slash)") checked 2026-10-03

Neko app page

Upstream neko:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03

nginx

# Neko: nginx for neko.example.org
# App-specific lines are checked against Neko's docs (2026-10-03); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name neko.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name neko.example.org;
    ssl_certificate     /etc/letsencrypt/live/neko.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/neko.example.org/privkey.pem;

    location / {
        proxy_pass http://neko:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Neko
# Checked against Neko's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... neko.example.org
  Scheme ................ http
  Forward Hostname / IP . neko
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Neko's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Neko: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Neko's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
neko.example.org {
	reverse_proxy neko:8080
}

Traefik labels

# Neko: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Neko's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  neko:
    labels:
      traefik.enable: "true"
      traefik.http.routers.neko.rule: "Host(`neko.example.org`)"
      traefik.http.routers.neko.entrypoints: "websecure"
      traefik.http.routers.neko.tls: "true"
      traefik.http.routers.neko.tls.certresolver: "letsencrypt"
      traefik.http.routers.neko.service: "neko"
      traefik.http.services.neko.loadbalancer.server.port: "8080"

In Neko itself

  1. Neko docs: Reverse Proxy Setup (server.proxy; WebSocket ping every 10 s, heartbeat every 120 s; Nginx and Caddy examples) checked 2026-10-03
  2. Neko docs: Configuration, server (server.proxy trusts X-Forwarded-For and X-Real-IP) checked 2026-10-03
  3. Neko docs: WebRTC Configuration (WebRTC cannot go through a reverse proxy) checked 2026-10-03

Linkwarden app page

Upstream linkwarden:3000 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03

nginx

# Linkwarden: nginx for links.example.org
# App-specific lines are checked against Linkwarden's docs (2026-10-03); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name links.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name links.example.org;
    ssl_certificate     /etc/letsencrypt/live/links.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/links.example.org/privkey.pem;

    location / {
        proxy_pass http://linkwarden:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $host; # [1]
        proxy_set_header Forwarded ""; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Linkwarden
# Checked against Linkwarden's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... links.example.org
  Scheme ................ http
  Forward Hostname / IP . linkwarden
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Host $host; # [1]
    proxy_set_header Forwarded ""; # [1]
}

Caddyfile

# Linkwarden: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Linkwarden's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
links.example.org {
	reverse_proxy linkwarden:3000
}

Traefik labels

# Linkwarden: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Linkwarden's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  linkwarden:
    labels:
      traefik.enable: "true"
      traefik.http.routers.linkwarden.rule: "Host(`links.example.org`)"
      traefik.http.routers.linkwarden.entrypoints: "websecure"
      traefik.http.routers.linkwarden.tls: "true"
      traefik.http.routers.linkwarden.tls.certresolver: "letsencrypt"
      traefik.http.routers.linkwarden.service: "linkwarden"
      traefik.http.services.linkwarden.loadbalancer.server.port: "3000"

In Linkwarden itself

  1. Linkwarden docs: Reverse Proxy (NGINX example; NEXTAUTH_URL and BASE_URL) checked 2026-10-03

ConvertX app page

Upstream convertx:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03

nginx

# ConvertX: nginx for convert.example.org
# App-specific lines are checked against ConvertX's docs (2026-10-03); [n] = source n below.
# ConvertX's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name convert.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name convert.example.org;
    ssl_certificate     /etc/letsencrypt/live/convert.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/convert.example.org/privkey.pem;

    location / {
        proxy_pass http://convertx:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for ConvertX
# Checked against ConvertX's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... convert.example.org
  Scheme ................ http
  Forward Hostname / IP . convertx
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: ConvertX's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# ConvertX: Caddyfile site block, the same one the dankhost builder writes.
# Checked against ConvertX's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
convert.example.org {
	reverse_proxy convertx:3000
}

Traefik labels

# ConvertX: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against ConvertX's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  convertx:
    labels:
      traefik.enable: "true"
      traefik.http.routers.convertx.rule: "Host(`convert.example.org`)"
      traefik.http.routers.convertx.entrypoints: "websecure"
      traefik.http.routers.convertx.tls: "true"
      traefik.http.routers.convertx.tls.certresolver: "letsencrypt"
      traefik.http.routers.convertx.service: "convertx"
      traefik.http.services.convertx.loadbalancer.server.port: "3000"

In ConvertX itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. ConvertX README (Deployment: log-in needs localhost or https unless HTTP_ALLOWED=true; WEBROOT) checked 2026-10-03

DocuSeal app page

Upstream app:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03

nginx

# DocuSeal: nginx for sign.example.org
# App-specific lines are checked against DocuSeal's docs (2026-10-03); [n] = source n below.
# DocuSeal's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name sign.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name sign.example.org;
    ssl_certificate     /etc/letsencrypt/live/sign.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/sign.example.org/privkey.pem;

    location / {
        proxy_pass http://app:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for DocuSeal
# Checked against DocuSeal's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... sign.example.org
  Scheme ................ http
  Forward Hostname / IP . app
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: DocuSeal's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# DocuSeal: Caddyfile site block, the same one the dankhost builder writes.
# Checked against DocuSeal's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
sign.example.org {
	reverse_proxy app:3000
}

Traefik labels

# DocuSeal: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against DocuSeal's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.docuseal.rule: "Host(`sign.example.org`)"
      traefik.http.routers.docuseal.entrypoints: "websecure"
      traefik.http.routers.docuseal.tls: "true"
      traefik.http.routers.docuseal.tls.certresolver: "letsencrypt"
      traefik.http.routers.docuseal.service: "docuseal"
      traefik.http.services.docuseal.loadbalancer.server.port: "3000"

In DocuSeal itself

  1. DocuSeal: docker-compose.yml (its own Caddy: caddy reverse-proxy --from $HOST --to app:3000; FORCE_SSL) checked 2026-10-03
  2. DocuSeal: config/environments/production.rb (FORCE_SSL sets assume_ssl and force_ssl) checked 2026-10-03

BentoPDF app page

Upstream bentopdf:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03

nginx

# BentoPDF: nginx for bentopdf.example.org
# App-specific lines are checked against BentoPDF's docs (2026-10-03); [n] = source n below.
# BentoPDF's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name bentopdf.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name bentopdf.example.org;
    ssl_certificate     /etc/letsencrypt/live/bentopdf.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/bentopdf.example.org/privkey.pem;

    location / {
        proxy_pass http://bentopdf:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for BentoPDF
# Checked against BentoPDF's docs (2026-10-03); [n] = source n below.

Details tab
  Domain Names .......... bentopdf.example.org
  Scheme ................ http
  Forward Hostname / IP . bentopdf
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: BentoPDF's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# BentoPDF: Caddyfile site block, the same one the dankhost builder writes.
# Checked against BentoPDF's docs (2026-10-03); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
bentopdf.example.org {
	reverse_proxy bentopdf:8080
}

Traefik labels

# BentoPDF: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against BentoPDF's docs (2026-10-03); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  bentopdf:
    labels:
      traefik.enable: "true"
      traefik.http.routers.bentopdf.rule: "Host(`bentopdf.example.org`)"
      traefik.http.routers.bentopdf.entrypoints: "websecure"
      traefik.http.routers.bentopdf.tls: "true"
      traefik.http.routers.bentopdf.tls.certresolver: "letsencrypt"
      traefik.http.routers.bentopdf.service: "bentopdf"
      traefik.http.services.bentopdf.loadbalancer.server.port: "8080"

In BentoPDF itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. BentoPDF README (nginx-unprivileged on port 8080; WASM from jsDelivr; Digital Signature CORS Proxy) checked 2026-10-03

Termix app page

Upstream termix:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08

nginx

# Termix: nginx for termix.example.org
# App-specific lines are checked against Termix's docs (2026-10-08); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name termix.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name termix.example.org;
    ssl_certificate     /etc/letsencrypt/live/termix.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/termix.example.org/privkey.pem;

    location / {
        proxy_pass http://termix:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Termix
# Checked against Termix's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... termix.example.org
  Scheme ................ http
  Forward Hostname / IP . termix
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Termix's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Termix: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Termix's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
termix.example.org {
	reverse_proxy termix:8080
}

Traefik labels

# Termix: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Termix's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  termix:
    labels:
      traefik.enable: "true"
      traefik.http.routers.termix.rule: "Host(`termix.example.org`)"
      traefik.http.routers.termix.entrypoints: "websecure"
      traefik.http.routers.termix.tls: "true"
      traefik.http.routers.termix.tls.certresolver: "letsencrypt"
      traefik.http.routers.termix.service: "termix"
      traefik.http.services.termix.loadbalancer.server.port: "8080"

In Termix itself

  1. Termix docs: Reverse Proxy (NGINX WebSocket upgrade, Traefik, Caddy) checked 2026-10-08
  2. Termix docs: Environment Variables (ALLOW_REGISTRATION, ALLOW_PASSWORD_RESET, EXTERNAL_FORCE_HTTPS) checked 2026-10-08

Documenso app page

Upstream documenso:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08

nginx

# Documenso: nginx for documenso.example.org
# App-specific lines are checked against Documenso's docs (2026-10-08); [n] = source n below.
# Documenso's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name documenso.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name documenso.example.org;
    ssl_certificate     /etc/letsencrypt/live/documenso.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/documenso.example.org/privkey.pem;

    location / {
        proxy_pass http://documenso:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Documenso
# Checked against Documenso's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... documenso.example.org
  Scheme ................ http
  Forward Hostname / IP . documenso
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Documenso's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Documenso: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Documenso's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
documenso.example.org {
	reverse_proxy documenso:3000
}

Traefik labels

# Documenso: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Documenso's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  documenso:
    labels:
      traefik.enable: "true"
      traefik.http.routers.documenso.rule: "Host(`documenso.example.org`)"
      traefik.http.routers.documenso.entrypoints: "websecure"
      traefik.http.routers.documenso.tls: "true"
      traefik.http.routers.documenso.tls.certresolver: "letsencrypt"
      traefik.http.routers.documenso.service: "documenso"
      traefik.http.services.documenso.loadbalancer.server.port: "3000"

In Documenso itself

  1. Documenso docs: Docker Compose (required variables, signing certificate, first account) checked 2026-10-08

MeTube app page

Upstream metube:8081 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08

nginx

# MeTube: nginx for metube.example.org
# App-specific lines are checked against MeTube's docs (2026-10-08); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name metube.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name metube.example.org;
    ssl_certificate     /etc/letsencrypt/live/metube.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/metube.example.org/privkey.pem;

    location / {
        proxy_pass http://metube:8081;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for MeTube
# Checked against MeTube's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... metube.example.org
  Scheme ................ http
  Forward Hostname / IP . metube
  Forward Port .......... 8081
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: MeTube's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# MeTube: Caddyfile site block, the same one the dankhost builder writes.
# Checked against MeTube's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
metube.example.org {
	reverse_proxy metube:8081
}

Traefik labels

# MeTube: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against MeTube's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  metube:
    labels:
      traefik.enable: "true"
      traefik.http.routers.metube.rule: "Host(`metube.example.org`)"
      traefik.http.routers.metube.entrypoints: "websecure"
      traefik.http.routers.metube.tls: "true"
      traefik.http.routers.metube.tls.certresolver: "letsencrypt"
      traefik.http.routers.metube.service: "metube"
      traefik.http.services.metube.loadbalancer.server.port: "8081"

In MeTube itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. MeTube wiki: Reverse proxy configurations (WebSocket for Socket.IO, URL_PREFIX) checked 2026-10-08

TREK app page

Upstream app:3000 · WebSockets: required on /ws [1] · Upload limit: 500m [1] · Timeouts: 86400 [1] · docs checked 2026-10-08

nginx

# TREK: nginx for trek.example.org
# App-specific lines are checked against TREK's docs (2026-10-08); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name trek.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name trek.example.org;
    ssl_certificate     /etc/letsencrypt/live/trek.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/trek.example.org/privkey.pem;

    client_max_body_size 500m; # [1]
    proxy_read_timeout 86400; # [1]

    location / {
        proxy_pass http://app:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # WebSocket traffic [1]
    location /ws {
        proxy_pass http://app:3000;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for TREK
# Checked against TREK's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... trek.example.org
  Scheme ................ http
  Forward Hostname / IP . app
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 500m; # [1]
proxy_read_timeout 86400; # [1]

Caddyfile

# TREK: Caddyfile site block, the same one the dankhost builder writes.
# Checked against TREK's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
trek.example.org {
	reverse_proxy app:3000
}

Traefik labels

# TREK: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against TREK's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.trek.rule: "Host(`trek.example.org`)"
      traefik.http.routers.trek.entrypoints: "websecure"
      traefik.http.routers.trek.tls: "true"
      traefik.http.routers.trek.tls.certresolver: "letsencrypt"
      traefik.http.routers.trek.service: "trek"
      traefik.http.services.trek.loadbalancer.server.port: "3000"

In TREK itself

  1. TREK wiki: Reverse Proxy (WebSocket on /ws, 500 MB bodies, Mcp-Session-Id) checked 2026-10-08

RomM app page

Upstream romm:8080 · WebSockets: required [1] · Upload limit: 0 [1] · Timeouts: defaults · docs checked 2026-10-08

nginx

# RomM: nginx for romm.example.org
# App-specific lines are checked against RomM's docs (2026-10-08); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name romm.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name romm.example.org;
    ssl_certificate     /etc/letsencrypt/live/romm.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/romm.example.org/privkey.pem;

    client_max_body_size 0; # [1]

    location / {
        proxy_pass http://romm:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for RomM
# Checked against RomM's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... romm.example.org
  Scheme ................ http
  Forward Hostname / IP . romm
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 0; # [1]

Caddyfile

# RomM: Caddyfile site block, the same one the dankhost builder writes.
# Checked against RomM's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
romm.example.org {
	reverse_proxy romm:8080
}

Traefik labels

# RomM: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against RomM's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  romm:
    labels:
      traefik.enable: "true"
      traefik.http.routers.romm.rule: "Host(`romm.example.org`)"
      traefik.http.routers.romm.entrypoints: "websecure"
      traefik.http.routers.romm.tls: "true"
      traefik.http.routers.romm.tls.certresolver: "letsencrypt"
      traefik.http.routers.romm.service: "romm"
      traefik.http.services.romm.loadbalancer.server.port: "8080"

In RomM itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. RomM docs: Reverse Proxy (port 8080, nginx WebSocket headers, client_max_body_size 0) checked 2026-10-08

PLANKA app page

Upstream planka:1337 · WebSockets: required [1] · Upload limit: 50M [1] · Timeouts: defaults · docs checked 2026-10-08

nginx

# PLANKA: nginx for planka.example.org
# App-specific lines are checked against PLANKA's docs (2026-10-08); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name planka.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name planka.example.org;
    ssl_certificate     /etc/letsencrypt/live/planka.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/planka.example.org/privkey.pem;

    client_max_body_size 50M; # [1]

    location / {
        proxy_pass http://planka:1337;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for PLANKA
# Checked against PLANKA's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... planka.example.org
  Scheme ................ http
  Forward Hostname / IP . planka
  Forward Port .......... 1337
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

client_max_body_size 50M; # [1]

Caddyfile

# PLANKA: Caddyfile site block, the same one the dankhost builder writes.
# Checked against PLANKA's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
planka.example.org {
	reverse_proxy planka:1337
}

Traefik labels

# PLANKA: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against PLANKA's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  planka:
    labels:
      traefik.enable: "true"
      traefik.http.routers.planka.rule: "Host(`planka.example.org`)"
      traefik.http.routers.planka.entrypoints: "websecure"
      traefik.http.routers.planka.tls: "true"
      traefik.http.routers.planka.tls.certresolver: "letsencrypt"
      traefik.http.routers.planka.service: "planka"
      traefik.http.services.planka.loadbalancer.server.port: "1337"

In PLANKA itself

  1. PLANKA docs: Reverse Proxy, Nginx (socket.io WebSocket, client_max_body_size 50M) checked 2026-10-08
  2. PLANKA docs: Reverse Proxy, Caddy (X-Forwarded-Proto, BASE_URL) checked 2026-10-08

Gatus app page

Upstream gatus:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08

nginx

# Gatus: nginx for gatus.example.org
# App-specific lines are checked against Gatus's docs (2026-10-08); [n] = source n below.
# Gatus's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name gatus.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name gatus.example.org;
    ssl_certificate     /etc/letsencrypt/live/gatus.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/gatus.example.org/privkey.pem;

    location / {
        proxy_pass http://gatus:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Gatus
# Checked against Gatus's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... gatus.example.org
  Scheme ................ http
  Forward Hostname / IP . gatus
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Gatus's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Gatus: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Gatus's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
gatus.example.org {
	reverse_proxy gatus:8080
}

Traefik labels

# Gatus: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Gatus's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  gatus:
    labels:
      traefik.enable: "true"
      traefik.http.routers.gatus.rule: "Host(`gatus.example.org`)"
      traefik.http.routers.gatus.entrypoints: "websecure"
      traefik.http.routers.gatus.tls: "true"
      traefik.http.routers.gatus.tls.certresolver: "letsencrypt"
      traefik.http.routers.gatus.service: "gatus"
      traefik.http.services.gatus.loadbalancer.server.port: "8080"

In Gatus itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Gatus README (web.port 8080; no reverse-proxy section) checked 2026-10-08

Homer app page

Upstream homer:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08

nginx

# Homer: nginx for homer.example.org
# App-specific lines are checked against Homer's docs (2026-10-08); [n] = source n below.
# Homer's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name homer.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name homer.example.org;
    ssl_certificate     /etc/letsencrypt/live/homer.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/homer.example.org/privkey.pem;

    location / {
        proxy_pass http://homer:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Homer
# Checked against Homer's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... homer.example.org
  Scheme ................ http
  Forward Hostname / IP . homer
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Homer's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Homer: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Homer's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
homer.example.org {
	reverse_proxy homer:8080
}

Traefik labels

# Homer: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Homer's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  homer:
    labels:
      traefik.enable: "true"
      traefik.http.routers.homer.rule: "Host(`homer.example.org`)"
      traefik.http.routers.homer.entrypoints: "websecure"
      traefik.http.routers.homer.tls: "true"
      traefik.http.routers.homer.tls.certresolver: "letsencrypt"
      traefik.http.routers.homer.service: "homer"
      traefik.http.services.homer.loadbalancer.server.port: "8080"

In Homer itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Homer README (PORT 8080; SUBFOLDER for a sub-path) checked 2026-10-08

Owncast app page

Upstream owncast:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08

nginx

# Owncast: nginx for owncast.example.org
# App-specific lines are checked against Owncast's docs (2026-10-08); [n] = source n below.

# WebSocket map [1]. It belongs in the http {} context, which conf.d files are.
# Leave it out if your nginx already defines $connection_upgrade.
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen 80;
    listen [::]:80;
    server_name owncast.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name owncast.example.org;
    ssl_certificate     /etc/letsencrypt/live/owncast.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/owncast.example.org/privkey.pem;

    proxy_pass_header Authorization; # [1]

    location / {
        proxy_pass http://owncast:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $host; # [1]
        proxy_set_header X-Forwarded-Server $host; # [1]
        proxy_set_header Authorization $http_authorization; # [1]
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection $connection_upgrade; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Owncast
# Checked against Owncast's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... owncast.example.org
  Scheme ................ http
  Forward Hostname / IP . owncast
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_pass_header Authorization; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Host $host; # [1]
    proxy_set_header X-Forwarded-Server $host; # [1]
    proxy_set_header Authorization $http_authorization; # [1]
}

Caddyfile

# Owncast: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Owncast's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
owncast.example.org {
	reverse_proxy owncast:8080
}

Traefik labels

# Owncast: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Owncast's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  owncast:
    labels:
      traefik.enable: "true"
      traefik.http.routers.owncast.rule: "Host(`owncast.example.org`)"
      traefik.http.routers.owncast.entrypoints: "websecure"
      traefik.http.routers.owncast.tls: "true"
      traefik.http.routers.owncast.tls.certresolver: "letsencrypt"
      traefik.http.routers.owncast.service: "owncast"
      traefik.http.services.owncast.loadbalancer.server.port: "8080"

In Owncast itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Owncast docs: NGINX (WebSocket map, Authorization header) checked 2026-10-08
  2. Owncast docs: SSL and reverse proxies (RTMP on 1935 does not go through the proxy; /ws for chat) checked 2026-10-08

Dawarich app page

Upstream dawarich_app:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08

nginx

# Dawarich: nginx for dawarich.example.org
# App-specific lines are checked against Dawarich's docs (2026-10-08); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name dawarich.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name dawarich.example.org;
    ssl_certificate     /etc/letsencrypt/live/dawarich.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/dawarich.example.org/privkey.pem;

    proxy_redirect off; # [1]

    location / {
        proxy_pass http://dawarich_app:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Server $host; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Dawarich
# Checked against Dawarich's docs (2026-10-08); [n] = source n below.

Details tab
  Domain Names .......... dawarich.example.org
  Scheme ................ http
  Forward Hostname / IP . dawarich_app
  Forward Port .......... 3000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_redirect off; # [1]
# NPM puts this text inside the server block, where proxy_set_header does not reach its own
# location /. So this location / replaces NPM's (an Access List on this host no longer applies).
location / {
    include conf.d/include/proxy.conf;
    proxy_set_header X-Forwarded-Server $host; # [1]
}

Caddyfile

# Dawarich: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Dawarich's docs (2026-10-08); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
dawarich.example.org {
	reverse_proxy dawarich_app:3000
}

Traefik labels

# Dawarich: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Dawarich's docs (2026-10-08); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  dawarich_app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.dawarich.rule: "Host(`dawarich.example.org`)"
      traefik.http.routers.dawarich.entrypoints: "websecure"
      traefik.http.routers.dawarich.tls: "true"
      traefik.http.routers.dawarich.tls.certresolver: "letsencrypt"
      traefik.http.routers.dawarich.service: "dawarich"
      traefik.http.services.dawarich.loadbalancer.server.port: "3000"

In Dawarich itself

  1. Dawarich docs: Setting Up Reverse Proxy (APPLICATION_HOSTS, nginx example) checked 2026-10-08

OmniTools app page

Upstream omni-tools:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09

nginx

# OmniTools: nginx for omni-tools.example.org
# App-specific lines are checked against OmniTools's docs (2026-10-09); [n] = source n below.
# OmniTools's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name omni-tools.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name omni-tools.example.org;
    ssl_certificate     /etc/letsencrypt/live/omni-tools.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/omni-tools.example.org/privkey.pem;

    location / {
        proxy_pass http://omni-tools:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for OmniTools
# Checked against OmniTools's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... omni-tools.example.org
  Scheme ................ http
  Forward Hostname / IP . omni-tools
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: OmniTools's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# OmniTools: Caddyfile site block, the same one the dankhost builder writes.
# Checked against OmniTools's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
omni-tools.example.org {
	reverse_proxy omni-tools:80
}

Traefik labels

# OmniTools: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against OmniTools's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  omni-tools:
    labels:
      traefik.enable: "true"
      traefik.http.routers.omni-tools.rule: "Host(`omni-tools.example.org`)"
      traefik.http.routers.omni-tools.entrypoints: "websecure"
      traefik.http.routers.omni-tools.tls: "true"
      traefik.http.routers.omni-tools.tls.certresolver: "letsencrypt"
      traefik.http.routers.omni-tools.service: "omni-tools"
      traefik.http.services.omni-tools.loadbalancer.server.port: "80"

In OmniTools itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. OmniTools README (Docker Compose, port 80, files processed in the browser) checked 2026-10-09

LibrePhotos app page

Upstream proxy:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09

nginx

# LibrePhotos: nginx for librephotos.example.org
# App-specific lines are checked against LibrePhotos's docs (2026-10-09); [n] = source n below.
# LibrePhotos's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name librephotos.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name librephotos.example.org;
    ssl_certificate     /etc/letsencrypt/live/librephotos.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/librephotos.example.org/privkey.pem;

    location / {
        proxy_pass http://proxy:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for LibrePhotos
# Checked against LibrePhotos's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... librephotos.example.org
  Scheme ................ http
  Forward Hostname / IP . proxy
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: LibrePhotos's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# LibrePhotos: Caddyfile site block, the same one the dankhost builder writes.
# Checked against LibrePhotos's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
librephotos.example.org {
	reverse_proxy proxy:80
}

Traefik labels

# LibrePhotos: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against LibrePhotos's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  proxy:
    labels:
      traefik.enable: "true"
      traefik.http.routers.librephotos.rule: "Host(`librephotos.example.org`)"
      traefik.http.routers.librephotos.entrypoints: "websecure"
      traefik.http.routers.librephotos.tls: "true"
      traefik.http.routers.librephotos.tls.certresolver: "letsencrypt"
      traefik.http.routers.librephotos.service: "librephotos"
      traefik.http.services.librephotos.loadbalancer.server.port: "80"

In LibrePhotos itself

  1. LibrePhotos: deploy/compose/docker-compose.yml (proxy, db, frontend, backend) checked 2026-10-09
  2. LibrePhotos docs: Single Container Deployment (Behind a reverse proxy: CSRF_TRUSTED_ORIGINS) checked 2026-10-09

Homebox app page

Upstream homebox:7745 · WebSockets: required [1] · Upload limit: not given · Timeouts: 86400 [1] · docs checked 2026-10-09

nginx

# Homebox: nginx for homebox.example.org
# App-specific lines are checked against Homebox's docs (2026-10-09); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name homebox.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name homebox.example.org;
    ssl_certificate     /etc/letsencrypt/live/homebox.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/homebox.example.org/privkey.pem;

    proxy_read_timeout 86400; # [1]

    location / {
        proxy_pass http://homebox:7745;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Homebox
# Checked against Homebox's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... homebox.example.org
  Scheme ................ http
  Forward Hostname / IP . homebox
  Forward Port .......... 7745
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_read_timeout 86400; # [1]

Caddyfile

# Homebox: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Homebox's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
homebox.example.org {
	reverse_proxy homebox:7745
}

Traefik labels

# Homebox: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Homebox's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  homebox:
    labels:
      traefik.enable: "true"
      traefik.http.routers.homebox.rule: "Host(`homebox.example.org`)"
      traefik.http.routers.homebox.entrypoints: "websecure"
      traefik.http.routers.homebox.tls: "true"
      traefik.http.routers.homebox.tls.certresolver: "letsencrypt"
      traefik.http.routers.homebox.service: "homebox"
      traefik.http.services.homebox.loadbalancer.server.port: "7745"

In Homebox itself

  1. Homebox docs: Proxying (HBOX_OPTIONS_TRUST_PROXY, nginx WebSocket example) checked 2026-10-09

Photoview app page

Upstream photoview:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09

nginx

# Photoview: nginx for photoview.example.org
# App-specific lines are checked against Photoview's docs (2026-10-09); [n] = source n below.
# Photoview's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name photoview.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name photoview.example.org;
    ssl_certificate     /etc/letsencrypt/live/photoview.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/photoview.example.org/privkey.pem;

    location / {
        proxy_pass http://photoview:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Photoview
# Checked against Photoview's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... photoview.example.org
  Scheme ................ http
  Forward Hostname / IP . photoview
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Photoview's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Photoview: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Photoview's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
photoview.example.org {
	reverse_proxy photoview:80
}

Traefik labels

# Photoview: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Photoview's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  photoview:
    labels:
      traefik.enable: "true"
      traefik.http.routers.photoview.rule: "Host(`photoview.example.org`)"
      traefik.http.routers.photoview.entrypoints: "websecure"
      traefik.http.routers.photoview.tls: "true"
      traefik.http.routers.photoview.tls.certresolver: "letsencrypt"
      traefik.http.routers.photoview.service: "photoview"
      traefik.http.services.photoview.loadbalancer.server.port: "80"

In Photoview itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Photoview docs: Reverse Proxy (Traefik labels, Caddy, Apache) checked 2026-10-09
  2. Photoview docs: Setup with Docker (port 80, media mounts read-only, tags, updating) checked 2026-10-09

SparkyFitness app page

Upstream sparkyfitness-frontend:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09

nginx

# SparkyFitness: nginx for sparkyfitness.example.org
# App-specific lines are checked against SparkyFitness's docs (2026-10-09); [n] = source n below.
# SparkyFitness's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name sparkyfitness.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name sparkyfitness.example.org;
    ssl_certificate     /etc/letsencrypt/live/sparkyfitness.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/sparkyfitness.example.org/privkey.pem;

    location / {
        proxy_pass http://sparkyfitness-frontend:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for SparkyFitness
# Checked against SparkyFitness's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... sparkyfitness.example.org
  Scheme ................ http
  Forward Hostname / IP . sparkyfitness-frontend
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: SparkyFitness's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# SparkyFitness: Caddyfile site block, the same one the dankhost builder writes.
# Checked against SparkyFitness's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
sparkyfitness.example.org {
	reverse_proxy sparkyfitness-frontend:80
}

Traefik labels

# SparkyFitness: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against SparkyFitness's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  sparkyfitness-frontend:
    labels:
      traefik.enable: "true"
      traefik.http.routers.sparkyfitness.rule: "Host(`sparkyfitness.example.org`)"
      traefik.http.routers.sparkyfitness.entrypoints: "websecure"
      traefik.http.routers.sparkyfitness.tls: "true"
      traefik.http.routers.sparkyfitness.tls.certresolver: "letsencrypt"
      traefik.http.routers.sparkyfitness.service: "sparkyfitness"
      traefik.http.services.sparkyfitness.loadbalancer.server.port: "80"

In SparkyFitness itself

  1. SparkyFitness docs: Reverse Proxy (headers, frontend container on port 80) checked 2026-10-09
  2. SparkyFitness docs: Environment Variables (frontend URL, admin email, sign-up, email) checked 2026-10-09

bitmagnet app page

Upstream bitmagnet:3333 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09

nginx

# bitmagnet: nginx for bitmagnet.example.org
# App-specific lines are checked against bitmagnet's docs (2026-10-09); [n] = source n below.
# bitmagnet's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name bitmagnet.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name bitmagnet.example.org;
    ssl_certificate     /etc/letsencrypt/live/bitmagnet.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/bitmagnet.example.org/privkey.pem;

    location / {
        proxy_pass http://bitmagnet:3333;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for bitmagnet
# Checked against bitmagnet's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... bitmagnet.example.org
  Scheme ................ http
  Forward Hostname / IP . bitmagnet
  Forward Port .......... 3333
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: bitmagnet's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# bitmagnet: Caddyfile site block, the same one the dankhost builder writes.
# Checked against bitmagnet's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
bitmagnet.example.org {
	reverse_proxy bitmagnet:3333
}

Traefik labels

# bitmagnet: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against bitmagnet's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  bitmagnet:
    labels:
      traefik.enable: "true"
      traefik.http.routers.bitmagnet.rule: "Host(`bitmagnet.example.org`)"
      traefik.http.routers.bitmagnet.entrypoints: "websecure"
      traefik.http.routers.bitmagnet.tls: "true"
      traefik.http.routers.bitmagnet.tls.certresolver: "letsencrypt"
      traefik.http.routers.bitmagnet.service: "bitmagnet"
      traefik.http.services.bitmagnet.loadbalancer.server.port: "3333"

In bitmagnet itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. bitmagnet docs: Installation (minimal docker-compose.yml, ports 3333 and 3334, upgrading) checked 2026-10-09
  2. bitmagnet docs: FAQ (not a public service, VPN, system requirements) checked 2026-10-09

13ft app page

Upstream 13ft:5000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09

nginx

# 13ft: nginx for 13ft.example.org
# App-specific lines are checked against 13ft's docs (2026-10-09); [n] = source n below.
# 13ft's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name 13ft.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name 13ft.example.org;
    ssl_certificate     /etc/letsencrypt/live/13ft.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/13ft.example.org/privkey.pem;

    location / {
        proxy_pass http://13ft:5000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for 13ft
# Checked against 13ft's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... 13ft.example.org
  Scheme ................ http
  Forward Hostname / IP . 13ft
  Forward Port .......... 5000
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: 13ft's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# 13ft: Caddyfile site block, the same one the dankhost builder writes.
# Checked against 13ft's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
13ft.example.org {
	reverse_proxy 13ft:5000
}

Traefik labels

# 13ft: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against 13ft's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  13ft:
    labels:
      traefik.enable: "true"
      traefik.http.routers.13ft.rule: "Host(`13ft.example.org`)"
      traefik.http.routers.13ft.entrypoints: "websecure"
      traefik.http.routers.13ft.tls: "true"
      traefik.http.routers.13ft.tls.certresolver: "letsencrypt"
      traefik.http.routers.13ft.service: "13ft"
      traefik.http.services.13ft.loadbalancer.server.port: "5000"

In 13ft itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. 13ft README (how it works: poses as GoogleBot; Docker; reverse proxy) checked 2026-10-09

Moodist app page

Upstream moodist:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09

nginx

# Moodist: nginx for moodist.example.org
# App-specific lines are checked against Moodist's docs (2026-10-09); [n] = source n below.
# Moodist's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name moodist.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name moodist.example.org;
    ssl_certificate     /etc/letsencrypt/live/moodist.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/moodist.example.org/privkey.pem;

    location / {
        proxy_pass http://moodist:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for Moodist
# Checked against Moodist's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... moodist.example.org
  Scheme ................ http
  Forward Hostname / IP . moodist
  Forward Port .......... 8080
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: Moodist's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# Moodist: Caddyfile site block, the same one the dankhost builder writes.
# Checked against Moodist's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
moodist.example.org {
	reverse_proxy moodist:8080
}

Traefik labels

# Moodist: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against Moodist's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  moodist:
    labels:
      traefik.enable: "true"
      traefik.http.routers.moodist.rule: "Host(`moodist.example.org`)"
      traefik.http.routers.moodist.entrypoints: "websecure"
      traefik.http.routers.moodist.tls: "true"
      traefik.http.routers.moodist.tls.certresolver: "letsencrypt"
      traefik.http.routers.moodist.service: "moodist"
      traefik.http.services.moodist.loadbalancer.server.port: "8080"

In Moodist itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. Moodist README (features, Self-Hosting with Docker Compose) checked 2026-10-09
  2. Moodist: Dockerfile (static Astro build served by Caddy on 8080) checked 2026-10-09

OliveTin app page

Upstream olivetin:1337 · WebSockets: required on /websocket [1] · Upload limit: not given · Timeouts: 600s [1] · docs checked 2026-10-09

nginx

# OliveTin: nginx for olivetin.example.org
# App-specific lines are checked against OliveTin's docs (2026-10-09); [n] = source n below.

server {
    listen 80;
    listen [::]:80;
    server_name olivetin.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name olivetin.example.org;
    ssl_certificate     /etc/letsencrypt/live/olivetin.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/olivetin.example.org/privkey.pem;

    proxy_read_timeout 600s; # [1]
    proxy_send_timeout 600s; # [1]

    location / {
        proxy_pass http://olivetin:1337;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # WebSocket traffic [1]
    location /websocket {
        proxy_pass http://olivetin:1337;
        proxy_http_version 1.1; # [1]
        proxy_set_header Upgrade $http_upgrade; # [1]
        proxy_set_header Connection "upgrade"; # [1]
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for OliveTin
# Checked against OliveTin's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... olivetin.example.org
  Scheme ................ http
  Forward Hostname / IP . olivetin
  Forward Port .......... 1337
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... on  # [1]

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

proxy_read_timeout 600s; # [1]
proxy_send_timeout 600s; # [1]

Caddyfile

# OliveTin: Caddyfile site block, the same one the dankhost builder writes.
# Checked against OliveTin's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
olivetin.example.org {
	reverse_proxy olivetin:1337
}

Traefik labels

# OliveTin: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against OliveTin's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  olivetin:
    labels:
      traefik.enable: "true"
      traefik.http.routers.olivetin.rule: "Host(`olivetin.example.org`)"
      traefik.http.routers.olivetin.entrypoints: "websecure"
      traefik.http.routers.olivetin.tls: "true"
      traefik.http.routers.olivetin.tls.certresolver: "letsencrypt"
      traefik.http.routers.olivetin.service: "olivetin"
      traefik.http.services.olivetin.loadbalancer.server.port: "1337"

In OliveTin itself

No app-side setting for a reverse proxy. The project documents nothing more.

  1. OliveTin docs: Nginx (WebSocket on /websocket) checked 2026-10-09
  2. OliveTin docs: Caddy (plain reverse_proxy works for its WebSockets) checked 2026-10-09

AdventureLog app page

Upstream app:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09

nginx

# AdventureLog: nginx for adventurelog.example.org
# App-specific lines are checked against AdventureLog's docs (2026-10-09); [n] = source n below.
# AdventureLog's docs give no nginx setting beyond the generic lines. The project documents nothing more.

server {
    listen 80;
    listen [::]:80;
    server_name adventurelog.example.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name adventurelog.example.org;
    ssl_certificate     /etc/letsencrypt/live/adventurelog.example.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/adventurelog.example.org/privkey.pem;

    location / {
        proxy_pass http://app:80;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Nginx Proxy Manager

# Nginx Proxy Manager: Hosts > Proxy Hosts > Add Proxy Host, for AdventureLog
# Checked against AdventureLog's docs (2026-10-09); [n] = source n below.

Details tab
  Domain Names .......... adventurelog.example.org
  Scheme ................ http
  Forward Hostname / IP . app
  Forward Port .......... 80
  Cache Assets .......... off
  Block Common Exploits . on
  Websockets Support .... off (the docs ask for no WebSocket headers)

SSL tab
  SSL Certificate ....... Request a new SSL Certificate
  Force SSL ............. on
  HTTP/2 Support ........ on

Advanced tab: Custom Nginx Configuration

# Nothing to add: AdventureLog's docs give no setting beyond NPM's defaults. The project documents nothing more.

Caddyfile

# AdventureLog: Caddyfile site block, the same one the dankhost builder writes.
# Checked against AdventureLog's docs (2026-10-09); [n] = source n below.
# Caddy passes WebSockets and sets X-Forwarded-For/-Proto/-Host by itself.
adventurelog.example.org {
	reverse_proxy app:80
}

Traefik labels

# AdventureLog: Traefik v3 labels, the same ones the dankhost builder writes.
# Checked against AdventureLog's docs (2026-10-09); [n] = source n below.
# "websecure" and "letsencrypt" are the builder's entrypoint and resolver names: use yours.
# Traefik must share a Docker network with the container; it passes WebSockets by itself.
services:
  app:
    labels:
      traefik.enable: "true"
      traefik.http.routers.adventurelog.rule: "Host(`adventurelog.example.org`)"
      traefik.http.routers.adventurelog.entrypoints: "websecure"
      traefik.http.routers.adventurelog.tls: "true"
      traefik.http.routers.adventurelog.tls.certresolver: "letsencrypt"
      traefik.http.routers.adventurelog.service: "adventurelog"
      traefik.http.services.adventurelog.loadbalancer.server.port: "80"

In AdventureLog itself

  1. AdventureLog docs: Standard Deployment (one container, 2 GB RAM on first boot, updating) checked 2026-10-09
  2. AdventureLog docs: Installation with Caddy checked 2026-10-09

The proxies' own documentation

The generic lines in every block (the listen, certificate and header lines of the nginx blocks, the Nginx Proxy Manager field names, Caddy's and Traefik's defaults) come from these.

nginx

Nginx Proxy Manager

Caddy

Traefik

The Caddy and Traefik blocks are generated from the same data as the builder, so a file built there and a block copied here say the same thing. The one exception is marked in its section: nothing on this page turns off certificate checking toward the app.

Made with AI tools. · Privacy