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.
- Immich
- Nextcloud
- Home Assistant
- Vaultwarden
- Jellyfin
- Paperless-ngx
- Uptime Kuma
- Audiobookshelf
- Navidrome
- PhotoPrism
- Syncthing
- n8n
- Open WebUI
- Grafana
- Forgejo
- Frigate
- Portainer CE
- AdGuard Home
- ntfy
- Gotify
- Pi-hole
- Plex Media Server
- Node-RED
- Mosquitto
- Zigbee2MQTT
- Umami
- Calibre-Web
- Gitea
- Dozzle
- Homarr
- SearXNG
- code-server
- PrivateBin
- authentik
- Radicale
- Karakeep
- wallabag
- IT-Tools
- HedgeDoc
- Seerr
- FreshRSS
- Mealie
- Actual Budget
- Stirling-PDF
- linkding
- Miniflux
- Kavita
- Ghost
- BookStack
- Wiki.js
- Memos
- Vikunja
- changedetection.io
- Authelia
- wg-easy
- Firefly III
- Tandoor Recipes
- Grocy
- Homepage
- Kopia
- SiYuan
- Reactive Resume
- ToolJet
- Appsmith
- Trilium Notes
- Khoj
- Glance
- QwenPaw
- Langfuse
- Plausible CE
- ArchiveBox
- Dashy
- Beszel
- NocoBase
- listmonk
- Neko
- Linkwarden
- ConvertX
- DocuSeal
- BentoPDF
- Termix
- Documenso
- MeTube
- TREK
- RomM
- PLANKA
- Gatus
- Homer
- Owncast
- Dawarich
- OmniTools
- LibrePhotos
- Homebox
- Photoview
- SparkyFitness
- bitmagnet
- 13ft
- Moodist
- OliveTin
- AdventureLog
The defaults that cause most of it
- nginx accepts request bodies up to
client_max_body_size 1mand answers 413 above that; it waitsproxy_read_timeout 60sfor the app; and before nginx 1.29.7 it spoke HTTP/1.0 to the app, so WebSockets needproxy_http_version 1.1plus the Upgrade and Connection headers, which nginx never forwards by itself. [nginx docs below] - Nginx Proxy Manager raises the body limit to
2000mand the timeouts to90sfor every host, sends Host, X-Forwarded-Proto, X-Forwarded-For and X-Real-IP, and adds the WebSocket headers only when Websockets Support is on. Text in the Advanced tab lands in the server block. [NPM source below] - Caddy proxies WebSockets and sets X-Forwarded-For, -Proto and -Host on its own, and sets no body-size limit unless you add one, which is why most Caddy blocks here are two lines. [Caddy docs below]
- Traefik also passes WebSockets and the forwarded headers by default, but its entrypoint read timeout is 60 seconds, which is what cuts long uploads (Immich documents error 499). [Traefik docs below]
- The app usually has to be told to trust the proxy (Home Assistant, Nextcloud, Jellyfin, ntfy) or told its public https address (Nextcloud, Paperless-ngx, n8n, Grafana, Forgejo): that half is under “In app itself” in each section.
Immich app page
Upstream immich-server:2283 · WebSockets: required [1] · Upload limit: 50000M [1] · Timeouts: 600s [1] · docs checked 2026-09-26
# 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: 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
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]
# 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
}
# 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
Optional: list your proxy's address in IMMICH_TRUSTED_PROXIES (comma-separated IPs) on the immich-server container, so Immich takes the visitor's address from the forwarded headers. [2]
IMMICH_TRUSTED_PROXIES=<proxy IP>
- Immich must be served on the root of a (sub)domain; a sub-path such as /immich is not supported. [1]
- If the proxy gets certificates with Let's Encrypt's http-01 challenge, make sure /.well-known/immich still reaches Immich, or the mobile app may fail to connect. [1]
- Immich docs: Reverse Proxy (nginx, Caddy and Traefik examples) checked 2026-09-26
- 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
# 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: 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
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]
# 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
}
# 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
In config/config.php: trust the proxy's address, and fix the protocol and the command-line URL so links and notifications use https. [1]
'trusted_proxies' => ['<proxy IP>'], 'overwriteprotocol' => 'https', 'overwrite.cli.url' => 'https://cloud.example.org',
With the official nextcloud Docker image the same settings are environment variables; APACHE_DISABLE_REWRITE_IP=1 lets Nextcloud read the forwarded headers from the trusted proxy. [4]
APACHE_DISABLE_REWRITE_IP=1 TRUSTED_PROXIES=<proxy IP> OVERWRITEPROTOCOL=https OVERWRITECLIURL=https://cloud.example.org
- 512M is the value in Nextcloud's own nginx configuration. Browser uploads are sent in 100 MiB chunks by default (files.chunked_upload.max_size), so this limit is not the maximum file size. [2]
- The manual's nginx example also has a catch-all 'location ^~ /.well-known' redirect to /index.php; it is left out here because it would also catch Let's Encrypt's /.well-known/acme-challenge/ on the same host. The two DAV redirects are the ones the Caddy example has too. [1]
- Nextcloud admin manual: Reverse proxy (trusted_proxies, overwrite parameters, CalDAV/CardDAV redirects, the NPM proxy_hide_header note) checked 2026-09-26
- 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
- Nextcloud admin manual: NGINX configuration (client_max_body_size 512M) checked 2026-09-26
- 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
# 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: 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
proxy_buffering off; # [2]
# 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
}
# 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
Home Assistant 2026.8 and newer: Settings > System > Network > HTTP server, turn on Trust X-Forwarded-For and add the proxy to Trusted proxies. Requests from a reverse proxy are blocked until both are set. For a range, give the network address (192.168.1.0/24, not 192.168.1.50/24). [1]
Trust X-Forwarded-For: on Trusted proxies: <proxy IP>
Before 2026.8 the same two settings lived in configuration.yaml. On upgrade Home Assistant imports them and raises a repair issue until you delete the http: block. [1]
http: use_x_forwarded_for: true trusted_proxies: - <proxy IP>
- Home Assistant Container keeps port 8123 (the 2026.8 default of 80 applies to Home Assistant OS). Its documented compose file uses host networking, so the upstream is the host: host.docker.internal:8123 from a proxy container with an extra_hosts host-gateway entry, or 127.0.0.1:8123 for a proxy installed on the same machine. [1]
Vaultwarden app page
Upstream vaultwarden:80 · WebSockets: required [1] · Upload limit: 525M [1] · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
client_max_body_size 525M; # [1]
# 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}
}
}
# 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.
- The wiki's map sends an empty Connection value instead of 'close' when there is no upgrade, so keepalive connections to Vaultwarden keep working. [1]
- On 504 Gateway Timeout the wiki suggests longer timeouts in the server block: proxy_connect_timeout, proxy_send_timeout, proxy_read_timeout and send_timeout 777. [1]
Jellyfin app page
Upstream jellyfin:8096 · WebSockets: required on /socket [1] · Upload limit: 20M [1] · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
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]
}
# 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
}
# 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
Dashboard > Networking: add the proxy's IP address to Known Proxies. Jellyfin ignores forwarded-for headers from any other address, so without it every visitor looks like the proxy and remote-access limits do not work. [2]
Known Proxies: <proxy IP>
- The docs' comment: nginx's default client_max_body_size of 1M 'might not be enough for some posters'. [1]
Paperless-ngx app page
Upstream webserver:8000 · WebSockets: required [1] · Upload limit: 10M [1] · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
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]
# 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
}
# 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
Set PAPERLESS_URL to the public address (no trailing slash, no path); the wiki says it is required behind a reverse proxy. It fills ALLOWED_HOSTS, CORS_ALLOWED_HOSTS and CSRF_TRUSTED_ORIGINS. [2]
PAPERLESS_URL=https://docs.example.org
The wiki also suggests these three when the proxy forwards host, port and protocol. [1]
PAPERLESS_USE_X_FORWARD_HOST=true PAPERLESS_USE_X_FORWARD_PORT=true PAPERLESS_PROXY_SSL_HEADER='["HTTP_X_FORWARDED_PROTO", "https"]'
- 10M is the wiki's example ('Adjust as required. This is the maximum size for file uploads.'); raise it if you upload larger scans. [1]
- Paperless-ngx wiki: Using a Reverse Proxy with Paperless-ngx (nginx, Nginx Proxy Manager) checked 2026-09-26
- 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
# 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: 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
# Nothing to add: Uptime Kuma's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
If Uptime Kuma is reachable only through the proxy, turn on trusted proxy headers so logs show the visitor's address. [1]
Settings > Reverse Proxy > HTTP Headers > Trust Proxy: Yes
- The wiki: 'Unlike other web apps, Uptime Kuma is based on WebSocket.' A sub-directory such as /uptimekuma is not supported. [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
# 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: 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
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]
# 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
}
# 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.
- 10240M is the docs' value, there to 'prevent 413 Request Entity Too Large' on uploads. [2]
- Audiobookshelf README: Reverse Proxy Set Up ('Audiobookshelf requires a websocket connection') checked 2026-09-26
- Audiobookshelf docs: Reverse proxy > NGINX (client_max_body_size 10240M, Host $http_host, proxy_redirect) checked 2026-09-26
- 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
# 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: 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
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]
}
# 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
}
}
# 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
Keep PhotoPrism's own TLS off so the proxy handles certificates, and set the public site URL. If the proxy reaches PhotoPrism from outside Docker's default internal range, add its IP or CIDR to PHOTOPRISM_TRUSTED_PROXY. [1]
PHOTOPRISM_DISABLE_TLS="true" PHOTOPRISM_SITE_URL="https://gallery.example.org/" PHOTOPRISM_TRUSTED_PROXY="<proxy IP or CIDR>"
Syncthing app page
Upstream syncthing:8384 · WebSockets: not in the docs · Upload limit: not given · Timeouts: 600s [1] · docs checked 2026-09-26
# 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: 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
proxy_read_timeout 600s; # [1] proxy_send_timeout 600s; # [1]
# 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}
}
}
# 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.
- Syncthing's examples serve the GUI under /syncthing/ on an existing site; here it gets its own subdomain, so the location is /. [1]
n8n app page
Upstream n8n:5678 · WebSockets: required [2] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
# 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]
}
# 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
}
# 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
Set the public webhook URL and tell n8n it sits behind one proxy. N8N_WEBHOOK_URL replaces WEBHOOK_URL, which is deprecated from n8n 2.35.0. [1]
N8N_WEBHOOK_URL=https://n8n.example.org/ N8N_PROXY_HOPS=1
- The editor gets live updates over WebSockets by default (N8N_PUSH_BACKEND=websocket); the alternative is sse. [2]
Open WebUI app page
Upstream open-webui:8080 · WebSockets: required [1] · Upload limit: 20M [1] · Timeouts: 10m [1] · docs checked 2026-09-26
# 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: 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
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]
# 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
}
# 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
Set CORS_ALLOW_ORIGIN to the public address. The docs: without it WebSocket connections fail behind a proxy such as NPM, even with Websockets Support on. [1]
CORS_ALLOW_ORIGIN="https://chat.example.org"
- The docs call buffering 'the most common cause of garbled markdown': with proxy_buffering on, nginx re-chunks the streamed answer and tokens such as ** and ## show up raw. [1]
Grafana app page
Upstream grafana:3000 · WebSockets: required on /api/live/ [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
# Nothing to add: Grafana's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Tell Grafana its public name so links and redirects are right; when the proxy terminates TLS, root_url must carry https. [1]
[server] domain = grafana.example.org root_url = https://grafana.example.org/
- Grafana Live holds one WebSocket per open dashboard; the tutorial notes you may have to raise nginx's worker_connections (512 by default). [1]
Forgejo app page
Upstream server:3000 · WebSockets: required [1] · Upload limit: 512M [1] · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
client_max_body_size 512M; # [1] merge_slashes off; # [1]
# 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
}
# 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
Set ROOT_URL (app.ini [server], or FORGEJO__server__ROOT_URL in Docker) to the https address so the links Forgejo generates use HTTPS. [1]
FORGEJO__server__ROOT_URL=https://git.example.org/
- merge_slashes off is marked 'Required to handle URL-encoded slashes' in the docs. [1]
Frigate app page
Upstream frigate:8971 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
# Nothing to add: Frigate's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Turn Frigate's own TLS off first. Port 8971 serves HTTPS with a self-signed certificate by default, and a proxy that sends plain HTTP to it gets HTTP 400 'The plain HTTP request was sent to HTTPS port'. The docs' other route is to make the proxy accept the self-signed certificate; this page does not print that, because it switches off certificate checking. [2]
tls: enabled: False
- Camera controls, live streams and other live parts of the UI need WebSockets; the docs name NPM's Websockets Support toggle as one that must be switched on. [1]
- The dankhost builder takes the docs' other route for Frigate: it keeps Frigate's TLS on and has the proxy accept the self-signed certificate on the internal Docker network. This page does not print that, because it switches certificate checking off. [2]
Portainer CE app page
Upstream portainer:9000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
# 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]
# 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
}
# 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
Optional: pass the proxy's address with --trusted-proxies so the Authentication logs show the real client address. If the public origin cannot be inferred from the forwarded headers, list it with --trusted-origins. [1]
command: --trusted-proxies <proxy IP> --trusted-origins https://portainer.example.org
- Forward X-Forwarded-Proto https only when the browser really uses HTTPS: Portainer then sets Secure cookies, and a browser on plain HTTP drops them (401, instant logout). [1]
- Portainer's reverse-proxy page gives no WebSocket setting, so none is printed here. If the container console will not connect through nginx, that is the part to look at.
AdGuard Home app page
Upstream adguardhome:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-26
# 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: 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
# Nothing to add: AdGuard Home's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
In AdGuardHome.yaml: list the proxy under dns.trusted_proxies so AdGuard Home reads the real client address from its headers. To answer DNS-over-HTTPS through the proxy without AdGuard Home's own TLS, set http.doh.insecure_enabled (v0.107.74 and newer; older versions call it allow_unencrypted_doh under tls). [2]
http: doh: insecure_enabled: true dns: trusted_proxies: - <proxy IP>
ntfy app page
Upstream ntfy:80 · WebSockets: required [1] · Upload limit: 0 [1] · Timeouts: 3m [1] · docs checked 2026-09-26
# 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: 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
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.
# 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
}
# 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
The docs' warning: behind a proxy you must set behind-proxy, otherwise all visitors are rate-limited as if they were one. Set base-url to the public address too. [1]
NTFY_BEHIND_PROXY=true NTFY_BASE_URL=https://ntfy.example.org
- client_max_body_size 0 streams request bodies (attachments) straight to ntfy; the nginx example marks it 'Stream request body to backend'. [1]
Gotify app page
Upstream gotify:80 · WebSockets: required [1] · Upload limit: not given · Timeouts: 1m [1] · docs checked 2026-09-26
# 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: 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
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.
# 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
}
# 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
Trust the proxy for the client address, and mark session cookies Secure once Gotify is reached over HTTPS. [2]
GOTIFY_SERVER_TRUSTEDPROXIES=<proxy IP> GOTIFY_SERVER_SECURECOOKIE=true
- The docs: 'The proxy must preserve the host because Gotify verifies the host with the origin for WebSocket connections', hence Host $http_host. [1]
- Gotify docs: nginx (WebSocket headers, Host $http_host, 1m timeouts) checked 2026-09-26
- 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
# 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: 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
# Nothing to add: Pi-hole's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Set the web interface password, which the proxy does not replace. The docs' compose form reads it from a variable. [2]
FTLCONF_webserver_api_password: ${ADMIN_PASSWORD}
- Pi-hole's docs publish no reverse-proxy settings; this block only forwards the web interface on port 80. The admin pages are at /admin. DNS (port 53) never goes through an HTTP proxy. [1]
- Pi-hole's docs give no reverse-proxy settings, so no WebSocket setting is printed here.
Plex Media Server app page
Upstream plex:32400 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29
# 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: 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
# Nothing to add: Plex Media Server's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Tell Plex the address clients should use: Settings > Network > Custom server access URLs, which the page names for a server behind a reverse proxy. In the official Docker image ADVERTISE_IP sets the same list. [1]
https://plex.example.org:443
- Plex's page gives no nginx settings; this block forwards everything to port 32400, "the primary port that Plex uses". Plex's own Remote Access test checks port 32400 directly, not the proxy. [2]
- Plex's support pages give no reverse-proxy WebSocket setting, so none is printed here.
Node-RED app page
Upstream node-red:1880 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29
# 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: 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
# Nothing to add: Node-RED's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Put a login on the editor before it is reachable through the proxy: "By default, the Node-RED editor is not secured". Uncomment adminAuth in /data/settings.js with a hash from node-red admin hash-pw. [1]
adminAuth: { type: "credentials", users: [{ username: "admin", password: "<hash from node-red admin hash-pw>", permissions: "*" }] }
- A proxy adds HTTPS, not a login: anyone who reaches the editor can deploy flows until adminAuth is set. [1]
- Node-RED's docs publish no reverse-proxy settings, so no WebSocket setting is printed here.
- Node-RED docs: Securing Node-RED (the editor is not secured by default; adminAuth; hash-pw) checked 2026-09-29
- 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
# 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: 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
# Nothing to add: Mosquitto's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
The proxy needs a listener that speaks MQTT over WebSockets; plain MQTT (1883) cannot go through an HTTP proxy. [1]
listener 9001 protocol websockets
- Every request on this listener is a WebSocket (protocol websockets), so the upgrade headers are required. Clients connect to wss://{{host}}; devices that only speak plain MQTT keep using port 1883 on your network. [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
# 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: 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
# Nothing to add: Zigbee2MQTT's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Give the frontend a token of its own; the docs recommend it over HTTP basic authentication in the proxy. [1]
frontend: enabled: true auth_token: <a long random token>
- The docs: basic authentication in the proxy breaks the frontend's WebSocket in WebKit browsers (Safari and every browser on iOS), so use auth_token instead. [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
# 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: 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
# Nothing to add: Umami's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Only if your proxy passes the visitor's address in a non-standard header: name that header, or Umami records the proxy as every visitor. [1]
CLIENT_IP_HEADER=<header name>
- Umami's docs give no reverse-proxy WebSocket setting, so none is printed here.
Calibre-Web app page
Upstream calibre-web:8083 · WebSockets: not in the docs · Upload limit: 20M [1] · Timeouts: defaults · docs checked 2026-09-29
# 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: 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
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]
# 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
}
}
# 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.
- On a sub-path such as /calibre the wiki adds proxy_set_header X-Script-Name /calibre; on its own subdomain, as here, that line is left out. [1]
Gitea app page
Upstream server:3000 · WebSockets: required [1] · Upload limit: 512M [1] · Timeouts: defaults · docs checked 2026-09-29
# 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: 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
client_max_body_size 512M; # [1]
# 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
}
# 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
Set ROOT_URL to the public https address ([server] in app.ini, or GITEA__server__ROOT_URL in Docker). [1]
GITEA__server__ROOT_URL=https://gitea.example.org/
- The docs: the proxy must not decode the URI (a request for /a%2Fb has to reach Gitea as /a%2Fb, not /a/b), which is why proxy_pass has no path after the address. [1]
- client_max_body_size 512M: the docs say a small limit gives "413 Request Entity Too Large" when uploading large files. [1]
Dozzle app page
Upstream dozzle:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29
# 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: 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
chunked_transfer_encoding off; # [1] proxy_buffering off; # [1] proxy_cache off; # [1]
# 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
}
}
# 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.
- Dozzle streams logs as server-sent events: with buffering on they arrive in bursts or not at all. Its page also says not to compress text/event-stream. [1]
Homarr app page
Upstream homarr:7575 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-29
# 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: 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
# Nothing to add: Homarr's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- Homarr's page gives only the upstream (homarr:7575) for Caddy and Traefik and no nginx settings. [1]
- Homarr's proxy page gives no WebSocket setting, so none is printed here.
SearXNG app page
Upstream core:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30
# 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: 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
# Nothing to add: SearXNG's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Give SearXNG its public address, so the links it builds point at the proxy. [2]
SEARXNG_BASE_URL=https://search.example.org/
- The docs' example sets X-Real-IP and X-Forwarded-For (for the bot detection, botdetection/trusted_proxies.py) and X-Forwarded-Proto; the generic lines above already send all three. [1]
- X-Script-Name is only for serving SearXNG under a path such as /searxng; on its own subdomain it is left out. [1]
- SearXNG's nginx example sends no Upgrade header; it needs no WebSocket, so none is printed here.
code-server app page
Upstream code-server:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30
# 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: 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
# 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.
# 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
}
# 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.
- code-server talks to the browser over WebSockets; without the Upgrade and Connection headers the editor loads and then cannot connect. [2]
- The guide's Caddy example is a plain reverse_proxy; for a sub-path it adds uri strip_prefix /code. [1]
PrivateBin app page
Upstream privatebin:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30
# 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: 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
# Nothing to add: PrivateBin's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Tell PrivateBin which header carries the visitor's address, or its rate limit (one paste per 10 seconds per address) counts every visitor as the proxy. The dankhost builder writes this into conf.php. [2]
[traffic] header = "X_FORWARDED_FOR"
- The README: the container serves plain HTTP on 8080, so use a reverse proxy for HTTPS termination in production. Its nginx and php-fpm inside accept uploads up to 10 MiB by default. [1]
- PrivateBin's docs give no WebSocket setting, so none is printed here.
authentik app page
Upstream server:9000 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30
# 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: 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
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.
# 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
}
# 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.
- authentik's nginx example proxies to its HTTPS listener on 9443; its page says to use port 9000 and http:// for the HTTP listener, as here. [1]
- Its example calls the map variable $connection_upgrade_keepalive and maps "no upgrade" to an empty value, so keepalive connections stay open; the map above does the same. [1]
- authentik only believes forwarded headers from its trusted proxy networks, by default 127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fe80::/10 and ::1/128. A proxy that connects from another address needs AUTHENTIK_LISTEN__TRUSTED_PROXY_CIDRS, or authentik sees HTTP instead of HTTPS. [1]
Radicale app page
Upstream radicale:5232 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30
# 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: 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
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.
# 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
}
# 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.
- X-Script-Name is only for serving Radicale under a path such as /radicale/ (and the proxy must then strip that path); at the root of a subdomain the docs say to leave it out. [1]
- Radicale's reverse-proxy examples give no WebSocket setting, so none is printed here.
Karakeep app page
Upstream web:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30
# 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: 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
# Nothing to add: Karakeep's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Set NEXTAUTH_URL to the public address; the docs: without it Karakeep works but "will redirect you to wrong addresses on signout for example". [1]
NEXTAUTH_URL=https://karakeep.example.org
- Karakeep's docs give no reverse-proxy setting, so none is printed here.
- 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
# 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: 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
# 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]
}
# 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
}
# 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
Set the public address wallabag builds its links from. [1]
SYMFONY__ENV__DOMAIN_NAME=https://read.example.org
- wallabag's nginx example gives no WebSocket setting, so none is printed here.
IT-Tools app page
Upstream it-tools:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30
# 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: 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
# Nothing to add: IT-Tools's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- IT-Tools' README gives only the docker run command, a static page served by nginx on port 80, and no proxy settings. [1]
- IT-Tools's README gives no WebSocket setting, so none is printed here.
- 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
# 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: 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
# Nothing to add: HedgeDoc's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Tell HedgeDoc its public address, or it links assets and pages with the wrong host, scheme or port. [1]
CMD_DOMAIN=pad.example.org CMD_PROTOCOL_USESSL=true CMD_URL_ADDPORT=false
- The guide: the proxy must allow WebSocket Upgrade requests at /socket.io/ and pass through the scheme the client used. [1]
- Behind Cloudflare, turn Rocket Loader off, or HedgeDoc may break (the guide). [1]
Seerr app page
Upstream seerr:5055 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-09-30
# 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: 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
# 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]
}
# 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
}
# 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
In Seerr: Settings > Network > Enable Proxy Support, so it records each visitor's address from the forwarded headers instead of the proxy's. It is off by default. [2]
- Base URLs cannot be configured in Seerr, so it needs its own subdomain; the sub-folder nginx example on the same page is an unsupported workaround. [1]
- Seerr's reverse-proxy page gives no WebSocket setting, so none is printed here.
- Seerr docs: Reverse Proxy (subdomain only; nginx headers) checked 2026-09-30
- 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
# 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: 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
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]
}
# 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
}
# 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
List the proxy in TRUSTED_PROXY (space-separated IPs or CIDR ranges, no host names), so FreshRSS logs the visitor's address from X-Forwarded-For instead of the proxy's. It also matters for external authentication. [1]
TRUSTED_PROXY=<proxy IP or range>
- The README forwards the Authorization header so that the Google Reader API keeps working behind nginx. [1]
- For a sub-folder such as /freshrss the README's nginx example adds X-Forwarded-Prefix /freshrss/; on its own subdomain it is left out. [1]
- FreshRSS's nginx example gives no WebSocket setting, so none is printed here.
Mealie app page
Upstream mealie:9000 · WebSockets: not in the docs · Upload limit: 0 [2] · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
client_max_body_size 0; # [2]
# 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
}
# 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
Set BASE_URL to the public address; Mealie uses it for links in notifications and for the OpenID Connect callback, and it defaults to http://localhost:8080. [1]
BASE_URL=https://recipes.example.org
- client_max_body_size 0 switches nginx's upload limit off. It comes from a community guide written for an older two-container Mealie (mealie-frontend on port 3000); today's single image answers on port 9000. [2]
- Mealie's SWAG guide gives no WebSocket setting, so none is printed here.
Actual Budget app page
Upstream actual-server:5006 · WebSockets: not in the docs · Upload limit: 0 [1] · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
client_max_body_size 0; # [1]
# 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
}
# 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.
- Actual needs a secure context and sends its own Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy headers so its SQLite engine can use SharedArrayBuffer. If your nginx adds these headers too, the browser sees duplicates and Actual stops with a SharedArrayBufferMissing error. The docs' fix is proxy_hide_header for both, then add_header once each (with Origin-Agent-Cluster "?1"). The blocks here add none, so there is nothing to collide. [1]
- client_max_body_size 0 (no upload limit) is from the docs' NGINX example config. [1]
- Actual's reverse-proxy page gives no WebSocket setting, so none is printed here.
Stirling-PDF app page
Upstream stirling-pdf:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: Stirling-PDF's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Optional: the largest upload Stirling-PDF accepts (the guide's example is 2GB; the number must be 0-999, followed by KB, MB or GB). Raise the proxy's limit to match. [1]
SYSTEMFILEUPLOADLIMIT=2GB
- The guide asks the proxy to keep the public hostname and send X-Forwarded-Proto (plus X-Forwarded-Host if the Host it passes on differs), because Stirling-PDF builds its login redirects from them. The generic lines above already send Host and X-Forwarded-Proto. [1]
- The guide gives no number for the proxy: it says to match the proxy's upload limit to the uploads you allow and to allow enough time for processing. [1]
- Stirling-PDF's production guide gives no WebSocket setting, so none is printed here.
linkding app page
Upstream linkding:9090 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.
# 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
}
# 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
If logins fail with "403 CSRF verification failed", the proxy has changed the Host header: set the public origin here instead (with https://, without a path). [2]
LD_CSRF_TRUSTED_ORIGINS=https://bookmarks.example.org
- linkding's nginx section also asks for X-Forwarded-Proto $scheme, which the generic lines above already send. Caddy and Apache need no extra configuration, the docs say. [1]
- linkding's reverse-proxy section gives no WebSocket setting, so none is printed here.
Miniflux app page
Upstream miniflux:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
proxy_redirect off; # [1]
# 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
}
# 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
BASE_URL is the address Miniflux builds its links and cookie path from; its default is localhost over plain http. [2]
BASE_URL=https://feeds.example.org/
Optional: the networks (CIDR) allowed to send X-Forwarded-For, X-Forwarded-Proto and X-Real-Ip (and the proxy authentication header). It is empty by default. [2]
TRUSTED_REVERSE_PROXY_NETWORKS=<proxy network CIDR>
- The how-to's nginx example sends Host, X-Real-IP, X-Forwarded-For and X-Forwarded-Proto, the same four generic lines as above, plus proxy_redirect off. [1]
- Miniflux's nginx example gives no WebSocket setting, so none is printed here.
- Miniflux docs: How-to, Reverse-Proxy Configuration (nginx example) checked 2026-10-01
- 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
# 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: 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
# Nothing to add: Kavita's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Kavita trusts X-Forwarded-Host and the other forwarding headers only from localhost. If your proxy connects from any other address, list that address in appsettings.json in the mounted config folder, or EPUB images may break. [3]
"KnownProxies": [ "<proxy IP>" ]
- The wiki says these example configurations are user-submitted. [3]
- Kavita wiki: NGINX Example (Host and X headers, WebSocket headers) checked 2026-10-01
- Kavita wiki: NGINX Proxy Manager (Docker) example (Websockets Support enabled) checked 2026-10-01
- 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
# 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: 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
# Nothing to add: Ghost's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Set url, required in production, to the address used to reach the site, with https:// when using SSL. In Docker it is the url environment variable. [1]
url=https://blog.example.org
- ghost-docker's own web server config proxies everything to ghost:2368 and only optionally compresses with gzip; its other lines (logging, security headers, ActivityPub and analytics routes) belong to optional services and are not copied here. [2]
- To serve Ghost Admin on a separate domain, the example has a commented second site block ({$ADMIN_DOMAIN}) that proxies to the same ghost:2368. [2]
- Ghost's Caddyfile example gives no WebSocket setting, so none is printed here.
BookStack app page
Upstream bookstack:80 · WebSockets: not in the docs · Upload limit: 100m [1] · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
client_max_body_size 100m; # [1] client_body_timeout 120s; # [1]
# 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
}
# 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
Set APP_URL to the public https address, so generated URLs cannot be manipulated and secure cookies switch on. [2]
APP_URL=https://bookstack.example.org
Trust the proxy, or BookStack records the proxy's address for every user in the audit log and in rate limiting. [2]
APP_PROXIES=<proxy IP>
- The docs' 100m is an example: BookStack's own FILE_UPLOAD_SIZE_LIMIT in .env (megabytes; the docs' example is 50) and PHP's post_max_size and upload_max_filesize also cap uploads. client_body_timeout matters only when one upload takes longer than 60 seconds. [1]
- BookStack's documentation gives no WebSocket setting, so none is printed here.
Wiki.js app page
Upstream wiki:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: Wiki.js's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- Wiki.js documents nothing proxy-specific: its Docker page covers only its own HTTPS (port 3443 with Let's Encrypt), and its sample config says to use a reverse proxy such as nginx for anything more advanced, without giving settings. Only the upstream is printed here. [2]
- Wiki.js's documentation gives no WebSocket setting, so none is printed here.
Memos app page
Upstream memos:5230 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: Memos's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Set MEMOS_INSTANCE_URL to the public URL (absolute, without credentials, query or fragment). Since Memos 0.31 it does not change whether the instance is private or public; that is the separate ACCESS setting. [1]
MEMOS_INSTANCE_URL=https://memos.example.org
- The page asks for the standard headers Host, X-Forwarded-Proto and X-Forwarded-For, which the generic lines above already send, and gives no proxy configuration of its own. [1]
- Memos's reverse-proxy page gives no WebSocket setting, so none is printed here.
Vikunja app page
Upstream vikunja:3456 · WebSockets: required [1] · Upload limit: 20M [1] · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
client_max_body_size 20M; # [1]
# 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
}
# 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
Set VIKUNJA_SERVICE_PUBLICURL to the public https address, with the trailing slash as in the docs. [1]
VIKUNJA_SERVICE_PUBLICURL=https://tasks.example.org/
- If you raise the maximum upload size in Vikunja's settings, raise client_max_body_size with it. [1]
- The WebSocket lines come from the docs' Nginx Proxy Manager walkthrough, which turns Websockets Support on (NPM then sends Upgrade and Connection $http_connection); the docs' plain nginx example has no WebSocket lines. [1]
changedetection.io app page
Upstream changedetection:5000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: changedetection.io's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Turn on USE_X_SETTINGS, or changedetection.io ignores the Host, X-Forwarded-Prefix and X-Forwarded-Proto headers the proxy sends. [1]
USE_X_SETTINGS=1
BASE_URL is the address put into notification alerts. [2]
BASE_URL=https://watch.example.org
- On its own subdomain the wiki's Caddy example is just reverse_proxy. The nginx example on that page is for a sub-folder (/app/, with X-Forwarded-Prefix and a trailing slash on location and proxy_pass); none of that is needed on a subdomain. [1]
- Known issue listed on the page: random problems fetching resources behind Caddy or Traefik (GitHub issue 2053). [1]
- changedetection.io's reverse-proxy page gives no WebSocket setting, so none is printed here.
Authelia app page
Upstream authelia:9091 · WebSockets: not in the docs · Upload limit: not given · Timeouts: 360 [1] · docs checked 2026-10-01
# 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: 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
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]
}
# 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
}
# 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.
- This is the portal's own server block (auth.<domain> to authelia:9091), with the lines of the docs' proxy.conf (Standard Variant). Protecting another app with Authelia takes two more snippets on that app's server block (authelia-location.conf and authelia-authrequest.conf, on the same page); the dankhost builder writes the Caddy and Traefik versions when you tick Authelia with other apps. [1]
- Authelia's proxy.conf also trusts forwarded addresses through nginx's real_ip module (set_real_ip_from for your proxies' ranges, real_ip_header X-Forwarded-For, real_ip_recursive on). The docs ask you to list only the ranges your own proxies use, not whole private subnets. [1]
- Authelia's NGINX page for the portal itself gives no WebSocket setting, so none is printed here.
wg-easy app page
Upstream wg-easy:51821 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: wg-easy's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- wg-easy documents nothing proxy-specific beyond the upstream: its Traefik tutorial routes to port 51821 and adds no headers or middleware for wg-easy itself. Its Caddy tutorial moves the web UI to port 80 with PORT=80 and proxies to wg-easy:80; with the default port the upstream is wg-easy:51821 as here. [1]
- Only the web UI goes through the proxy. The VPN itself is 51820/udp, published on the host as in the tutorials ("no need to publish the HTTP server anymore"). [2]
- wg-easy's Caddy and Traefik tutorials gives no WebSocket setting, so none is printed here.
- wg-easy docs: Traefik tutorial (loadbalancer.server.port=51821) checked 2026-10-01
- 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
# 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: 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
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]
}
# 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
}
# 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
Trust the proxy: the FAQ gives TRUSTED_PROXIES as * or your proxy's IP address (the dankhost builder writes the proxy's address). [1]
TRUSTED_PROXIES=<proxy IP>
APP_URL must match the external URL: Firefly III uses it to validate some requests and to build the links in its emails. [3]
APP_URL=https://money.example.org
- Without TRUSTED_PROXIES the Docker FAQ names two symptoms: Content Security Policy errors, and links that point at http:// so forms and charts do not work. [2]
- The three buffer lines are the FAQ's fix for 502 Bad Gateway: the header Firefly III sends with a token can be too long for the proxy's buffers. [1]
- Unexplained 431 errors (logging in, for example) mean the proxy's maximum header size is too small; with Authelia in front, the FAQ asks for a buffer size of at least 8192. [1]
- A subdirectory instead of a subdomain works too; the Docker FAQ quotes a user-contributed Apache setup that rewrites the URLs in the pages. [2]
- Firefly III's FAQ gives no WebSocket setting, so none is printed here.
- 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
- Firefly III docs: Docker FAQ (CSP errors and http links without TRUSTED_PROXIES; running under a subdirectory) checked 2026-10-01
- 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
# 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: 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
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.
# 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
}
# 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
Set ALLOWED_HOSTS to the public host name. The default * works, but the docs say it should be the actual host. [3]
ALLOWED_HOSTS=tandoor.example.org
Since 2.6.1 Tandoor rate-limits logins by the client address in X-Forwarded-For and counts its own built-in nginx as one proxy. With one reverse proxy in front the count is 2; raise it if logins fail with 403. [2]
ALLAUTH_TRUSTED_PROXY_COUNT=2
- The FAQ's checklist: Host and X-Forwarded-Host must match the URL you open Tandoor with, and X-Forwarded-Proto must hold exactly one protocol. Open /system/ and read the DEBUG section to see what Tandoor receives. Wrong headers show up as CSRF errors, broken links, or images and recipes that do not load. [2]
- The docs' nginx example also has a proxy_redirect from its own local address (127.0.0.1:8080) to the public https address. It is not printed here: it only rewrites redirects that point at that example address, and this block proxies to web_recipes:80. [1]
- The docs warn that behind jwilder's nginx-proxy uploads stop at 1 MB until client_max_body_size is raised; they give no value for it. [1]
- Tandoor's documentation gives no WebSocket setting, so none is printed here.
Grocy app page
Upstream grocy:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: Grocy's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- Grocy documents nothing proxy-specific. Its config only needs BASE_URL and BASE_PATH changed when it runs in a subdirectory; on its own subdomain, as here, the defaults (BASE_URL "/", BASE_PATH empty) are right. Only the upstream is printed here. [1]
- Optional: if your proxy does the login, AUTH_CLASS Grocy\Middleware\Auth\ReverseProxyAuthMiddleware takes the user name from the header named in REVERSE_PROXY_AUTH_HEADER (REMOTE_USER by default). Every setting can also be an environment variable with the GROCY_ prefix. [1]
- Grocy's configuration gives no WebSocket setting, so none is printed here.
Homepage app page
Upstream homepage:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: Homepage's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Since v1.0 Homepage answers only localhost:3000 and 127.0.0.1:3000 unless the host is listed here (comma-separated, no spaces). On host validation errors, add the host exactly as the log prints it. [1]
HOMEPAGE_ALLOWED_HOSTS=dash.example.org
With the built-in login (v2.0 and later), give the external URL with https:// so the login cookies are marked Secure. [1]
HOMEPAGE_EXTERNAL_URL=https://dash.example.org
- Homepage does not rate-limit password attempts itself. The docs ask the proxy to rate-limit POST requests to /api/auth/callback/credentials when Homepage is reachable from outside, without giving a proxy setting; failed attempts are logged at warn level as "<nextauth> Failed password sign-in attempt", usable as a fail2ban or CrowdSec filter. [1]
- Public deployments should still sit behind a proxy with authentication and TLS, or a VPN; the docs call the built-in host check a best-effort guard, not a substitute. [1]
- Homepage's installation page gives no WebSocket setting, so none is printed here.
Kopia app page
Upstream kopia:51515 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: Kopia's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- Kopia's only proxy example is for the repository server's gRPC API, which other Kopia clients use to back up into this server: nginx 1.16 or newer, listen 443 ssl http2, client_max_body_size 0 and grpc_pass grpcs:// to port 51515. It needs Kopia started with --tls-cert-file and --tls-key-file: --insecure, which the dankhost compose uses, does not work there, because gRPC needs TLS. [1]
- The blocks here proxy the web UI over plain HTTP to the --insecure server. The docs give no setting for that use, so only the upstream is printed. [1]
- Kopia's documentation gives no WebSocket setting, so none is printed here.
SiYuan app page
Upstream main:6806 · WebSockets: required on /ws [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Host: NPM already sends Host $host, the same value as $http_host while NPM listens on 443.
# 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
}
# 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.
- Keep Host as $http_host in both locations: $host drops a non-standard port (such as 8443), Origin validation then fails, and the page sticks on the logo with repeated reloads, 401 API responses or failed WebSocket connections. [1]
- Proxy, do not redirect: the README warns that URL rewriting for redirection can break authentication. [1]
- The README asks for a WebSocket proxy on /ws without spelling out the lines; the Upgrade and Connection lines above are the standard nginx pair for it. [1]
Reactive Resume app page
Upstream reactive-resume:3000 · WebSockets: required [1] · Upload limit: 10M [1] · Timeouts: 60s [1] · docs checked 2026-10-01
# 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: 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
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]
# 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
}
# 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
APP_URL is used for absolute URLs, redirects and sign-in; behind a reverse proxy it is your public https URL. [2]
APP_URL=https://resume.example.org
- The 10M body size is for resume uploads; the 60-second timeouts are what the example calls reasonable for app requests. [1]
- The docs' nginx example also sets its own TLS protocols and ciphers and three response headers (X-Frame-Options, X-Content-Type-Options, X-XSS-Protection). Those are site-wide nginx choices rather than anything Reactive Resume needs from the proxy, so they are left to your own setup. [1]
ToolJet app page
Upstream tooljet:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: ToolJet's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
ToolJet's public URL, scheme included: it must begin with http or https. [1]
TOOLJET_HOST=https://tooljet.example.org
- ToolJet documents nothing proxy-specific: its Docker page asks only for TOOLJET_HOST and a DNS record pointing at the server. Only the upstream is printed here. [1]
- TOOLJET_HTTP_PROXY in ToolJet's docs is the other direction: a proxy for ToolJet's own outgoing requests, not one in front of it. [2]
- ToolJet's Docker page gives no WebSocket setting, so none is printed here.
Appsmith app page
Upstream appsmith:80 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: Appsmith's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Recommended: restricts sensitive sign-in flows to your domain against account takeover; when unset the check is skipped. Also in Settings > Configuration > Appsmith Base URL. [2]
APPSMITH_BASE_URL=https://appsmith.example.org
- Appsmith documents nothing about an outside reverse proxy. Its docs have it terminate TLS itself: Appsmith runs Caddy inside the container, and a Custom Domain (Admin Settings, or APPSMITH_CUSTOM_DOMAIN as a bare host name) makes it generate a certificate and serve HTTPS on port 443. Only the upstream is printed here. [1]
- Appsmith's documentation gives no WebSocket setting, so none is printed here.
Trilium Notes app page
Upstream trilium:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: 90 [1] · docs checked 2026-10-01
# 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: 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
proxy_read_timeout 90; # [1]
# 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
}
# 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
Trust the proxy, so Trilium sees the real client address for rate limiting, logging and secure cookies. true takes the left-most X-Forwarded-For address; the proxy's IP address or Express shortcuts such as loopback or uniquelocal also work. [3]
[Network] trustedReverseProxy=true
The same setting as an environment variable, as in the docs' Traefik compose file (the dankhost builder sets it to true). [4]
TRILIUM_NETWORK_TRUSTEDREVERSEPROXY=true
- Without the WebSocket upgrade the client appears to load but never receives sync or live updates. [2]
- Do not put a forward-auth login (Authelia, authentik, oauth2-proxy) in front of everything: sync cannot answer an interactive login and fails with "Unexpected token '<'". Use Trilium's own login (OpenID Connect included), or exempt /api/setup/*, /api/login/sync and /api/sync/* from the proxy's auth; Trilium authenticates those itself. [2]
- Trilium docs: Reverse proxy, Nginx (WebSocket headers, proxy_read_timeout 90) checked 2026-10-01
- Trilium docs: Reverse proxy (applies to every proxy; authentication proxies and the sync endpoints) checked 2026-10-01
- Trilium docs: Trusted proxy (trustedReverseProxy) checked 2026-10-01
- 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
# 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: 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
# Nothing to add: Khoj's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
The public host name, without a scheme (no http or https prefix). If it is wrong, the admin panel fails with CSRF trusted-origin or unset-cookie errors. [1]
KHOJ_DOMAIN=khoj.example.org
Only behind a reverse proxy: the name the proxy uses to reach Khoj. With the proxy on Khoj's Docker network that is the service name, server; unset, it defaults to KHOJ_DOMAIN. [1]
KHOJ_ALLOWED_DOMAIN=server
- Khoj documents no proxy configuration of its own. Its remote-access page asks for HTTPS on a public domain (KHOJ_NO_HTTPS=True only on a private network), KHOJ_DOMAIN and authentication. Only the upstream is printed here. [2]
- Khoj's documentation gives no WebSocket setting, so none is printed here.
- Khoj: docker-compose.yml (KHOJ_DOMAIN; KHOJ_ALLOWED_DOMAIN behind a reverse proxy; KHOJ_NO_HTTPS) checked 2026-10-01
- 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
# 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: 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
# Nothing to add: Glance's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
In glance.yml: tell Glance it is behind a proxy, so it takes the client address and request details from the X-Forwarded-* headers. Glance blocks an address after 5 failed logins in 5 minutes, which needs the real client address. [1]
server: proxied: true
- base-url is only for serving Glance under a directory; the proxy must then strip that prefix before forwarding. [1]
- Glance's configuration reference gives no WebSocket setting, so none is printed here.
QwenPaw app page
Upstream qwenpaw:8088 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-01
# 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: 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
# Nothing to add: QwenPaw's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Login is off by default; turn it on before the console is reachable through a proxy. QWENPAW_AUTH_USERNAME and QWENPAW_AUTH_PASSWORD create the admin account at startup (the dankhost builder sets all three). [1]
QWENPAW_AUTH_ENABLED=true
- QwenPaw documents nothing proxy-specific. Only the upstream is printed here. [1]
- Requests from 127.0.0.1 and ::1 skip the login, and allow_no_auth_hosts in the config lists more addresses that skip it. Do not add your proxy's address there: every request through the proxy comes from that address. [2]
- The chat API streams its answers with SSE; the docs give no proxy setting for it. [3]
- QwenPaw's documentation gives no WebSocket setting, so none is printed here.
- QwenPaw docs: Security, Web Authentication (off by default; localhost bypass) checked 2026-10-01
- QwenPaw docs: Config (QWENPAW_AUTH_ENABLED; allow_no_auth_hosts) checked 2026-10-01
- 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
# 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: 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
# Nothing to add: Langfuse's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
The public URL, on both langfuse-web and langfuse-worker: it is used for sign-in and for the links in emails, Slack notifications and integration settings. [1]
NEXTAUTH_URL=https://langfuse.example.org
- Only the langfuse-web container (port 3000) has to be reachable by users, the API and the SDKs; the docs expect TLS to end at a load balancer or proxy in front of it. [2]
- Keep the public Host header at the proxy, as the blocks here do: the in-app MCP endpoint accepts only NEXTAUTH_URL's host unless others are listed in LANGFUSE_MCP_ALLOWED_HOSTS. [1]
- Intermittent 502 or 504 errors usually mean Langfuse closes idle keep-alive connections before the proxy does; set KEEP_ALIVE_TIMEOUT on langfuse-web at least 5 seconds above the proxy's idle timeout. [3]
- The compose file also opens MinIO on port 9090, and langfuse-web's LANGFUSE_S3_MEDIA_UPLOAD_ENDPOINT defaults to http://localhost:9090. Media uploads from other machines need that endpoint set to an address they can reach; this page proxies only langfuse-web. [4]
- Langfuse's self-hosting documentation gives no WebSocket setting, so none is printed here.
- Langfuse docs: Configuration (NEXTAUTH_URL; LANGFUSE_MCP_ALLOWED_HOSTS: prefer preserving the public host at the proxy) checked 2026-10-01
- Langfuse docs: Networking (only langfuse-web needs to be reachable; TLS at a load balancer) checked 2026-10-01
- Langfuse FAQ: Intermittent 502 and 504 network errors (KEEP_ALIVE_TIMEOUT) checked 2026-10-01
- 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
# 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: 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
# Nothing to add: Plausible CE's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
BASE_URL is the actual public URL. [2]
BASE_URL=https://plausible.example.org
The port Plausible listens on for the proxy; the wiki's example uses 8000, the upstream here. [1]
HTTP_PORT=8000
- HTTP_PORT=80 together with HTTPS_PORT=443 makes Plausible fetch its own Let's Encrypt certificate; the README says to choose other values behind a reverse proxy. [2]
- Since 2.1.2 Plausible CE can serve HTTPS itself, so a proxy is optional. The wiki's nginx and Apache examples are community-contributed and not tested by the maintainers. [1]
ArchiveBox app page
Upstream archivebox:5797 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03
# 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: 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
# Nothing to add: ArchiveBox's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
The canonical public address. With it set, ArchiveBox builds every link and redirect from it and takes the scheme from it, so https stays https behind the proxy. [2]
BASE_URL=https://archive.example.org
Everything on one host name, with archived pages served without their JavaScript: the mode for a proxy without wildcard DNS. [2]
SERVER_SECURITY_MODE=safe-onedomain-nojsreplay
- Single-domain mode needs one certificate for the BASE_URL host. Isolated-subdomain mode (full JavaScript replay) needs a certificate for both the host and *.host, normally through DNS-01; never use on-demand TLS or request certificates for the snap-* names. [1]
- Modes whose names start with unsafe- or danger- let archived JavaScript run on the same origin as the admin session: the Configuration page says not to use them on a public host name. [2]
- ArchiveBox's Docker and Configuration pages gives no WebSocket setting, so none is printed here.
Dashy app page
Upstream dashy:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03
# 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: 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
proxy_redirect off; # [1] proxy_buffering off; # [1]
# 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
}
# 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.
- The docs say not to expose Dashy to the internet on its built-in auth alone: put an auth layer in front (Authelia, authentik, or the proxy's own), because its status-check and /cors-proxy endpoints are open without auth. DISABLE_PROXY_ENDPOINTS=true turns those endpoints off. [1]
- GET /healthz answers 200 without auth, for a proxy health check. [1]
- Dashy's management docs gives no WebSocket setting, so none is printed here.
Beszel app page
Upstream beszel:8090 · WebSockets: required [1] · Upload limit: 10M [1] · Timeouts: 360s [1] · docs checked 2026-10-03
# 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: 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
client_max_body_size 10M; # [1] proxy_read_timeout 360s; # [1]
# 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
}
}
}
# 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
The public address, used in notification links and in the agent settings the hub generates. [1]
APP_URL=https://beszel.example.org
- The proxy must pass WebSocket connections: agents set up with a universal token connect to the hub that way. [1]
NocoBase app page
Upstream app:80 · WebSockets: required [1] · Upload limit: not given · Timeouts: 600 [1] · docs checked 2026-10-03
# 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: 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
proxy_connect_timeout 600; # [1] proxy_read_timeout 600; # [1] proxy_send_timeout 600; # [1] send_timeout 600; # [1] proxy_buffering off; # [1]
# 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
}
# 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.
- The docs proxy the root path to the container's built-in Nginx on port 80; that one location / also carries /api/, /ws and /files/. If you split static files from application routes, keep /files/ going to NocoBase: it checks the login before serving uploads. [1]
- The docs' example writes Connection $connection_upgrade without showing the map that defines it; the map above is nginx's usual one for WebSocket proxying. [1]
- Serving under a sub-path needs APP_PUBLIC_PATH set first (the docs' Subpath deployment section). [1]
listmonk app page
Upstream app:9000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03
# 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: 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
# Nothing to add: listmonk's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
In Settings > General, the Root URL: the public address of the installation, with no trailing slash. Subscription, unsubscribe and tracking links in every e-mail are built from it. [2]
https://lists.example.org
- Only these routes need to be public: /subscription/*, /link/*, /campaign/*, /public/*, /webhooks/service/* and /uploads/*. /admin/*, /api/* and /webhooks/bounce are the admin side; the docs list them for auth proxies and firewalls. [1]
- listmonk's documentation gives no WebSocket setting, so none is printed here.
Neko app page
Upstream neko:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03
# 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: 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
# Nothing to add: Neko's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Trust the proxy's X-Forwarded-For and X-Real-IP headers (server.proxy in config.yml). [2]
NEKO_SERVER_PROXY=true
- Only the web page and its WebSocket go through the proxy. The video itself is WebRTC, which the docs say no reverse proxy can forward: its UDP (or TCP) port must reach the server directly. [3]
- Neko pings each WebSocket client every 10 seconds and clients send a heartbeat every 120 seconds; proxy timeouts must allow for that. [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
- Neko docs: Configuration, server (server.proxy trusts X-Forwarded-For and X-Real-IP) checked 2026-10-03
- 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
# 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: 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
# 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]
}
# 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
}
# 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
Set both to the public address in .env (or the environment), then restart Linkwarden. BASE_URL matters for e-mail features such as password reset. [1]
NEXTAUTH_URL=https://links.example.org/api/v1/auth BASE_URL=https://links.example.org
- 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
# 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: 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
# Nothing to add: ConvertX's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- Log-in works only over https or on localhost; behind an https proxy nothing needs changing. HTTP_ALLOWED=true is only for plain-http access on a local network. [1]
- To serve it under a path such as /convert, set WEBROOT=/convert. [1]
- ConvertX documents no proxy configuration of its own; only the upstream is printed here. [1]
- ConvertX's README gives no WebSocket setting, so none is printed here.
DocuSeal app page
Upstream app:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03
# 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: 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
# Nothing to add: DocuSeal's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Any non-empty value other than false makes DocuSeal assume and enforce HTTPS; the compose file sets it to the host name. [2]
FORCE_SSL=sign.example.org
- DocuSeal's own compose file puts a plain Caddy reverse proxy in front of app:3000 with no extra settings, so only the upstream is printed here. [1]
- DocuSeal's compose file and README gives no WebSocket setting, so none is printed here.
BentoPDF app page
Upstream bentopdf:8080 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-03
# 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: 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
# Nothing to add: BentoPDF's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- The container is nginx serving static files; every PDF operation runs in the browser, so no upload limit or timeout applies on the proxy. [1]
- Digital signatures need a separate CORS proxy, which the README sets up outside this container. [1]
- BentoPDF's README gives no WebSocket setting, so none is printed here.
Termix app page
Upstream termix:8080 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08
# 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: 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
# Nothing to add: Termix's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Only if you add OIDC, GitHub, Google or LDAP sign-in: set EXTERNAL_FORCE_HTTPS=true so the sign-in callback URLs use https, which the Environment Variables page says is "required if behind reverse proxy". [2]
EXTERNAL_FORCE_HTTPS=true
- The docs' NGINX example adds the WebSocket upgrade headers; their Caddy example is a plain reverse_proxy, since "Caddy has native WebSocket support". [1]
Documenso app page
Upstream documenso:3000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08
# 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: 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
# Nothing to add: Documenso's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Set the public address; links in every email are built from it. [1]
NEXT_PUBLIC_WEBAPP_URL=https://documenso.example.org
- The docs give no reverse-proxy example of their own: Documenso listens on plain HTTP on port 3000 and NEXT_PUBLIC_WEBAPP_URL names the address it is reached at. [1]
- Documenso's self-hosting docs give no WebSocket setting, so none is printed here.
MeTube app page
Upstream metube:8081 · WebSockets: required [1] · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-08
# 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: 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
# Nothing to add: MeTube's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- The wiki: MeTube uses WebSocket (Socket.IO) for live updates, so the proxy must pass the Upgrade and Connection headers. Under a sub-path such as /metube/, set URL_PREFIX to match. [1]
TREK app page
Upstream app:3000 · WebSockets: required on /ws [1] · Upload limit: 500m [1] · Timeouts: 86400 [1] · docs checked 2026-10-08
# 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: 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
client_max_body_size 500m; # [1] proxy_read_timeout 86400; # [1]
# 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
}
# 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
For a TLS proxy the wiki's Environment Variables page pairs FORCE_HTTPS with TRUST_PROXY (and APP_URL is the base of links in emails); this compose file already sets all three. [1]
APP_URL=https://trek.example.org FORCE_HTTPS=true TRUST_PROXY=1
- The page's three hard requirements: WebSocket upgrades on /ws (proxy_read_timeout 86400 keeps them open), a body size of at least 500 MB for backup restores, and passing the Mcp-Session-Id header on /mcp if you use MCP. [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
# 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: 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
client_max_body_size 0; # [1]
# 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
}
# 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.
- client_max_body_size 0 turns nginx's upload limit off, so ROMs of any size can be uploaded through the web page. [1]
PLANKA app page
Upstream planka:1337 · WebSockets: required [1] · Upload limit: 50M [1] · Timeouts: defaults · docs checked 2026-10-08
# 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: 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
client_max_body_size 50M; # [1]
# 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
}
# 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
BASE_URL must match the address you configured on the proxy (Caddy page). [2]
BASE_URL=https://planka.example.org
- The docs' nginx example sends socket.io (location ~* \.io) with the WebSocket upgrade headers and long timeouts, and everything else as plain HTTP. The Caddy page adds header_up X-Forwarded-Proto {scheme}, "strictly required if you rely on secure cookies"; Caddy also sends that header on its own. [1]
- PLANKA docs: Reverse Proxy, Nginx (socket.io WebSocket, client_max_body_size 50M) checked 2026-10-08
- 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
# 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: 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
# Nothing to add: Gatus's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- The README has no reverse-proxy section; Gatus serves its page and API over plain HTTP on web.port, 8080 by default. [1]
- Gatus's README gives no WebSocket setting, so none is printed here.
- 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
# 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: 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
# Nothing to add: Homer's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- Homer is static files on port 8080 (PORT). To serve it under a sub-path such as /homer, the README's SUBFOLDER variable sets that path. [1]
- Homer serves static files; its README gives no WebSocket setting, so none is printed here.
- 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
# 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: 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
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]
}
# 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
}
# 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.
- The reverse-proxy page: forward every path, including the WebSocket upgrade at /ws that chat uses, and send RTMP to port 1935 directly, never to the web proxy. [2]
- Owncast docs: NGINX (WebSocket map, Authorization header) checked 2026-10-08
- 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
# 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: 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
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]
}
# 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
}
# 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
Put the domain into APPLICATION_HOSTS in both the app and the sidekiq service, without http:// or https://; the page warns the site will not work otherwise. [1]
APPLICATION_HOSTS=dawarich.example.org,localhost,::1,127.0.0.1
- Dawarich's reverse-proxy page gives no WebSocket setting in its nginx example, so none is printed here.
- 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
# 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: 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
# Nothing to add: OmniTools's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- The container is nginx serving static files on port 80; every tool runs in the browser, so no upload limit or timeout applies on the proxy. [1]
- OmniTools's README gives no WebSocket setting, so none is printed here.
- 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
# 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: 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
# Nothing to add: LibrePhotos's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
Behind an HTTPS proxy, the docs set CSRF_TRUSTED_ORIGINS to the address you use, with the scheme, or the Django admin rejects logins; this compose file sets it. [2]
CSRF_TRUSTED_ORIGINS=https://librephotos.example.org
- The upstream is LibrePhotos' own bundled proxy container (nginx on port 80), which sends each request on to the frontend or the backend; the compose file publishes only that container. [1]
- LibrePhotos's documentation gives no WebSocket setting, so none is printed here.
Homebox app page
Upstream homebox:7745 · WebSockets: required [1] · Upload limit: not given · Timeouts: 86400 [1] · docs checked 2026-10-09
# 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: 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
proxy_read_timeout 86400; # [1]
# 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
}
# 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
The Proxying page: behind a reverse proxy "you must set HBOX_OPTIONS_TRUST_PROXY to true"; this compose file sets it. [1]
HBOX_OPTIONS_TRUST_PROXY=true
- The docs' nginx example carries the WebSocket upgrade headers for /api/v1/ws/events and proxy_read_timeout 86400 for long-lived connections; their Caddy example is a plain reverse_proxy, since Caddy handles WebSocket upgrades on its own. [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
# 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: 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
# Nothing to add: Photoview's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- The page's Caddy example is one reverse_proxy line to Photoview's port, and its Traefik labels name port 80 with the http scheme. [1]
- Photoview's reverse-proxy page gives no WebSocket setting, so none is printed here.
- Photoview docs: Reverse Proxy (Traefik labels, Caddy, Apache) checked 2026-10-09
- 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
# 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: 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
# Nothing to add: SparkyFitness's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
SPARKY_FITNESS_FRONTEND_URL is the public address; the Environment Variables page calls it "crucial for CORS security and cookie session" handling. This compose file sets it. [2]
SPARKY_FITNESS_FRONTEND_URL=https://sparkyfitness.example.org
- The page sends the proxy to the frontend container on port 80 and lists the headers Nginx Proxy Manager should pass: Host, X-Real-IP, X-Forwarded-For and X-Forwarded-Proto (which Caddy and the nginx block below send anyway), plus X-Forwarded-Ssl on. [1]
- SparkyFitness's reverse-proxy page gives no WebSocket setting, so none is printed here.
bitmagnet app page
Upstream bitmagnet:3333 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09
# 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: 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
# Nothing to add: bitmagnet's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- The web UI and API are on 3333; the BitTorrent port 3334 (TCP and UDP) is not HTTP and stays outside the proxy. [1]
- bitmagnet has no login and its FAQ advises against a public instance ("The UI and API allow destructive actions"): add basic authentication on the proxy or keep the site on your network. [2]
- bitmagnet's documentation gives no WebSocket setting, so none is printed here.
13ft app page
Upstream 13ft:5000 · WebSockets: not in the docs · Upload limit: not given · Timeouts: defaults · docs checked 2026-10-09
# 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: 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
# Nothing to add: 13ft's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- The README's reverse-proxy example is an Apache VirtualHost with a plain ProxyPass to the app; nothing beyond forwarding is needed. It has no login, so a password on the proxy is the only thing between the internet and a page that makes your server fetch any URL. [1]
- 13ft's README gives no WebSocket setting, so none is printed here.
- 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
# 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: 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
# Nothing to add: Moodist's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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.
- The container is Caddy serving the static site on port 8080; nothing beyond forwarding is needed. [2]
- Moodist's README gives no WebSocket setting, so none is printed here.
- Moodist README (features, Self-Hosting with Docker Compose) checked 2026-10-09
- 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
# 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: 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
proxy_read_timeout 600s; # [1] proxy_send_timeout 600s; # [1]
# 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
}
# 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.
- The docs' nginx example sends /websocket with the upgrade headers and 600-second timeouts, because the web UI uses a WebSocket; their Caddy page: a plain reverse_proxy "seems to work without any special configuration for websockets". [1]
- OliveTin docs: Nginx (WebSocket on /websocket) checked 2026-10-09
- 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
# 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: 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
# Nothing to add: AdventureLog's docs give no setting beyond NPM's defaults. The project documents nothing more.
# 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
}
# 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
The Standard Deployment page: behind an HTTPS reverse proxy, set SITE_URL to your public HTTPS URL; the app derives CSRF_TRUSTED_ORIGINS and its other URLs from it. This compose file sets it. [1]
SITE_URL=https://adventurelog.example.org
- The Standard Deployment serves the frontend and the backend from one container on one port, so the proxy needs no path rules; the Caddy page's split by /media, /admin, /static and /accounts is for the two-container Advanced Deployment. [2]
- AdventureLog's documentation gives no WebSocket setting, so none is printed here.
- AdventureLog docs: Standard Deployment (one container, 2 GB RAM on first boot, updating) checked 2026-10-09
- 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 docs: WebSocket proxying (Upgrade and Connection are hop-by-hop headers, so they have to be passed explicitly; HTTP/1.1 to the upstream) checked 2026-09-26
- nginx docs: ngx_http_core_module, client_max_body_size (default 1m; 0 disables the check) checked 2026-09-26
- nginx docs: ngx_http_proxy_module, proxy_read_timeout (default 60s) checked 2026-09-26
- nginx docs: ngx_http_proxy_module, proxy_http_version (1.1 by default since nginx 1.29.7, 1.0 before) checked 2026-09-26
Nginx Proxy Manager
- Nginx Proxy Manager source: proxy_host.conf template (Websockets Support adds Upgrade/Connection and HTTP/1.1; the Advanced text is placed inside the server block; a 'location /' in it replaces NPM's own) checked 2026-09-26
- Nginx Proxy Manager source: nginx.conf (client_max_body_size 2000m, proxy_read_timeout and proxy_send_timeout 90s for every host) checked 2026-09-26
- Nginx Proxy Manager source: include/proxy.conf (sends Host $host, X-Forwarded-Proto, X-Forwarded-For and X-Real-IP) checked 2026-09-26
- Nginx Proxy Manager source: en.json (the field and toggle names: Domain Names, Scheme, Forward Hostname / IP, Forward Port, Cache Assets, Block Common Exploits, Websockets Support, Force SSL, HTTP/2 Support, Custom Nginx Configuration) checked 2026-09-26
Caddy
- Caddy docs: reverse_proxy (supports WebSocket connections; sets X-Forwarded-For, X-Forwarded-Proto and X-Forwarded-Host) checked 2026-09-26
- Caddy docs: request_body (max_size is an opt-in limit: bigger bodies get HTTP 413) checked 2026-09-26
Traefik
- Traefik docs: EntryPoints (http.redirections, http3, transport.respondingTimeouts.readTimeout default 60s) checked 2026-09-24
- Traefik docs: Docker routing labels (traefik.enable, routers, services, middlewares, traefik.docker.network) checked 2026-09-24
- Traefik docs: Exposing services, WebSocket supported out of the box checked 2026-09-24