SSL: no alternative certificate subject name matches target host name

I can’t conect my website with working SSL-Certificate to MainWP.
I’ve add URI and click on test connection a failure comes up.

Verbindungstest gescheitert.
Fehlermeldung: SSL: no alternative certificate subject name matches target host name ‘mydomain’

Server is nginx with Vhost first block:
server {
listen 80;
listen [::]:80;
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name mydomain;
return 301 https://www.mydomain$request_uri;

The Domains are matching with the installed Let’s Encrypt Certificate and the website is running in secure mode in all tested browser.

I can’t find the problem. Did anyone have the same problem in the past or have a solution?

Hey @Cyberworx

Welcome to the MainWP community!

Can you double-check that the SSL certificate exactly matches the domain name used in MainWP (including any subdomains)?
Mismatches like between www.mydomain and mydomain, can cause errors.

Another issue might be related to incomplete certificate chains.
Some applications, like MainWP, may require a complete chain to establish a connection, even if browsers don’t flag it.

Finally, it might be a good idea to have your host support investigate any potential issues with the certificates of both the Dashboard site and the Child site.

Thank you for your answer Bojan!

I’ve double-checked the domain entries, it is the same.
Also I’ve a second Certificate generated. Same issue.
MainWP is on the same machine, all other domains working fine.

I can’t see any failure in config files, that is my problem.

Thanks for checking that.

Would you mind opening a private Help Desk ticket so we can collect some additional information & investigate further?

And please refer to this Managers thread by its URL in the ticket.

1 Like

Thank you Bojan.

It is strange. I didn’t make any changes and when I just recorded it on video it suddenly went.

Good Morning Bojan,
Question, does MainWP first check the DNS entries and then the connection to the website?
If not, then that’s the problem.
If the A entry has changed, this error occurs. Now I’ve the same problem with another website that I have moved.

Hi @Cyberworx

MainWP does not check the DNS entries before making a cURL request during the Test Connection.

Usually, after site migration, it can take up to a few days before the DNS cache clears from your dashboard site server and DNS starts resolving properly.

If you want, you can wait for a few days if the issue resolves, or if you prefer, you can ask your dashboard site host provider to flush the DNS cache from the server and see if that speeds up the process.

1 Like

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