Closed maeries closed 1 week ago
The problem seems to be related with Caddy sending HTTP requests while Zulip only listens to HTTPS. I read that DISABLE_HTTPS: "True"
does not work anymore. Is there an alternative? The way it's described in the docs does not seem to be made to be used with docker https://zulip.readthedocs.io/en/latest/production/deployment.html#configuring-zulip-to-allow-http
Edit to be more clear: When I set Caddy2 to connect via port 80 I get the "Too many redirects". Then I set it to use port 443 I get "Client sent an HTTP request to an HTTPS server."
Figured it out. Under the environment variables in the docker-compose.yml you have to set DISABLE_HTTPS: 'True'
. Then set your reverse proxy to connect to the http (non s) port of zulip
We've got improved reverse proxy documentation that covers how to do this successfully, so closing.
I just installed Zulip via Docker on my server. When I open the webinterface in a Browser (I tried Firefox, Edge, Firefox Android) I only get a redirection error aka. "too many redirects"
How to reproduce
Or
up this docker-compose.yml
networks: caddy_net: external: true default: