webzod
account

Install a certificate that covers this hostname on Apache

tls.cert.wrong_host · effort: minutes

Why it matters

The certificate the server presents is issued for other names, so browsers show a name-mismatch warning and refuse to continue silently. This happens when the host was never added to the certificate, or when the server picks the wrong certificate for the name.

The fix

  1. Give the host its own VirtualHost on port 443 with a matching ServerName (and ServerAlias for other names) and its own certificate files.
  2. Make sure the certificate lists every name in ServerName and ServerAlias.
  3. Test the configuration and reload Apache.
/etc/apache2/sites-available/site-ssl.conf
<VirtualHost *:443>
    ServerName example.com
    SSLEngine on
    SSLCertificateFile    /etc/letsencrypt/live/example.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem
</VirtualHost>

The examples use example.com. Replace it with your own domain.

Read the documentation (opens in a new tab)

Scan your domain to see whether this applies to you.