Why Is My Accounting Website Showing An Ssl Not Private Warning
Summary
This guide helps you troubleshoot and resolve: Why Is My Accounting Website Showing An Ssl Not Private Warning. Follow the steps below to fix the issue.
Common Causes
Understanding the SSL Not Private Warning
An SSL certificate encrypts the connection between your website and your visitors. When a certificate is expired, misconfigured, or mismatched, browsers display an Your connection is not private or Not secure warning. For accountancy and bookkeeping practices, this erodes client trust and can raise concerns about the privacy of sensitive financial data.
Beyond client perception, a broken SSL connection can cause practical business disruption. Online contact forms, client portal logins, and payment pages may fail to submit or may be blocked by browsers entirely. From an SEO perspective, search engines may demote insecure sites in search results, reducing visibility for potential clients searching for accounting services.
Australian Compliance Context
Accountancy and bookkeeping practices routinely handle sensitive financial information, including tax file numbers, bank account details, and personal client records. Under the Privacy Act 1988 and the Australian Privacy Principles (APPs), Australian organisations are required to take reasonable steps to protect personal information from misuse, interference, loss, and unauthorised access or disclosure.
Transmitting client data over an insecure HTTP connection undermines these confidentiality obligations. While an SSL warning alone does not constitute a breach, it indicates that data in transit is not encrypted, which may conflict with professional expectations around data privacy and could complicate your response if a data incident occurs.
Quick Fix Steps
- Check whether the warning affects all pages or only specific pages.
- Check your computer's date and time settings.
- View your SSL certificate details to confirm the expiry date.
- Verify that HTTPS redirects are active.
- Use browser developer tools to identify mixed content resources.
- Update insecure resources from http:// to https://.
- Validate the fix by visiting the site in an incognito window.
- If the issue persists, Open a Ticket.
Detailed Instructions
Check Your Computer's Date and Time
SSL certificates are time-sensitive. If your computer's clock is incorrect, a valid certificate may appear expired or not yet valid, triggering a browser warning.
- On Windows, select Start, then Settings > Time & language > Date & time.
- Ensure Set time automatically is enabled.
- On macOS, select Apple menu > System Settings > General > Date & Time, and confirm Set date and time automatically is enabled.
- Restart your browser and reload the website.
View SSL Certificate Details in Your Browser
You can inspect the certificate directly from the browser to check the issuing authority, domain coverage, and expiry date.
- Open your website in Google Chrome, Microsoft Edge, or Mozilla Firefox.
- Click the padlock icon (or the warning triangle/not secure indicator) in the address bar.
- Select Connection is not secure or Certificate, depending on your browser.
- Review the Valid from and Valid to dates. If the current date falls outside this range, the certificate has expired.
- Confirm the certificate is issued for your exact domain (for example,
www.yourpractice.com.auandyourpractice.com.au). - Check the issuing certificate authority. If it is self-signed or unrecognised, browsers will not trust it.
Confirm HTTPS Redirects Are Active
Your website should automatically redirect all HTTP traffic to HTTPS. The method depends on your hosting environment.
cPanel
- Log in to your cPanel account.
- Navigate to Domains > Force HTTPS Redirect.
- Toggle the redirect to On for your domain.
Plesk
- Log in to your Plesk control panel.
- Go to Websites & Domains > Hosting Settings.
- Enable Permanent SEO-safe 301 redirect from HTTP to HTTPS.
- Click OK.
WordPress
- Log in to your WordPress admin dashboard.
- Go to Settings > General.
- Update the WordPress Address (URL) and Site Address (URL) fields to use
https://instead ofhttp://. - Click Save Changes.
- Alternatively, install and activate a plugin such as Really Simple SSL, then follow the plugin's setup wizard to enable automatic HTTPS redirection.
.htaccess (Apache Servers)
If you have access to your site's .htaccess file, you can add a redirect rule:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Identify and Resolve Mixed Content Errors
Mixed content occurs when a secure HTTPS page loads images, scripts, stylesheets, or other resources over an insecure HTTP connection. Browsers may block these resources or display a warning.
Use Browser Developer Tools
- Open your website in Chrome or Edge.
- Press F12 to open Developer Tools.
- Select the Security tab to view a summary of secure and insecure origins.
- Select the Console tab and reload the page. Look for messages labelled Mixed Content that list the specific
http://URLs being blocked. - Note the file paths or domains causing the errors.
Update Insecure Resources
- In WordPress, go to Settings > General and ensure both site URLs use
https://. - Edit pages or posts to replace any hardcoded
http://links in image sources, script tags, or stylesheet references withhttps://. - If you edited theme files directly, update the references in your theme directory.
- Clear your browser cache and any caching plugin cache, then reload the page.
Verify Certificate Installation and Chain of Trust
If the certificate is installed but the chain of trust is incomplete, browsers may still reject it.
- Use the browser certificate view described above to confirm the certificate authority is recognised.
- Check that intermediate certificates are installed on your web server alongside the primary certificate.
- If you are unsure who issued the certificate or where it is hosted, check your domain registrar account, hosting control panel, or billing records for SSL or security product invoices.
- If the provider cannot be identified, Open a Ticket for assistance.
Certificate Name Mismatch
A name mismatch happens when the certificate was issued for one domain but visitors access a different domain. For example, the certificate may cover yourpractice.com.au but not www.yourpractice.com.au, or vice versa.
- Confirm the certificate covers both the www and non-www versions of your domain.
- If you use a .au domain, ensure the certificate was issued for the exact registered domain name.
- Contact your certificate provider to reissue or update the certificate if the domain names do not match.
Cloudflare and CDN SSL Issues
If your website uses Cloudflare or another content delivery network, SSL termination may occur at the CDN edge rather than your origin server. Common issues include:
- Flexible SSL mode encrypting traffic between the visitor and Cloudflare, but not between Cloudflare and your server.
- Mixed content warnings caused by the origin server serving HTTP while Cloudflare expects HTTPS.
- Expired or missing origin certificates.
Log in to your Cloudflare dashboard and review the SSL/TLS settings. For most small business websites, Full or Full (Strict) encryption mode is appropriate. Ensure your origin server has a valid certificate installed if using Full (Strict).
Troubleshooting
Self-Signed or Untrusted Certificate
Browsers trust certificates issued by recognised certificate authorities. If you created a self-signed certificate internally, visitors will see a strong warning. Purchase or request a certificate from a trusted certificate authority and install it on your web server according to your hosting provider's instructions.
Validate the Fix
- Open a new incognito or private browsing window.
- Visit your website using the standard domain address.
- Confirm the padlock icon displays in the address bar without a warning triangle or
Not securelabel. - Test a contact form or client login page to ensure submissions work over HTTPS.
- If the warning returns or persists, Open a Ticket.
Still Having Issues?
💻 Open a Ticket