Karl Fathi

You're absolutely right, i've been really busy these pasts months, but i'll be checking everything and adding more examples soon. Thanks for your comments

Had the very same issue and traced it to the same cause. I believe this information should be included in [UPGRADING.md](https://github.com/zulip/docker-zulip/blob/main/UPGRADING.md) as a lot of people will encounter this issue.

X-Forwarded-Proto is correctly set and has been working since i've setup my Zulip instance (version 5). It's the update to version 7 that required using ``CSRF_TRUSTED_ORIGINS`` to resolve the "CSRF...

I personally don't use traefik, i have my own solution based on nginx-proxy, maybe @chgayot can shed some light on that part. In any case, if there's a need to...

There's an issue in the following block: ``` upstream mydomain.com { # neopolis_wordpress_1 server :80; } ``` It lacks the IP for the upstream server. The docker-compose.yml file in this...

Thanks a lot for raising this issue, i'm aware of it and in the process of updating this repo with a more robust setup. In the meantime, if you're interested...

Could you maybe post your nginx.tmpl and generated default.conf as well as full compose setup?

Looks like your nginx 'locks' instance is not on the nginx-proxy network: The block: ``` locks: depends_on: - nginx image: nginx container_name: locks restart: always environment: - VIRTUAL_HOST=locks.bertelsen.ca - LETSENCRYPT_HOST=locks.bertelsen.ca...

I don't think it will be possible until docker-letsencrypt-nginx-proxy-companion stops [relying on it to find the container](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/blob/1ea4335b510dda7b293865bfc05323f083af64bc/app/entrypoint.sh#L27) Maybe you could PR them?