- You may be restricted from accessing resources when attempting to read XML or JSON data saved in a local file during project testing or creation.
- Stored data on your Host DNS cache could mean that you try to access resources to old IPs and hence will not be successful.
This article will explore what to do when you get the error – Chrome not allowed to load local resource.
In the early 2010s, the Chrome browser supplanted earlier browsers such as Mozilla Firefox and Internet Explorer as the industry standard, and it currently dominates online browsers.
Google Chrome is quick, simple to use, and has the most extensive addon library of any browser. It is an excellent browser for both business and personal use.
However, as is the case with tech, it comes with its flaws, and users have observed a few errors, including:
- Chrome not syncing – When Chrome does not sync, you are no longer able to share similar data across devices.
- Google Chrome not shutting down correctly – This is an error where the browser, would no longer shut down when you use the close button.
- Chrome ERR_FILE_NOT_FOUND error – Here is an error that is associated with opening new pages or tabs, and is often caused by malfunctioning plugins.
- Google Chrome is running slow – This issue means your browser is lagging. It might also be a general PC problem.
This error is similar to the HTTPS errors in Google Chrome. Let’s get to it.
How do I fix Chrome cannot resolve local resources?
1. Change to Public DNS
- Right-click on the Start menu and click on Settings.
- On the left pane click on Network & Internet, then scroll down and select Advanced network settings on the right pane.
- In the Related settings section, click on More network adapter options.
- Right-click on your adapter and select Properties.
- Select Internet Protocol Version 4 (TCP/IPv4), then click the Properties button.
- Under the section for Preferred DNS server, type 18.104.22.168, and for the Alternate DNS server section, type 22.214.171.124, tick Validate settings upon exit and hit OK.
- Relaunch your browser and try reaccessing the resource.
Updating your network setting’s DNS servers is a simple solution to this problem. For example, you may use any publicly accessible DNS servers on the internet. Lastly, consistently utilize recognized and trusted server addresses when resolving domains for security reasons.
2. Install the Web Server for Chrome extension
- Navigate to the extension page for Web Server for Chrome
- Click on the Add to Chrome button.
- Select the CHOOSE FOLDER button, and select the folder where your project is located.
- Click on the address in the Web Server URL(s) menu to run the file.
3. Clear your DNS host cache
- On your browser, type the address below and hit enter.
- Click the button to Clear host cache.
- Relaunch your browser and try re-accessing the resource.
When you browse the same domain repeatedly, Chrome employs DNS caching to speed up the site’s loading by mapping IP addresses from the cache.
While this error is not exclusive to Chrome, you may try another browser. We love to recommend Opera because it is built on Chromium and has an extensive array of features.
Its UI is also pleasant and it arranges all your most used tools in such a way that they are easily accessible. The browser also offers an extensive repertoire of extensions to enhance customization.
How do I allow local access to Chrome?
- Hit the close button to shut down all open instances of your Chrome browser.
- Open your run dialogue using hotkeys Windows + R.
- Type the text below and hit enter.
You sometimes have to read XML or JSON data saved in a local file during a project’s testing or creation phases of a new site. IIS or even IIS Express, and Visual Studio may be used to execute the test website.
Note that you will have to try a different solution if you are not allowed to load local resource iframe, PHP, HTML, or Jquery.
You should have successfully resolved the error of Chrome not allowed to load local resources. Please note that these solutions are not in any particular order, and you should try whichever seems the easiest to implement.
This isn’t the only resource problem, and many reported Error loading this resource in Chrome message, but that issue can be easily fixed.