Let's Encrypt cert does not cover channels.loomio.example.com
eternaltyro opened this issue · comments
Somehow, there's a new sub-subdomain in the network tab of Firefox that is channels.loomio.example.com. The domain I chose for loomio was loomio.example.com.
channels.loomio.example.com - does not have a valid certificate (or docker-compose components didn't create for it) and this is cause for potential errors in the page.
Hi @eternaltyro - Sorry about this, is this a new site or one that you've been running a while?
You need to create a channels_env (based on scripts/default_channels_env from this repo) alongside the existing env file.
This will trigger a certificate fetch from letsencrypt, however you will need to add a CNAME record for channels.loomio.example.com -> loomio.example.com too
Hi @eternaltyro - Sorry about this, is this a new site or one that you've been running a while?
This is a new site.
You need to create a
channels_env(based on scripts/default_channels_env from this repo) alongside the existingenvfile.This will trigger a certificate fetch from letsencrypt, however you will need to add a CNAME record for channels.loomio.example.com -> loomio.example.com too
I will try this and report back if there are problems. Thanks for now 👍
@robguthrie once I do the changes, should I restart the stack? Is there a safe way to do it ?
Thanks for the PR!
the restart process just as documented in the readme:
docker-compose down; docker-compose up -d