Subdomain not encrypted

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: certbot certonly --manual --manual-public-ip-logging-ok --preferred-challenges dns-01 --server -d "*" -d

It produced this output: IMPORTANT NOTES:

  • Congratulations! Your certificate and chain have been saved at:
    Your key file has been saved at:
    Your cert will expire on 2021-08-03. To obtain a new or tweaked
    version of this certificate in the future, simply run certbot
    again. To non-interactively renew all of your certificates, run
    "certbot renew"

  • If you like Certbot, please consider supporting our work by:

    Donating to ISRG / Let's Encrypt:
    Donating to EFF:

My web server is (include version): Apache2

The operating system my web server runs on is (include version): Ubuntu-20.04

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 0.31.0


I'm not seeing any issue with or Could you please elaborate what the issue is?

Edit: the foo subdomain does give an issue, I wasn't paying attention. The HTTP VirtualHost actually redirects to the apex domain in HTTPS, not to the foo subdomain with HTTPS, so I didn't catch the certificate error for the foo subdomain..


Welcome to the Let's Encrypt Community, Kehinde :slightly_smiling_face:

You have a wildcard A record (IPv4 address) in your DNS as shown in the dig screenshot below. Such practice is very non-standard. You need a ServerName * or ServerAlias * in one of your VirtualHosts in Apache to serve the correct certificate. Be sure the VirtualHost with either of those directives appears after the others in your configuration or your VirtualHosts for specific subdomains (like www) won't ever be used. You can read more in the official Apache documentation.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.