Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Local WP SSL Not Working: Causes and How to Fix It

Local WP SSL Not Working: Causes and How to Fix It

Short answer

Local WP creates a self-signed certificate that browsers distrust until you click Trust on the site's Overview tab and restart the browser. If it still fails, switch the router mode to Site Domains, set both WordPress URLs to https and fix mixed content.

Key takeaways

  • Local's certificates are self-signed and must be trusted first.
  • Fully restart the browser after clicking Trust.
  • Firefox needs system certificates enabled or a manual exception.
  • SSL works with the Site Domains router mode.
  • Change WordPress URLs to https and run search and replace.
  • Renaming a site creates a new certificate to trust.

Why is SSL not working in Local WP?

SSL usually fails in Local because the site's certificate is not trusted yet, the router mode is set to localhost, WordPress still uses http URLs, or your browser keeps its own certificate store.

Local, the free desktop app from WP Engine for running WordPress sites on your computer, creates a self-signed certificate for each site. Browsers do not trust self-signed certificates until you tell your operating system to trust them.

That is why a fresh Local site often shows Not secure, a red padlock, or errors like NET::ERR_CERT_AUTHORITY_INVALID on its https address.

The fix is rarely complicated. In most cases you click the Trust button, restart the browser and update the site URLs to https.

If you are new to Local, our guide to installing WordPress using Local WP covers the basic setup this article builds on.

What are the common causes at a glance?

Most Local SSL problems match one of a few causes, and each has a quick first check.

SymptomLikely causeFirst fix
Not secure warning on httpsCertificate not trustedClick Trust in the site overview
Works in Chrome, fails in FirefoxFirefox uses its own certificate storeLet Firefox use system certificates
No https option at allRouter mode set to localhostSwitch to Site Domains router mode
Padlock broken on some pagesMixed content from http URLsUpdate URLs to https
Redirect loop after switchingMismatched site URLs or a plugin forcing httpsCheck WordPress Address and Site Address
Error after renaming the siteOld certificate for the old domainRe-trust or regenerate the certificate

Find your symptom in the table and jump to the matching section below.

Have you trusted the certificate in Local?

Open the site in Local, look for the SSL setting on the Overview tab and click Trust, then fully restart your browser.

Local cannot make browsers trust a certificate on its own. The Trust button adds the site's certificate to your operating system's trusted store.

  1. Open Local and select the site in the left sidebar.
  2. Stay on the Overview tab.
  3. Find the SSL row and click Trust.
  4. Approve the system prompt. macOS may ask for your password, and Windows may show a security warning.
  5. Quit the browser completely and open it again.

Local's own SSL in Local documentation describes this step. Restarting matters because browsers cache certificate decisions for the session.

If the Trust button seems to do nothing, check whether the certificate was added. On a Mac, open Keychain Access and search for your site's domain.

How do you fix trust on macOS?

On macOS, open Keychain Access, find the certificate for your Local site, open it and set it to Always Trust, then restart the browser.

Sometimes the certificate lands in the keychain but is not marked as trusted. You can fix that by hand.

  1. Open Keychain Access from Applications, then Utilities.
  2. Choose the System or login keychain and search for your site domain, such as mysite.local.
  3. Double-click the certificate.
  4. Expand Trust and set When using this certificate to Always Trust.
  5. Close the window and enter your password to save.

Local has a separate page on managing a site's SSL certificate in macOS. Safari and Chrome both read the macOS keychain, so the fix covers both.

If you see two certificates for the same domain, delete the older one. A stale certificate from a previous install can confuse the browser.

How do you fix trust on Windows?

On Windows, the Trust button adds the certificate to the Windows certificate store, so check that it appears there and restart every browser window.

Chrome and Edge use the Windows certificate store. If the Trust step was blocked by antivirus software or cancelled, the certificate is missing.

You can check by pressing Windows + R, typing certmgr.msc and opening Trusted Root Certification Authorities. Look for an entry matching your site domain.

If it is not there, click Trust in Local again and accept the prompt. Some security tools block certificate installs silently, so pause them briefly if needed.

After adding it, close every browser window, including ones in the system tray. Chrome often keeps running in the background.

Why does Firefox still show a warning?

Firefox keeps its own list of trusted certificates, so a certificate trusted by your operating system may still be rejected unless Firefox is set to use system certificates.

You have two ways to fix it:

  • Use system certificates. Firefox can read the operating system store. Mozilla explains this in its guide on setting up certificate authorities in Firefox.
  • Add an exception. On the warning page, click Advanced, then Accept the Risk and Continue. Firefox remembers this for the site.

The exception is quick for a single site. The system certificate option is better if you run many Local sites.

Is your router mode blocking SSL?

Local's SSL works with the Site Domains router mode, so if you use localhost router mode, switch it in Local's preferences and restart the site.

Local offers two router modes. Site Domains gives each site an address like mysite.local. localhost runs sites on localhost with different port numbers.

The localhost mode is handy on locked-down machines, but it limits SSL. To switch:

  1. Open Local's Preferences.
  2. Go to the Advanced tab.
  3. Find Router Mode and choose Site Domains.
  4. Apply the change and restart your sites.

After switching, your site uses its .local domain again. Trust the certificate if Local asks.

If you were also struggling to reach the site at all, see our guide on opening the WordPress dashboard in localhost.

Are your WordPress URLs still using http?

If WordPress Address and Site Address still start with http, pages load without SSL or mix secure and insecure content, so change both to https.

A trusted certificate is only half the job. WordPress must also generate https links.

  1. Log in to the dashboard of your Local site.
  2. Go to Settings, then General.
  3. Change both addresses from http to https.
  4. Save and log in again.

Links already stored in posts and widgets keep the old http address. Run a search and replace with a tool like WP-CLI, which Local includes through the Open site shell option.

wp search-replace 'http://mysite.local' 'https://mysite.local' --all-tables

The wp search-replace command reference explains each flag. Run it with --dry-run first to see what will change.

How do you fix mixed content on a Local site?

Mixed content happens when an https page loads images, scripts or styles over http, so replace those http URLs or force https for assets.

The browser shows a broken or warning padlock even though the certificate is valid. The page itself is secure, but some files are not.

Open your browser's developer tools and check the Console. Mixed content warnings list every file loaded over http.

Common sources include hard-coded image links, theme options, page builder data and custom CSS. MDN's page on mixed content explains why browsers block some of these files.

After running search and replace, clear any caches. Page builders such as Elementor store CSS files that may still include old URLs, so regenerate them from the builder's tools.

What if https causes a redirect loop?

A redirect loop on a Local site usually comes from mismatched site URLs, a plugin forcing https, or conflicting redirect rules, so align the URLs and disable the plugin to test.

Check these in order:

  • Site URLs. Both addresses in General Settings should match exactly, including https.
  • SSL plugins. Plugins that force https can loop if the certificate or URLs are wrong. Deactivate them to test.
  • wp-config constants. Look for WP_HOME, WP_SITEURL or FORCE_SSL_ADMIN values that disagree with the settings screen.
  • Cookies. Clear cookies for the .local domain and try a private window.

If you cannot reach the dashboard, rename the plugins folder in Local's site files to disable all plugins at once. Our guide on deactivating plugins without admin access shows the method.

What else can break Local SSL?

Renamed sites, port conflicts, outdated Local versions and security software can all stop SSL from working, so update Local and recheck each one.

A few less common causes:

  • Renamed domain. Changing a site's domain in Local creates a new certificate. Trust it again.
  • Port 443 in use. Another app using port 443, such as a different local server, can block Local's router.
  • Old Local version. Update Local, as fixes for certificate handling arrive in newer releases.
  • VPN or antivirus. Some tools intercept https traffic and replace certificates.

The Local community forum has threads for many of these cases. Search for your exact error message, such as ERR_CERT_INVALID.

Do you need SSL on a local site at all?

You do not strictly need SSL locally, but using it makes your local site match production, which helps you catch mixed content and https-only features early.

Many browser features, such as service workers and some payment widgets, only run on secure origins. Testing them on http gives misleading results.

Matching production also avoids surprises when you push the site live. If the live site uses https, the local copy should too.

Once SSL is working locally, read our guide to setting up a local WordPress development environment for tips on syncing local and live sites.

Frequently asked questions

Why does my Local site say Not secure?

Local signs each site's certificate itself, and browsers distrust self-signed certificates by default. Click Trust next to SSL on the site's Overview tab, approve the system prompt and restart your browser. The warning should disappear on the next visit.

Why does Local SSL work in Chrome but not Firefox?

Firefox keeps its own certificate store instead of using the operating system's list. Either set Firefox to use system certificates or add an exception for your site from the warning page. Chrome and Edge read the system store, so they work once you click Trust.

Can I use SSL in Local's localhost router mode?

SSL is designed around the Site Domains router mode, where each site gets its own .local domain. If you switched to localhost mode, change it back in Local's advanced preferences, restart your sites and trust the certificate again.

Do I need to change WordPress URLs after enabling SSL in Local?

Yes. Set both the WordPress Address and Site Address to https in General Settings, then run a search and replace on old http links. Without this step, pages may load over http or show mixed content warnings.

Is it safe to bypass the certificate warning on a local site?

For a site on your own computer, accepting the warning is low risk because traffic never leaves your machine. Still, trusting the certificate properly is better, since bypasses can hide real problems such as mixed content that would appear on the live site.

Sources

  1. SSL in Local Local
  2. Managing a Local site's SSL certificate in macOS Local
  3. Setting up certificate authorities in Firefox Mozilla Support
  4. wp search-replace WordPress Developer Resources
  5. Mixed content MDN Web Docs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.