Troubleshooting
Local WP Site Not Loading: Causes and How to Fix It

Short answer
A Local WP site usually fails to load because the site is stopped, the Local router cannot start, another app holds port 80, antivirus blocks the hosts file, or WordPress itself throws an error. Restart the site, try localhost router mode, then check ports, proxies and the debug log.
Key takeaways
- Restart the site, then Local, then your computer.
- Switch router mode to localhost to test routing problems.
- Free port 80 from other stacks like XAMPP or IIS.
- Antivirus and VPNs can block the hosts file.
- Use the debug log for white screens and critical errors.
Why is your Local WP site not loading?
A Local site usually fails to load because the site is not started, the router or hosts file is broken, another app is using the same ports, or a plugin error inside WordPress stops the page.
Local (from WP Engine) runs WordPress on your own computer with its own web server, PHP and database. When you click Open site, your browser asks a small router inside Local to send the request to the right site.
If any link in that chain breaks, you see errors such as:
- This site can't be reached
- ERR_CONNECTION_REFUSED or ERR_NAME_NOT_RESOLVED
- A blank white page or a critical error
- An endless loading spinner
- The wrong site, or a page that redirects to a live domain
Start with the simple checks below, then move to router, port and WordPress fixes.
Is the site actually running?
Check that the site shows as running in Local, because a stopped site, or one stuck while starting, cannot serve any pages.
In the Local app, each site in the left list has a status dot. Select the site and look at the top of the screen.
Try this first:
- Click Stop site, wait a few seconds, then click Start site
- Watch for an error message in the Local window
- Quit Local fully and reopen it
- Restart your computer if Local stays stuck on starting
A full restart clears stuck PHP or MySQL processes that keep ports busy. It fixes more Local problems than you might expect.
If a site will not start at all, open the Local log file. Local's help menu has an option to reveal it. Errors there usually name the service that failed, such as nginx, Apache, PHP or MySQL.
Is the Local router causing the problem?
The router maps site domains like mysite.local to the right site, so if it fails to start or the router mode is wrong, browsers cannot find any site.
Local has two router modes, which you can change in Preferences > Advanced:
| Router mode | Address format | When it helps |
|---|---|---|
| Site domains | mysite.local | Normal use, nicer URLs |
| localhost | localhost:10005 (a port per site) | When the hosts file or port 80 is blocked |
Local explains both in its router mode help article.
If you see a warning that the router is having trouble starting, switch to localhost mode, then try Open site again. If the site loads, the problem is with port 80 or the hosts file, covered below.
Switching modes changes the URL WordPress expects. Local updates this for you, but if you moved a database in by hand, the site and home URLs may still point to the old address.
Is another app using port 80 or 443?
Local's site domains mode needs ports 80 and 443, so another web server, VPN or app that holds those ports stops Local from routing traffic.
Common culprits:
- Another local stack such as XAMPP, MAMP, WAMP or Docker
- IIS or the World Wide Web Publishing Service on Windows
- Skype or other older chat apps on Windows
- The built-in Apache on some macOS setups
- Antivirus web shields that intercept local traffic
To find what is using port 80:
- On Windows, run netstat -ano | findstr :80 in Command Prompt, then match the PID in Task Manager
- On macOS, run sudo lsof -i :80 in Terminal
Stop the other app, then restart Local. If you need both tools, run Local in localhost mode so it uses its own ports.
Has the hosts file been changed or blocked?
In site domains mode, Local adds lines to your computer's hosts file, so a locked, reset or edited hosts file makes .local names fail to resolve.
The hosts file lives here:
- Windows: C:\Windows\System32\drivers\etc\hosts
- macOS and Linux: /etc/hosts
Open it with admin rights and look for lines with your site name ending in .local. If they are missing, Local could not write to the file.
Security software is the usual cause. Many antivirus tools lock the hosts file to stop malware. Allow Local in your antivirus settings, or temporarily disable hosts file protection, then restart Local.
A VPN or a custom DNS app can also bypass the hosts file. Turn the VPN off and test again.
Is your browser or proxy getting in the way?
Browsers can force .local names to https, cache old redirects, or send traffic through a proxy, so test in a private window and turn off proxies and VPNs.
Try these quick checks:
- Open the site in a private or incognito window
- Try a different browser
- Type the full address with http or https as Local shows it
- Turn off any VPN, ad blocker or proxy extension
- Clear the browser cache for that site
An error such as ERR_TUNNEL_CONNECTION_FAILED often means a proxy is set in your system or browser. Add .local and localhost to the proxy bypass list.
If you enabled SSL in Local and the browser warns about the certificate, trust it from the SSL section in Local. Our guide on Local WP SSL not working covers certificate problems.
Does the site load but show an error?
If the browser reaches the site but shows a white screen, a critical error or a database error, the problem is inside WordPress, not Local's networking.
Turn on debugging to see the actual error. In Local, click Open site folder, then edit app/public/wp-config.php and set WP_DEBUG to true with logging on. The WordPress debugging documentation explains each constant.
Common causes inside WordPress:
- A plugin or theme that is not compatible with the PHP version
- A memory limit that is too low
- A database that did not import correctly
- Site URLs that still point to the live domain
To rule out plugins, rename the wp-content/plugins folder, then reload. If the site loads, rename it back and disable plugins one at a time.
Once you can reach wp-admin again, the Health Check and Troubleshooting plugin lets you test plugins one by one without editing folders. Our guide on how to fix the white screen of death walks through the full process.
For database errors, see how to fix error establishing a database connection.
Does the site redirect to your live domain?
A site imported from a live server can still hold the live URL in the database, so WordPress redirects every request away from your local address.
This happens after manual imports or when a search and replace was skipped. To check:
- In Local, open the Database tab and launch Adminer
- Open the wp_options table
- Look at the siteurl and home rows
- Change both to the address Local shows for the site
A full search and replace is safer than editing two rows, since URLs also live in posts and settings. Local's WP-CLI tool can do this. Click Open site shell and run a search-replace from the live URL to the local URL.
Also check for hard-coded redirects in .htaccess, a caching plugin or a security plugin that forces the live domain.
Is the PHP version or web server the issue?
Some sites need a specific PHP version or web server, so switching PHP or between nginx and Apache in Local can make a broken site load again.
Local lets you change the PHP version and web server per site on the Overview tab. If the live site runs PHP 8.2, match that locally.
Very old plugins may fail on new PHP. Very new plugins may need a recent PHP. Our guide on which PHP version to use for WordPress explains the tradeoffs.
If a site uses custom .htaccess rules, it may only work on Apache. Switching to nginx in that case can cause 404 errors or loops.
Should you update or reinstall Local?
Yes, if nothing else works, update Local to the latest version, and as a last resort export your sites and reinstall the app.
Old Local versions can break after operating system updates, especially major macOS releases. Our guide on how to update Local WP covers the safe way to upgrade.
Before a reinstall:
- Export each important site from the right-click menu in Local
- Keep the exported zip files somewhere safe
- Uninstall Local and remove leftover app data if Local's docs say to
- Install the current version and import your sites
How do you find the cause quickly?
Work from the outside in: confirm the site is running, test localhost router mode, check ports and the hosts file, then look inside WordPress.
| Symptom | Most likely cause | First fix |
|---|---|---|
| Site can't be reached | Router or hosts file | Switch to localhost mode |
| Connection refused | Site stopped or port in use | Restart site, free port 80 |
| Tunnel connection failed | Proxy or VPN | Turn off proxy, bypass .local |
| White screen or critical error | Plugin, theme or PHP | Enable debug log |
| Redirects to live site | Old URLs in database | Search and replace URLs |
If you are still stuck, search the Local community forum. Many router and port issues are already answered there with operating system specific steps.
Frequently asked questions
Why does Local say this site can't be reached?
The browser cannot resolve the .local domain or reach the router. Restart the site, then switch router mode to localhost in Preferences > Advanced. If that works, check port 80 conflicts and whether antivirus blocks the hosts file.
How do I change router mode in Local?
Open Local, go to Preferences, then the Advanced tab, and choose between site domains and localhost. Localhost mode gives each site its own port, which avoids hosts file and port 80 problems.
Why does my Local site redirect to the live website?
The database still holds the live URL in the siteurl and home options. Run a search and replace from the live URL to the local URL using WP-CLI in the site shell, then clear any cache.
Can XAMPP and Local run at the same time?
They can clash because both want port 80. Stop XAMPP's Apache before using Local in site domains mode, or run Local in localhost mode so it uses separate ports.
How do I see errors on a Local site?
Open the site folder, edit wp-config.php in app/public, and turn on WP_DEBUG with logging. Reload the page, then read wp-content/debug.log to find the plugin, theme or PHP error behind the failure.
Sources
- What is router mode? Local
- Local community forum Local
- Debugging in WordPress WordPress Developer Resources
- Health Check & Troubleshooting WordPress.org Plugins
- wp search-replace WordPress Developer Resources
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.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


