Certificate not valid

Help
1

My domain is: gisella-music.com

Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.4.33

Operating System CentOs 7

I can login to a root shell on my machine : yes

I'm using a control panel to manage my site: No

Using certbot 1.11.0

I have moved this website about 26 hours ago to a new domain and changed also 26 hours ago the DNS
to the new IP

I have successfully created 2 certs on the new server gisella-music.com and www.gisella-music.com I can see them in my /etc/letsencrypt/live/ directory using the command:

if I check the domain gisella-music.com at the ssl shopper I get this output:
Screenshot by Lightshot

if I check the domain www.gisella-music.com at the ssl shopper I get this output:
Screenshot by Lightshot
this error could be the issue but I don't know how to fix it

Thank you

2

Have you told your web server (whatever it is; CentOS is an operating system, not a web server) to use the newly-issued certs? When you used the certonly command to certbot, that tells it to just obtain the certs--you need to configure your web server to use them appropriately.

3 Likes
3

thank you for your message... how do I do that?
Anyway I have unassigned and removed all old certs on the old server

1 Like
4

Since you haven't even shared what web server you're using, I don't have a clue. I'd suggest you find that out, and once you do, try doing a web search for something like "configure SSL" and the name of your web server.

3 Likes
5

I have added the server info

6

So then,

3 Likes
7

ok thank you I ll try to do that

1 Like
8

Looks like you got two separate certificates, but only configured one of them in your webserver.

You could also easily gotten a single cert for both hostnames.

Is there also a reason why you're using the standalone plugin? That's not very common nor useful if one has a working webserver running. Why not use the --apache plugin, or if you don't want Certbot updating any webserver configuration file, not the --webroot plugin?

2 Likes
9

Hi osiris thank you for your message,

I am pretty new in this stuff as I used to create SSL certs using Plesk with the old server and now I am not using Plesk anymore, so the standalone is the only way I new to create certs, which is pretty boring because I need to stop the apache server every time on a production server, so next time I will definitely try the apache plugin.
Is it better to have one certificate for both domains? Or one cert for each domain?
Anyway the issue seems to be solved now, probably a DNS propagation issue.

1 Like
10

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