Expand option does not seem to add www subdomain

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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: www.mindfulprogress.org

I ran this command: sudo certbot certonly --standalone --expand -d mindfulprogress.org -d www.mindfulprogress.org

It produced this output: You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry.

My web server is (include version): NGinx 1.24

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

My hosting provider, if applicable, is: GoDaddy

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

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

Hi,

When i initially ran certbot I only requested certificates for mindfulprogress.org. When i visit that site in the browser, without www. prepended, the browser says the connection is secure. However, when i add www. then the browser says insecure. Examining the certificate in the browser, it appears there is still only the mindfulprogress.org domain without the www one. After running the command to expand the existing cert on my server to the www also, i restarted my webserver many times but i see no change. What am i doing wrong?

Thanks,
Steven

Please show the output of:

sudo certbot certificates

Nevermind, my browser shows a perfectly fine connection to the www subdomain of your hostname. And I also see the www subdomain in the certificate information: you just need to look at the "Alternative Names" in the details.

You may just need to restart your browser to clear its cache. The cert looks fine as Osiris notes

3 Likes

God, that’s embarrassing. Thank you @Osiris and @MikeMcQ

Good ol’ IT restart solution.

3 Likes

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