# HTTPS not working on Synology Docker

**URL:** <https://forums.rocket.chat/t/https-not-working-on-synology-docker/10472>\
**Category:** Community Support\
**Created:** [February 27, 2021, 3:19pm UTC](https://forums.rocket.chat/t/https-not-working-on-synology-docker/10472 "2021-02-27T15:19:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gebowunjo](https://avatars.discourse-cdn.com/v4/letter/g/5e9695/32.png) [@Gebowunjo](https://forums.rocket.chat/u/Gebowunjo)\
**Post date:** [February 27, 2021, 3:19pm UTC](https://forums.rocket.chat/t/https-not-working-on-synology-docker/10472/1 "2021-02-27T15:19:27Z")

</div>

Hi everyone !

I have successfully installed rocket.chat on my Synology NAS, but I am having trouble getting HTTPS to work with it.

I’m working on a DS916+ running DSM 6.2.3-25426 Update 3. I’ve got the latest Docker application from synology installed. Also I did install a better version of Docker-compose with bash and installed Rocket-Chat with the default configuration file found on the Rocket chat website. I just replace the default “ROOT\_URL”.

I can access rocket chat with HTTP but not with HTTPS in local. Is there something I missed that I should have done ?

Thanks in advance for your replies.

---

<div class="post-metadata">

**Author:** ![beenmeckel](https://avatars.discourse-cdn.com/v4/letter/b/8dc957/32.png) [@beenmeckel](https://forums.rocket.chat/u/beenmeckel)\
**Post date:** [March 23, 2021, 9:41pm UTC](https://forums.rocket.chat/t/https-not-working-on-synology-docker/10472/2 "2021-03-23T21:41:50Z")

</div>

I will look into this. I know a bit f these things, but somehow I cannot managed it all. A SSL-certificate for the Synology interface is quite simple.

---

<div class="post-metadata">

**Author:** ![Gebowunjo](https://avatars.discourse-cdn.com/v4/letter/g/5e9695/32.png) [@Gebowunjo](https://forums.rocket.chat/u/Gebowunjo)\
**Post date:** [March 25, 2021, 9:46am UTC](https://forums.rocket.chat/t/https-not-working-on-synology-docker/10472/3 "2021-03-25T09:46:52Z")

</div>

I just found the solution. In fact the reverse proxy on my Synology was badly configurated.  
I reconfigured it and it works !  
Thanks
