# Let's Encrypt with sub-subdomain?
**URL:** https://meta.discourse.org/t/lets-encrypt-with-sub-subdomain/264703
**Category:** Support
**Created:** [May 11, 2023, 7:32pm UTC](https://meta.discourse.org/t/lets-encrypt-with-sub-subdomain/264703 "2023-05-11T19:32:05Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@jimkleiber](https://meta.discourse.org/u/jimkleiber)
#### Post date: [May 11, 2023, 7:32pm UTC](https://meta.discourse.org/t/lets-encrypt-with-sub-subdomain/264703/1 "2023-05-11T19:32:05Z")
Continuing the discussion from [Set up Let’s Encrypt with multiple domains](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains/56685):
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?
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [May 11, 2023, 11:10pm UTC](https://meta.discourse.org/t/lets-encrypt-with-sub-subdomain/264703/2 "2023-05-11T23:10:52Z")
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?
---
### Author:  [@jimkleiber](https://meta.discourse.org/u/jimkleiber)
#### Post date: [May 11, 2023, 11:15pm UTC](https://meta.discourse.org/t/lets-encrypt-with-sub-subdomain/264703/3 "2023-05-11T23:15:06Z")
I think I’m running into the problem discussed here:
> [@Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy](https://meta.discourse.org/t/setup-multisite-configuration-with-lets-encrypt-and-no-reverse-proxy/175285/18):
>
> 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.
---
### Author:  [@jimkleiber](https://meta.discourse.org/u/jimkleiber)
#### Post date: [May 12, 2023, 12:53am UTC](https://meta.discourse.org/t/lets-encrypt-with-sub-subdomain/264703/4 "2023-05-12T00:53:38Z")
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.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [June 11, 2023, 12:54am UTC](https://meta.discourse.org/t/lets-encrypt-with-sub-subdomain/264703/5 "2023-06-11T00:54:14Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.