Skip to content
New: Laravel Hosting, Node.js Hosting & GitHub DeploysSee the plans →
Products
Solutions
Developers

Guides

Fix "your connection is not private" on your website

Why browsers show a privacy error on your domain, how free SSL issues itself here, and the three causes that account for nearly every broken padlock.

Introduction

Every site receives a free Let’s Encrypt certificate, and the platform issues and renews it automatically. When a browser shows “your connection is not private”, one of the three causes in this guide is usually responsible.

Checking the Certificate Status

Open your site in the panel and go to Security. The SSL certificates table lists every domain and subdomain on the site with its status and expiry date.

If the status is Active, the certificate exists and the problem is elsewhere. If the domain is missing or not Active, the certificate does not exist yet, and the cause is almost always DNS.

Common Causes

The Domain Does Not Point Here Yet

Let’s Encrypt verifies control of a domain before signing, so the domain must resolve to our servers first. After you connect a domain, DNS propagates, the certificate arrives, and the padlock appears. This usually completes within the hour, and most of that time is DNS.

If the site is new or the domain was only just pointed, wait, then check the Security table again. After more than a few hours, the domain is probably not resolving here at all. The guide to pointing your domain shows how to check where your DNS points.

The Page Loads Insecure Resources

If the Security table says Active but the browser still withholds the padlock, the page itself is the cause. Browsers mark a page as insecure if it loads even one image, stylesheet, or script over plain http://.

This mostly affects WordPress, which stores full URLs in its settings and content. Go to Settings, then General, and confirm that both the WordPress Address and Site Address start with https://. Old posts and themes may still contain hardcoded http:// links, which you may fix by running a search and replace over the database. The browser’s developer console lists every insecure resource on the page.

Visitors Reach the Insecure Address

A certificate does not force visitors to use HTTPS, so someone may still land on the http:// version of your site. On the Security page, each domain has a Force HTTPS toggle. Once the certificate shows Active, turn it on to redirect every plain request to the secure version. You should enable this on every live site.

Using Cloudflare

Cloudflare adds another place where SSL may be misconfigured. A wrong setting there produces a privacy error or an infinite redirect loop, regardless of what the panel shows. For more information, see the Cloudflare guide.

Custom Certificates

You do not need to buy, upload, or renew a certificate. Certificates renew themselves before they expire. The panel’s Install custom SSL button is for the rare case where you already own a paid certificate and want to use it.

Keep reading

Other guides

Start building today

Laravel apps with queues and Horizon, WordPress stores, Node.js servers. One container with SSH, deploys from GitHub and people who answer. One bill a year.

Launch my site