Files
templates/blueprints/zulip/meta.json
Mauricio Siu 56df572522 fix: trust Dokploy's Traefik proxy via LOADBALANCER_IPS
Zulip 12 rejects requests forwarded by an untrusted reverse proxy with
a 500 "Proxy-Misconfiguration: Incorrect reverse proxy IPs set in
Zulip" error page. TRUST_GATEWAY_IP=True only whitelists the
container's default-route gateway IP, but Dokploy's Traefik connects
from its own container IP on the (dynamically-subnetted) compose
network, so it was never trusted.

Replace TRUST_GATEWAY_IP with LOADBALANCER_IPS covering the RFC1918
ranges, which Zulip feeds into nginx set_real_ip_from / its trusted
proxy list, so Traefik is trusted regardless of which Docker subnet it
connects from.

Also align meta.json version with the shipped image tag (12.1-0).

Note: the zulip-server image ships a HEALTHCHECK (/health, 300s start
period) and first boot runs full migrations, so Traefik only exposes
the router once the container turns healthy — expect several minutes
of 404 on the domain right after the first deploy.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 01:24:58 -06:00

19 lines
448 B
JSON

{
"id": "zulip",
"name": "Zulip",
"version": "12.1-0",
"description": "Open-source threaded team chat designed to keep team communication organized and productive.",
"logo": "zulip.svg",
"links": {
"github": "https://github.com/zulip/docker-zulip",
"website": "https://zulip.com/",
"docs": "https://zulip.readthedocs.io/projects/docker/"
},
"tags": [
"chat",
"collaboration",
"team",
"self-hosted"
]
}