Using RocketChat Docker's image behind a proxy (nginx-letsencrypt-companion) about docker.official.image HOT 7 CLOSED

In the environment variables for rocketchat container i set Accounts_UseDNSDomainCheck: "false" instead of true.
@gurumark you should try to use this.
Do you use the nginx-proxy-companion method?

from docker.official.image.

Hi!
When dealing with containers that don't use 80 or 443 port with nginx-proxy and lets-encrypt-nginx-proxy-companion, I set an additional container that serves as a reverse proxy between nginx-proxy and the non-80-port container. Not very graceful, but works seamlessly.

from docker.official.image.

I have the same issue with the same setup (changed my own domain to example.com). I cannot get https connection using:

docker run -d
--name db
--net emdnet
--restart=unless-stopped
mongo:3.0 --smallfiles

docker run -d
--name rocketchat
--net emdnet
--restart=unless-stopped
-e ROOT_URL=https://chat.example.com
-e "VIRTUAL_HOST=chat.example.com"
-e "LETSENCRYPT_HOST=chat.example.com"
-e "LETSENCRYPT_EMAIL=[email protected]"
--link db
rocket.chat

@cybergrunge Do you have a configuration that works?

from docker.official.image.

Thanks. I discovered that in other thread. It works!

from docker.official.image.

I've been experiencing the same issues, but with traefik as opposed to nginx-proxy to proxy into the container. I'm going to try Accounts_UseDNSDomainCheck: "false" and see if that improves the situation. Thanks!

from docker.official.image.

Why are you setting Accounts_UseDNSDomainCheck: ? Seems to work fine with the Jwilder proxy and lets encrypt companion.

from docker.official.image.

Looks like this is resolved and not a bug but more of a support type issue.

Closing

from docker.official.image.