Tracking domain SSL error (ERR_SSL_VERSION_OR_CIPHER_MISMATCH) despite verified CNAME

Hi everyone,

I’m running into an issue with my MailWizz tracking domain and could use some help.

Problem:
When I try to access my tracking URL in the browser, I get this error:

This site can’t provide a secure connection <br>tracking.xyz uses an unsupported protocol. <br>ERR_SSL_VERSION_OR_CIPHER_MISMATCH<br>
What I’ve done so far:

  • Added the tracking domain (tracking.xyz) in MailWizz
  • Created the required CNAME record in my DNS provider pointing to the MailWizz tracking domain
  • MailWizz dashboard shows the domain as verified
  • The domain resolves correctly, but HTTPS does not work
Issue:

  • The tracking domain is not serving over HTTPS
  • It appears there is no valid SSL certificate or there’s a mismatch in SSL configuration
Questions:

  1. Does MailWizz automatically issue SSL certificates for tracking domains, or do I need to install one manually on the server?
  2. If manual setup is required, should SSL be installed on the delivery server (where MailWizz is hosted) or on the DNS/domain side?
  3. If using Let’s Encrypt, what’s the correct way to generate a certificate for a CNAME-based tracking domain?
  4. Could this be related to server config (NGINX/Apache) not handling the tracking domain properly?
Any guidance or steps to fix this would be greatly appreciated.

Thanks in advance!
 

Attachments

  • mailwizz.PNG
    mailwizz.PNG
    16.3 KB · Views: 0
Does MailWizz automatically issue SSL certificates for tracking domains, or do I need to install one manually on the server?
You need to handle this on your own.

If manual setup is required, should SSL be installed on the delivery server (where MailWizz is hosted) or on the DNS/domain side?
Does not matter as long as accessing the trracking domain via https works. can be local or cloudflare, etc

If using Let’s Encrypt, what’s the correct way to generate a certificate for a CNAME-based tracking domain?
Depends on your setup really, if you're using a known control panel like plesk/cpanel, you can add each cname as a domain alias and generate ssl for them easily.
  1. Could this be related to server config (NGINX/Apache) not handling the tracking domain properly?
No, it has nothing to do, this is just invalid ssl.
 
Back
Top