Incorrect SSL Certificate

B

BillyS

Verified User
Joined
Jul 17, 2021
Messages
464
I have several domains on the server and all work except for one. What happens is upon automatic renewal through DA / LetsEncrypt, the certificate shows the Common Name (CN) as:

ftp.domain.com

Whereas the other sites show as the naked domain (which is what I want)

domain.com

When I manually renew the certificate for the ftp.domain.com site, it renews correctly as the naked domain. Any idea why this might be happening?
 
maybe you have configured generate for domain and subdomains, and at moment of generation domain wasn't resolved, but subdomain was. some DNS issues maybe.
 
That could be the case. Had something similar before, where it was mail.domain.com instead of domain.com. I changed the order in some file which DA generated for the request, just don't remember where/what that file was at the moment and F1 racing starts in 5 minutes so no time to search.

You could try there or otherwise remove the SSL certificate and request new one, selecting the right order might fix it. I don't see the issue anymore since we now always use wildcard certificates.
 
BillyS said:
I have several domains on the server and all work except for one. What happens is upon automatic renewal through DA / LetsEncrypt, the certificate shows the Common Name (CN) as:

ftp.domain.com

Whereas the other sites show as the naked domain (which is what I want)

domain.com

When I manually renew the certificate for the ftp. domain .com site, it renews correctly as the naked domain Get SSL Certificate. Any idea why this might be happening?
Click to expand...
We had SSL certificates working properly until it expired. After that I installed the new Wildcard certificate, tested it and it seemed to be working fine. To my surprise today when checking from outside the Network, I realized Zimbra is still using the old certificate. I'm using Zimbra 8.8.15 and have already successfuly upgrade to latest patch P33, but the problem still persists even after redeploying the new certificates on the newly updated Zimbra. I looked somewhat extensively for anybody else with these problems, I found 2 other threads but they were from 2010 and 2017 and OPs pretty much just upgraded their Zimbras to fix it. Is there anything I can try? Thanks in advance!
 
You must log in or register to reply here.
Back
Top