# Zammad Docker-Compose and https

**URL:** <https://community.zammad.org/t/zammad-docker-compose-and-https/4320>\
**Category:** Technical assistance\
**Created:** [March 29, 2020, 12:55pm UTC](https://community.zammad.org/t/zammad-docker-compose-and-https/4320 "2020-03-29T12:55:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)\
**Post date:** [April 7, 2020, 10:38am UTC](https://community.zammad.org/t/zammad-docker-compose-and-https/4320/2 "2020-04-07T10:38:49Z")

</div>

According to this issue, forcing the container to handling https “is out of scope” [SSL for Docker Zammad · Issue #91 · zammad/zammad-docker-compose · GitHub](https://github.com/zammad/zammad-docker-compose/issues/91) .

Most users, as far as I can tell, actually use another webserver / proxy to proxy to the Zammad application within docker context. But I might be absolutely wrong here! 🙂

(e.g. see: [NGINX Reverse Proxy for HTTPS](https://community.zammad.org/t/nginx-reverse-proxy-for-https/2363) )

I thought that you might be able to use volumes to “overwrite” the configuration files - however, after a quick search I failed to find anything to that. So please take the last part of my answer as a possible way that I can’t proove and thus my mind possibly playing tricks on me. ☹

---

_[View the full topic](https://community.zammad.org/t/zammad-docker-compose-and-https/4320)._
