How to Troubleshoot SSL and HTTPS Problems

Overview

SSL allows your website to use HTTPS, which encrypts the connection between your visitors and your website.

When SSL is working correctly, visitors should be able to access your website using an address such as:

https://example.com

If SSL or HTTPS is not configured correctly, visitors may see warnings such as:

"Your connection is not private"
"Your connection is not secure"
"Certificate expired"
"Certificate is not valid"
"Too many redirects"
"This site can't provide a secure connection"

HTTPS problems can be caused by the SSL certificate, DNS, domain configuration, redirects, WordPress settings, or website content.

Before You Start

First, determine exactly what is happening.

Try visiting both:

http://example.com

and:

https://example.com

Then determine whether:

HTTPS loads normally.
HTTPS loads but shows a browser warning.
HTTP works but HTTPS does not.
HTTPS works but HTTP does not redirect correctly.
The website redirects repeatedly.
Only certain pages produce warnings.
Images or other resources are not loading securely.

This will help narrow down the problem.

1. Check Whether Your Domain Uses the Correct DNS

SSL certificates are issued for a specific domain, so your domain needs to reach the correct hosting environment.

If your DNS is managed through cPanel, open:

cPanel → Domains → Zone Editor

Check the relevant records for your domain.

Depending on your setup, this may include:

A records
AAAA records
CNAME records

If your domain points somewhere other than the server where the SSL certificate is installed, HTTPS may not work as expected.

If DNS is managed by another provider, check the records there instead.

2. Check the Domain in cPanel

Open:

cPanel → Domains

Make sure the affected domain is actually configured on your hosting account.

Check:

Domain name
Document root
Domain status
Whether the domain was recently added
Whether the domain was recently moved

If the domain was just added, SSL issuance may take some time depending on the configuration and validation process.

3. Check Your SSL Certificate

Have Freedom Hosting offers free SSL certificates through Let's Encrypt, as well as paid SSL options.

For most ordinary websites, the free SSL option is sufficient.

If your certificate is missing, expired, invalid, or issued for the wrong domain, HTTPS may display a warning.

Check the SSL-related information available in cPanel.

Depending on the hosting configuration, SSL management may be available through:

cPanel → Security → SSL/TLS Status

The exact options available may vary depending on your hosting plan and server configuration.

4. Make Sure the Certificate Covers the Correct Domain

An SSL certificate must cover the hostname visitors are using.

For example, these are different hostnames:

example.com
www.example.com

A certificate that covers one does not automatically mean every other hostname is covered.

If visitors receive a certificate warning when using www.example.com but not example.com, check whether the certificate includes both names.

The same applies to subdomains such as:

shop.example.com
mail.example.com

5. Check Whether the Certificate Has Expired

An expired certificate can cause browsers to display serious security warnings.

If your certificate is expired, check your SSL management tools in cPanel.

Have Freedom Hosting may automatically issue and renew supported certificates, but renewal can occasionally fail because of DNS, domain, or configuration problems.

If automatic renewal has failed, the cause needs to be corrected before the certificate can be successfully renewed.

6. Check for Mixed Content

Sometimes HTTPS itself is working correctly, but the page still produces a browser warning because some content is being loaded over HTTP.

This is called mixed content.

For example, your page may load securely:

https://example.com

but attempt to load an image from:

http://example.com/images/logo.png

Other examples include:

Images
CSS files
JavaScript
Fonts
Embedded content
External resources

Mixed content is particularly common after converting an existing website from HTTP to HTTPS.

7. Check Your WordPress URLs

If your website uses WordPress, make sure WordPress knows that your website uses HTTPS.

In WordPress, check:

Settings → General

Look at:

WordPress Address (URL)
Site Address (URL)

For a properly configured HTTPS website, these will generally use:

https://

rather than:

http://

Do not change these settings blindly on a broken site.

If changing them causes additional problems, restore the previous configuration or use your backup.

8. Check WordPress Plugins

Some WordPress plugins modify HTTPS or redirect behavior.

This includes plugins related to:

SSL
Security
Caching
Redirects
Performance
CDN integration

If the HTTPS problem appeared immediately after installing or updating a plugin, that plugin may be involved.

Temporarily disabling the suspected plugin can help determine whether it is responsible.

9. Check `.htaccess`

Custom .htaccess rules can affect HTTP and HTTPS behavior.

For example, a website may contain rules intended to redirect:

http://example.com

to:

https://example.com

Incorrect rules can cause:

Redirect loops
500 errors
Unexpected redirects
Pages becoming inaccessible

You can review .htaccess through:

cPanel → Files → File Manager

For a typical primary website, it may be located at:

public_html/.htaccess

Make a backup before changing .htaccess.

10. Watch for Redirect Loops

A redirect loop occurs when the website continually redirects the visitor between URLs.

For example:

HTTP
 ↓
HTTPS
 ↓
HTTP
 ↓
HTTPS
 ↓
HTTP

Your browser may eventually report:

"Too many redirects."

Common causes include:

WordPress HTTPS settings
.htaccess rules
Redirect settings
Security plugins
Reverse proxy or CDN configuration
Conflicting HTTP/HTTPS settings

Check your redirect configuration and recent changes before modifying multiple settings.

11. Check cPanel Redirects

If you created a redirect through cPanel, review:

cPanel → Domains → Redirects

Look for redirects involving:

HTTP
HTTPS
www
Non-www
Old domains
New domains

Make sure multiple redirects aren't competing with one another.

A simple website should generally have one clear preferred URL structure.

12. Check Your CDN or Proxy

If your website uses a CDN or reverse proxy, HTTPS may involve more than just your hosting server.

The visitor may connect to:

Visitor
   ↓
CDN / Proxy
   ↓
Have Freedom Hosting
   ↓
Website

This can introduce additional SSL settings.

If you're using a third-party CDN or proxy, check its HTTPS settings as well.

Do not change SSL modes randomly. Some configurations can create redirect loops or certificate problems.

13. Clear Your Browser Cache

Sometimes your browser retains an old redirect or cached website resource.

After making changes, test the website using:

A private/incognito window
Another browser
Another device

This helps determine whether the problem is actually server-side.

14. Check From Another Network

If possible, test the website from another internet connection.

For example:

Mobile connection
Another Wi-Fi network
Another computer

If the website works normally elsewhere, the issue may involve local DNS caching or browser caching rather than the hosting account itself.

15. Check the Certificate Warning Carefully

Browser warnings often provide useful information.

Pay attention to messages such as:

Certificate expired
Certificate does not match the domain
Certificate authority not trusted
Certificate revoked
Connection not secure
Certificate is only valid for another hostname

The exact message can help determine what needs to be fixed.

If contacting support, include the exact warning rather than simply saying "SSL doesn't work."

Common HTTPS Problems

"HTTPS Does Not Work at All"

Check:

Domain configuration
DNS
SSL certificate
Certificate coverage
Recent domain changes

"My Certificate Is Expired"

Check your SSL management tools in cPanel.

If automatic renewal failed, there may be a DNS or domain validation issue preventing the certificate from being renewed.

"HTTPS Works but My Browser Says the Site Isn't Fully Secure"

Check for mixed content.

Look for resources still being loaded using:

http://

instead of:

https://

"My Website Says Too Many Redirects"

Check:

WordPress URL settings
.htaccess
cPanel redirects
Security plugins
CDN/proxy settings

Look for two systems trying to enforce different URL structures.

"The Website Works Without www but Not With www"

Check whether:

example.com

and:

www.example.com

both resolve correctly and are covered by the SSL certificate.

Review DNS and domain configuration as necessary.

"The Website Works With www but Not Without www"

The same principle applies.

Make sure both hostnames are configured appropriately and that your preferred version redirects correctly if necessary.

What Not to Do

Avoid:

Ignoring a browser certificate warning.
Disabling browser security warnings.
Installing random SSL plugins.
Repeatedly changing SSL settings without understanding them.
Creating multiple conflicting redirects.
Deleting certificates or configuration files without a backup.
Changing DNS records randomly.
Assuming every HTTPS problem is caused by the SSL certificate itself.

An HTTPS problem can originate from several different parts of the website configuration.

When to Contact Have Freedom Hosting

Contact Have Freedom Hosting Support if:

Your domain points to the correct hosting account but SSL cannot be issued.
Your certificate appears to be missing or incorrectly configured.
Automatic certificate renewal appears to have failed.
You receive a certificate mismatch warning.
You cannot determine why HTTPS is not working.
The problem appears to involve the hosting server's SSL configuration.
You've checked your website configuration but continue receiving errors.

When opening a support ticket, provide:

Your domain.
Whether you're using www or a non-www address.
The exact HTTPS URL you're testing.
The exact browser warning or error.
When the problem started.
Whether HTTP works.
Whether you recently changed DNS, WordPress, redirects, or SSL settings.
Screenshots if helpful.

Never provide passwords, private keys, authentication codes, or other sensitive credentials in a support ticket.

Quick SSL and HTTPS Checklist

Confirm the domain points to the correct hosting account.
Check DNS records.
Check the domain in cPanel.
Check SSL/TLS status.
Confirm the certificate covers the correct hostname.
Check whether the certificate is expired.
Test both http:// and https://.
Check for mixed content.
Check WordPress URL settings.
Check SSL/security plugins.
Review .htaccess if applicable.
Check cPanel redirects.
Check CDN or proxy settings if applicable.
Test in a private browser window.
Test from another device or network.
Record the exact browser error before contacting support.

Need Help?

HTTPS problems can look complicated, but the exact browser warning and the point where the connection fails usually provide useful clues.

Work through the checklist above and avoid making multiple configuration changes at once.

If you still cannot determine the cause, contact Have Freedom Hosting Support with the exact domain, URL, and error you're seeing so the problem can be investigated more efficiently.

Knowledgebase

Categories

Categories