# Site after servermove marked as insecure

**URL:** <https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298>\
**Category:** Help\
**Created:** [June 8, 2025, 5:59pm UTC](https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298 "2025-06-08T17:59:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![janvl](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@janvl](https://community.letsencrypt.org/u/janvl)\
**Post date:** [June 8, 2025, 5:59pm UTC](https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298/1 "2025-06-08T17:59:18Z")

</div>

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](https://www.traderwallet.pro)  
If i enter [http://www.traderwallet.pro](http://www.traderwallet.pro) it redirects to [https://traderwallet.pro](https://traderwallet.pro) which is correct.  
if i enter [http://traderwallet.pro](http://traderwallet.pro) it redirects to [https://traderwallet.pro](https://traderwallet.pro) which is correct.  
if i enter [https://traderwallet.pro](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

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [June 8, 2025, 6:06pm UTC](https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298/2 "2025-06-08T18:06:16Z")

</div>

> [@janvl](#):
>
> Now i have a url that Chrome says is insecure which is [https://www.traderwallet.pro](https://www.traderwallet.pro)

```nohighlight
$ 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.`)

```nohighlight
$ 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

```

---

<div class="post-metadata">

**Author:** ![janvl](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@janvl](https://community.letsencrypt.org/u/janvl)\
**Post date:** [June 8, 2025, 7:53pm UTC](https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298/3 "2025-06-08T19:53:00Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [June 8, 2025, 8:09pm UTC](https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298/4 "2025-06-08T20:09:24Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![janvl](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@janvl](https://community.letsencrypt.org/u/janvl)\
**Post date:** [June 8, 2025, 8:14pm UTC](https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298/6 "2025-06-08T20:14:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![janvl](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@janvl](https://community.letsencrypt.org/u/janvl)\
**Post date:** [June 8, 2025, 9:19pm UTC](https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298/7 "2025-06-08T21:19:43Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [July 8, 2025, 9:20pm UTC](https://community.letsencrypt.org/t/site-after-servermove-marked-as-insecure/238298/8 "2025-07-08T21:20:17Z")

</div>

Closed on July 8, 2025, 9:20pm UTC

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