Continuing the discussion from Set up Let’s Encrypt with multiple domains: I’ve tried to update my multisite instance with a new site that uses a URL like test.forum.example.com, so I put -d test.forum.example.com in the app.yml (well, web_only.yml because it’s two-container), and when I click the URL, it says the connection is not private and when I explore the advanced tab, it shows the certificate is valid for all of the other sites I put into my multisite in the format of -d domain.com and yet this one doesn’t show up. When I click to ignore the warning, the Discourse site loads normally. Any idea if this is a problem with using a sub-subdomain format?

One of the domains I was using in the multisite configuration was not working because the domain name expired and it was causing an error before the new sub-subdomain was being processed. Once I changed the expired domain name and added an A-record for the new domain name for that, the problem fixed itself.

I think I’m running into the problem discussed here: [image] Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy Sysadmins No. Something about let’s encrypt changed at some point. I’ll have you take a closer look at what all needs you get changed inside the container to handle multiple domains.

Let's Encrypt with sub-subdomain?

Product Support

supermathie (Michael Brown) May 11, 2023, 11:10pm 2

The number of components doesn’t matter.

If you look at the LE logs, was it able to issue the certificate or did it error?

Topic		Replies	Views
LetsEncrypt certificate not renewing Self-hosting letsencrypt	6	594	December 9, 2024
Let's Encrypt and multisite (on 2 containers) Product Support	14	1284	August 20, 2018
SSL working on root, but not on www Product Support	28	4716	December 30, 2021
Issue installing on subdomain Product Support	4	1837	March 8, 2017
Workaround for the 1 week Let's Encrypt limit Self-hosting	2	1367	June 16, 2023

Let's Encrypt with sub-subdomain?

Related topics