The discussion revolves around setting up Let’s Encrypt for a sub-subdomain (e.g., test.forum.example.com) in a Discourse multisite instance. jimkleiber encountered an issue where the certificate wasn’t issued for the sub-subdomain, despite being correctly added to the app.yml file. The site loaded normally after bypassing the security warning, but the certificate did not include the sub-subdomain. supermathie clarified that the number of domain components doesn’t affect the process and suggested checking the Let’s Encrypt logs for errors. jimkleiber linked to a related thread and later identified the root cause: an expired domain in the multisite configuration was causing the issue. Once the expired domain was corrected and a proper A-record was added for the new sub-subdomain, the problem resolved itself jimkleiber.
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.