Prefixed Certificate Doesn't Work?

[Zarken]

My domain is: gIdentity.net (works) addons.gidentity.net (doesnt work)

I ran this command: https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04

My web server is (include version): nginx/1.12.2

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

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): No

As mentioned in the domain section above, my main site works but not my prefixed site. I’ve just “updated” my certificate to include addons. but apparently it doesn’t work? (used the tutorial above)

[jared.m]

You obtained a certificate that covers both names, but that certificate is not being presented by your Nginx configuration. Instead, only the certificate covering gIdentity.net is being sent. Could you show us the exact commands you used (not a tutorial you followed…), as well as the output of certbot certificates?

[Osiris]

And show us the appropriate nginx configuration file.

[Zarken]

cerbot certificates output: https://puu.sh/zVyzy/a4ff7adcdc.png
the nginx config for addons.gidentity.net = https://puu.sh/zVyD5/747427072e.png
Commands i used:

sudo add-apt-repository ppa:certbot/certbot
sudo apt-get update
sudo apt-get install python-certbot-nginx
sudo certbot --nginx -d gidentity.net -d addons.gidentity.net
sudo certbot renew --dry-run

Thanks for the help

[stevenzhu]

Hi,

All certificate I saw logged was for your root domain only.

Can you try issue certificate for both domains. (Or a wildcard)?

Okay… The last certificate you issued contains both domains. (https://crt.sh/?id=375599196)

However, did you deploy the certificate to corresponding vHost? (also restart the server?)

Thank you

P.S. it’s “subdomain” not “prefixed” domain.