Why does my website need an ssl certificate and https?
Summary
This guide helps you troubleshoot and resolve: Why does my website need an ssl certificate and https?. Follow the steps below to fix the issue.
Common Causes
HTTPS (Hypertext Transfer Protocol Secure) is the secure version of HTTP, the protocol used to transfer data between a web browser and a website. When a website uses HTTPS, the connection is encrypted using an SSL/TLS certificate. This encryption ensures that any information sent by a visitor—such as contact form submissions, login credentials, or payment details—cannot be read or intercepted by third parties.
Why SSL Certificates and HTTPS Matter
SSL certificates do more than just encrypt data. They also authenticate the identity of your website, assuring visitors that they are connecting to your legitimate organisation and not an impostor site. Modern web browsers display a padlock icon in the address bar when a site is secured, providing a visual cue that builds customer confidence.
Search engines such as Google use HTTPS as a ranking signal. Websites served over HTTPS are generally favoured in search results over unsecured HTTP sites, meaning a missing or expired certificate can directly impact your visibility to potential customers. Additionally, browsers now mark HTTP sites as “Not Secure,” which can deter visitors from completing forms or making purchases.
Certificate Types and Subdomain Coverage
When selecting an SSL certificate, it is important to consider which parts of your website need to be secured. A single-domain certificate secures one specific domain, such as www.yourdomain.com.au. If you operate multiple subdomains—for example, shop.yourdomain.com.au, blog.yourdomain.com.au, or client-portal.yourdomain.com.au—a wildcard certificate is more suitable. A wildcard certificate secures your primary domain and an unlimited number of first-level subdomains using an asterisk, such as *.yourdomain.com.au. This simplifies management and ensures that every section of your online presence is encrypted.
Quick Fix Steps
- Visit your website using
https://at the start of the URL. - Look for the padlock icon in the browser address bar.
- Click the padlock to view certificate details and check the expiry date.
- If the certificate is expired or missing, contact your hosting provider or certificate authority to renew or install a new one.
- Set up a permanent redirect from
http://tohttps://so all traffic uses the secure connection.
Detailed Instructions
Installing or Renewing an SSL Certificate via cPanel
- Log in to your cPanel hosting account.
- Navigate to the Security section and click SSL/TLS.
- Select Manage SSL sites to install or renew a certificate.
- Choose your domain from the dropdown menu.
- Paste the certificate, private key, and CA bundle provided by your certificate authority into the relevant fields.
- Click Install Certificate.
- Enable Force HTTPS Redirect using the Domains or SSL/TLS Status tool in cPanel.
- Test your website by visiting
https://yourdomain.com.auand confirming the padlock appears.
Installing or Renewing an SSL Certificate via Plesk
- Log in to your Plesk control panel.
- Navigate to Websites & Domains and select your domain.
- Click SSL/TLS Certificates.
- Select Add SSL Certificate or choose an existing certificate to renew.
- Complete the required fields and request the certificate from your provider, or upload the certificate files provided by your certificate authority.
- Once issued, select the certificate and click Apply to install it on your domain.
- Enable the Permanent SEO-safe 301 redirect from HTTP to HTTPS option under Hosting Settings.
- Test your website by visiting
https://yourdomain.com.auand confirming the padlock appears.
Setting Up an HTTPS Redirect
.htaccess or web.config file before making changes. If you are unsure, ask your hosting provider to apply the redirect for you.- Access your website’s root directory via FTP, File Manager, or SSH.
- Locate or create the
.htaccessfile (for Apache servers) or theweb.configfile (for IIS servers). - Download a backup copy of the file to your local computer before editing.
- Add a rewrite rule that redirects all
http://traffic tohttps://. - Save the file and clear your browser cache.
- Visit your site using
http://and confirm it automatically loads overhttps://.
Troubleshooting
Mixed-Content Errors
A mixed-content error occurs when an HTTPS page loads some resources—such as images, stylesheets, or scripts—over an insecure HTTP connection. Browsers may block these resources or display a warning, even though the main page is encrypted.
- Open your website in Google Chrome or Microsoft Edge.
- Right-click anywhere on the page and select Inspect, or press
F12to open Developer Tools. - Click the Console tab.
- Look for messages labelled “Mixed Content” that list insecure
http://URLs. - Edit your website’s code or content management system settings to replace those URLs with
https://equivalents. - If you use a CMS such as WordPress, update the WordPress Address and Site Address under Settings > General to use
https://, then use a search-and-replace plugin to update internal links in your database. - Clear your site cache and browser cache, then reload the page.
Certificate Expired or Not Trusted
- Click the padlock icon in the browser address bar and select Connection is secure or Certificate.
- Check the expiry date listed in the certificate details.
- If the certificate has expired, log in to your hosting control panel or certificate authority account and renew it.
- After installation, restart your web server if required to apply the new certificate.
- Use an online SSL checker tool to confirm the certificate is valid and trusted by browsers.
Browser Still Shows “Not Secure”
- Ensure all pages, not just the homepage, are loading over
https://. - Check for hard-coded
http://links in your theme, plugins, or website files. - Verify that your HTTPS redirect is active and functioning correctly.
- Clear your browser cache or test in an incognito/private browsing window.
Too Many Redirects or Redirect Loops After Enabling HTTPS
A “Too many redirects” error typically occurs when your server and your application or content management system are both attempting to force HTTPS at the same time, creating an infinite loop. This is common after manually adding a redirect rule in .htaccess or web.config while a platform-level HTTPS setting is also enabled.
- If you use WordPress, log in to the admin dashboard and go to Settings > General. Ensure both the WordPress Address (URL) and Site Address (URL) use
https://. - Check your hosting control panel for a Force HTTPS or SSL/TLS redirect toggle. If this is enabled, remove any duplicate redirect rules from your
.htaccessorweb.configfile. - If you use a caching plugin or service, purge all caches after changing redirect settings.
- Temporarily rename your
.htaccessfile (for example, to.htaccess.bak) to determine if the redirect rule is causing the loop. If the site loads, the rule needs to be corrected. - Clear your browser cache or test in an incognito/private browsing window before concluding the issue is resolved.
- If the loop persists, contact your hosting provider and Open a Ticket for assistance.
Maintaining a valid SSL certificate and enforcing HTTPS across your website protects your visitors, supports your search engine rankings, and reinforces trust in your Australian business. If you need assistance installing, renewing, or troubleshooting your certificate, Open a Ticket.
Still Having Issues?
đź’» Open a Ticket