# Issue with Local WP Version 8.1.0+6514: Chrome displaying '404 Page Not Found' Error"

**URL:** <https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427>\
**Category:** Support\
**Created:** [December 14, 2023, 3:13pm UTC](https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427 "2023-12-14T15:13:02Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![RichardReed](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/richardreed/32/20362_2.png) [@RichardReed](https://community.localwp.com/u/RichardReed)\
**Post date:** [December 14, 2023, 3:13pm UTC](https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427/1 "2023-12-14T15:13:02Z")

</div>

I have been using the Local WP for a few weeks without any problems. However, last night, I encountered an issue when trying to access my local sites in Google Chrome. Instead of my websites, I received a “404 Oops… page not found” error message with the text “powered by SCE CDN engine v2.66 - [cachezone.net](http://cachezone.net).” Interestingly, everything worked perfectly fine in Safari. This issue seems to be exclusive to Chrome (Version 120.0.6099.109, Official Build, arm64).

I attempted various troubleshooting steps, including rebooting my system, clearing the cache, and more, but none of these actions resolved the issue. The only thing that temporarily worked was resetting Chrome to its default settings. However, this solution was short-lived, as the error reappeared this morning. It almost seems as if Chrome is running some kind of CDN server on my machine.

I am running this setup on macOS Sonma 14.2 (23C64) with Local WP Version 8.1.0+6514. Has anyone else experienced this issue, and does anyone have a solution for resolving it?

Thanks very much!  
Richard

 ![CleanShot 2023-12-14 at 10.03.00@2x](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/7/e/7e62911370d5ae33ccb5aaf631557cb3547d9c4e.png)  
 ![CleanShot 2023-12-14 at 10.03.14@2x](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/8/e/8e2103c6494a87609a9a84e03711a476ced027f8.png)

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [December 14, 2023, 8:50pm UTC](https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427/2 "2023-12-14T20:50:52Z")

</div>

Hi @RichardReed

When you open up your Dev Console in Chrome does it show an further errors or messaging?

I also noticed the Chrome URL shows that it’s Not Secure. If you add `HTTPS` to the URL like [https://localwp.com/](https://localwp.com/) does it load?

---

<div class="post-metadata">

**Author:** ![RichardReed](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/richardreed/32/20362_2.png) [@RichardReed](https://community.localwp.com/u/RichardReed)\
**Post date:** [December 14, 2023, 9:24pm UTC](https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427/3 "2023-12-14T21:24:15Z")

</div>

I’ve pinpointed the source of the problem: it turns out to be the VPN.AC Chrome extension. When the VPN is activated, it causes this issue.

When the “Not Secure” warning appears, it happens exclusively for local WordPress pages, even though they use HTTPS. I’m uncertain if this is a standard behavior for Local WordPress. There are no issues when using a web hosting server. Should I see this message?

I also attempted to enable SSL trust in the application, but encountered an error message stating, “Heads-up! There was a problem with trusting the local SSL certificate.” The exact nature of the issue is unclear.

Richard

 ![CleanShot 2023-12-14 at 16.25.46@2x](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/e/6/e6638c1386b6310a9f24d83f9b3645ddff7f582f.png)  
 ![CleanShot 2023-12-14 at 16.25.12@2x](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/4/4/44af093af040b761e15d465218bbbeddf14290fd.png)

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [December 15, 2023, 2:36pm UTC](https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427/4 "2023-12-15T14:36:50Z")

</div>

We have some documentation below that can help with troubleshooting SSL issues in Local. Sometimes it can be browser or extension specific and other times something in the machine.

> **[SSL in Local](https://localwp.com/help-docs/getting-started/ssl-in-local/)**
>
> This doc will go over SSL basics, using SSL in Local, and some common issues. If you are experiencing issues and are also using macOS check out this doc. Table of Contents: Secure Sockets Layer (SSL)…

> **[SSL Certificate on macOS](https://localwp.com/help-docs/getting-started/managing-local-sites-ssl-certificate-in-macos/)**
>
> In most cases, Local makes getting your offline development environment running HTTPS easy by providing a one-click solution for trusting a site’s SSL certificate. Occasionally, if that “trust”…

---

<div class="post-metadata">

**Author:** ![seltzdesign](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/seltzdesign/32/20399_2.png) [@seltzdesign](https://community.localwp.com/u/seltzdesign)\
**Post date:** [December 19, 2023, 11:47pm UTC](https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427/5 "2023-12-19T23:47:54Z")

</div>

I have the same issue (possibly). The local site was running fine a week ago, but now I get a 404 error on posts. It’s also working fine online of course.

I am on the latest version of Local (8.2) on Windows 11. I have local SSL enabled.

> [@Nick-B](#):
>
> When you open up your Dev Console in Chrome does it show an further errors or messaging?

For me there are no errors shown in Console.

After restarting Local I am getting this error:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/f/d/fdc75b7963a4af42409c7c25d73c35701619db35.png)

(Before it was starting the site, but gave 404 errors)

It’s so strange, Local had been running so reliably for many months.

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [December 20, 2023, 2:00pm UTC](https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427/6 "2023-12-20T14:00:11Z")

</div>

Hi @seltzdesign

If you create a new, blank site in Local can you access that okay? If you can, then you may want to try reimporting the site getting the errors. The steps would look like this:

- Locate the site files on your machine, and save a copy of them to your desktop. If you click `Go to Site Folder` under your site name it should take you right to where they are located.
- Once you have those copied, completely delete the site from Local
- Restart Local/your machine
- Reimport the site back into Local. You can refer here on how to [Restore from only Local site files](https://localwp.com/help-docs/getting-started/how-to-import-a-wordpress-site-into-local/#restore-local-site-from-site-files)

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [March 19, 2024, 2:00pm UTC](https://community.localwp.com/t/issue-with-local-wp-version-8-1-0-6514-chrome-displaying-404-page-not-found-error/40427/7 "2024-03-19T14:00:24Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
