Common SSL Errors

Below are the most common SSL-related errors and how to fix them.

ERR_CERT_COMMON_NAME_INVALID

The certificate is not valid for the domain you're visiting.

Solution: Ensure SSL is installed for the correct domain. If using www, make sure it's included in the certificate.

ERR_CERT_DATE_INVALID / NET::ERR_CERT_DATE_INVALID

The SSL certificate has expired or is not yet valid.

Solution: Renew your SSL certificate. For Let's Encrypt, try re-issuing the certificate in EGPNL.

ERR_SSL_PROTOCOL_ERROR

The server cannot establish a secure connection.

Solution: Clear browser cache, check SSL installation, or contact support if the issue persists.

Mixed Content Warning

The page loads some resources (images, scripts) over HTTP instead of HTTPS.

Solution: Update all resource URLs to use HTTPS. See "Fixing Mixed Content" section below.

ERR_TOO_MANY_REDIRECTS

The page is stuck in a redirect loop between HTTP and HTTPS.

Solution: Check for conflicting redirects in Nginx config and your application. See "Redirect Loop" section below.

Fixing Mixed Content

Mixed content occurs when HTTPS pages load HTTP resources:

For WordPress

  1. Install "Better Search Replace" plugin
  2. Search for: http://yourdomain.com
  3. Replace with: https://yourdomain.com
  4. Run on all tables

Or install "Really Simple SSL" plugin which handles this automatically.

For Custom Sites

  • Update hardcoded HTTP URLs in HTML, CSS, and JavaScript
  • Use protocol-relative URLs: //example.com/image.jpg
  • Or use relative paths: /images/logo.jpg
Find Mixed Content: Open browser developer tools (F12), go to Console tab, and look for mixed content warnings.

Fixing Redirect Loop

Redirect loops usually happen when:

  • Both .htaccess and Nginx have HTTPS redirects
  • WordPress forces HTTPS but server redirects back to HTTP
  • Conflicting plugin settings

Solution

  1. Remove any HTTPS redirects from .htaccess (not used in Nginx)
  2. Use only EGPNL's Force HTTPS option
  3. In WordPress, update Site URL and WordPress URL to HTTPS
  4. Clear all caches (browser, WordPress, CDN)

SSL Not Working After Installation

Check DNS Propagation

DNS changes can take 24-48 hours. Use DNSChecker.org to verify.

Clear Browser Cache

  1. Clear browser cache and cookies
  2. Try incognito/private browsing mode
  3. Test from a different device or network

Verify Certificate Installation

Use SSL Labs to check your certificate status.

Certificate Chain Issues

If you see "incomplete certificate chain" errors:

  • Ensure CA bundle/intermediate certificates are installed
  • For custom SSL, include all intermediate certificates
  • Use an SSL checker tool to identify missing certificates
Mobile Issues: Incomplete certificate chains often affect mobile browsers more than desktop browsers. Always test on multiple devices.

HSTS Issues

If you previously enabled HSTS and removed SSL:

  • Browsers remember HSTS settings and force HTTPS
  • Clear browser data or wait for HSTS to expire
  • Reinstall SSL to resolve immediately

Still Having Issues?

If none of these solutions work:

  1. Check EGPNL error logs for specific messages
  2. Verify your domain's DNS configuration
  3. Contact EGPHP support with details about the error

Related Articles

Free SSL Setup SSL Renewal Guide DNS Propagation Delay Website Not Loading