Site after servermove marked as insecure

Hi,

i moved a site from a server with Plesk to one with ISPConfig.
I had ISPConfig produce new certificates.
I redirect http to https
1 redirect www.domain.tld to domain.tld

Now i have a url that Chrome says is insecure which is https://www.traderwallet.pro
If i enter http://www.traderwallet.pro it redirects to https://traderwallet.pro which is correct.
if i enter http://traderwallet.pro it redirects to https://traderwallet.pro which is correct.
if i enter https://traderwallet.pro the sites loads as expected.

The browsercache was emptied, tested on edge - chrome - firefox - opera, the same happening in all these browsers.
I restarted Apache2 with no result.
This is a vserver running ubuntu 24.04 with apache.

How can i get letsencrypt to ditch the old certificate that seems to hang somewhere in the system?

Regards,
Jan

$ curl -IL https://www.traderwallet.pro/
curl: (60) SSL: no alternative certificate subject name matches target host name 'www.traderwallet.pro'

Your certificate does not include www.traderwallet.pro (note www.)

$ openssl s_client -connect www.traderwallet.pro:443 </dev/null | openssl x509 -noout -ext subjectAltName
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = E6
verify return:1
depth=0 CN = traderwallet.pro
verify return:1
DONE
X509v3 Subject Alternative Name: 
    DNS:traderwallet.pro
3 Likes

Thanks for the fast response 9peppe!

Is there a manual way to add www.traderwallet.pro to the certificate? Years ago i used certbot but i am used (and spoiled) to let ISPConfig handle the certificates.

Regards,
Jan

I have no experience with ispconfig but you can't "add" to an already issued certificate; you need to issue a new certificate with both www.traderwallet.pro and traderwallet.pro

(it's not mandatory for both names to be on the same certificate, I'm assuming it will be easier)

3 Likes

Thanks, this is the first time this happens. I will ask the ISPConfig developer.
I guess i will need to disable all SSL for the domain first and then start it new.
I will notify when it is solved.

Regards,
Jan

3 Likes

Hi,

I have disabled all SSL for the site in ISPConfig and then enabled it again.
Now it is working. Thanks 9peppe for setting me on the right trail.

Regards,
Jan

4 Likes