On Linux Debian 10 (Buster), I am using the http(s) client google-chrome-stable.
I was configuring (nginx) and testing (chrome) a reverse proxy and it got cached using a wrong domain.
I fixed the configuration but it still resolve to the wrong domain.
I have tried to go chrome://net-internals/#dns and click on Clear host cache but that didn't change anything.
I have tried to go chrome://net-internals/#sockets and click on Flush socket pools but that didn't change anything.
I am not working with FireFox, so FireFox can resolve correctly (so does curl).
After about 10 minutes, without restarting chrome. I did F5 (refresh) and it was loading the proper page. I haven't found a manual way to immediatly clear chrome cache.
I am doing devops and I haven't solved this issue for years.
Would love to know how to do one day :O
What happens if you open developer console F12 and then hold down on the refresh button and then select empty cache and hard reload?
Take a look at this gif for an example.
Related
I wanted to change DNS server on macOS 10.14.6 by going to System Preferences -> Network -> Advanced..., and adding 8.8.8.8 in the DNS tab. Since then, Chrome gives me a
DNS_PROBE_FINISHED_BAD_SECURE_CONFIG error.
First I returned to the previous DNS settings (putting 192.168.1.1 in place of 8.8.8.8). Since then I tried switching my router off/on. I cleared the Chrome DNS cache as explained in this answer. I cleared browsing data (history, cache, cookies) on Chrome. I stopped and restarted the mDNSResponder service.
From the terminal, both ping and curl work fine. Other browsers (Safari) work fine. Why do I see this error, and how do I solve it?
If you have checked all DNS settings but still got this error, you could take a look at the Chrome Secure DNS to see if this setting had switched on.
To turn Chrome Secure DNS on or off:
Open Chrome.
At the top right, tap More and then Settings.
Under “Privacy and security,” tap Security.
Turn Use Secure DNS on or off.
Anytime I have dev tools open on localhost my cookies are deleted and I am redirected to the login page on every page load which means I cannot use dev tools to debug or get insight into my site. I have localhost setup with a valid SSL cert (self-signed) and the site works normally until I open dev tools. How do I fix or disable this new "security" or setting in chrome?
After lots of issues and trying out many different things I came across this post/answer
When adding a Javascript library, Chrome complains about a missing source map, why?
Turns out that when I opened Dev Tools it would request a CSS map and the request was being sent to a different firewall causing my application to require me to re-authenticate every time this resource was requested. Turning off the CSS source map option fixed the issue
I use Xdebug on my development server and debug using PhpStorm in a page loading in Chrome. However, Chrome has the annoying feature to reload a page if it takes too long to load, launching another debug session on the page I'm already debugging.
I tried looking for a solution, this problem is an oldie, but the solutions posted then aren't applicable anymore.
I tried setting the Max. simultaneous connections to 1, but that causes other windows loading on the same dev server to halt completely until I'm done running the first debug session, so that's not an option for me either.
Is there any way to stop Chrome reloading pages when it 'thinks' the server in question is taking too long to answer?
I'm wondering if there is a terminal command that allows me to view my google chrome DNS cache on Mac.
Thanks
I have the same exact problem. Chrome is resolving a URL to the wrong IP, all other browsers resolve to the correct one. Upon inspecting the net-internals menu it just gives me the option to clear cache. There doesn't appear to be any direct way to see it.
What I did instead is I allowed the website to resolve to the wrong IP, then accessed the developer menu (F12 on Windows), clicked on Network, chose one of the loaded images and clicked the 'Headers' tab. under General -> Remote Address it showed me which cloudflare proxy IP the something.com address was resolved.
I have used a method for years that has worked for me and limited any mysterious domain-based issues with cookies and such.
In my /etc/hosts file, I do the following for the local development version of www.mysite.com:
127.0.0.1 localhost local.mysite.com
When I visit http://local.mysite.com:3000, this has done exactly what you'd expect for years and years, and still works in Safari and Firefox. However, Chrome started stubbornly giving me an ERR_CONNECTION_REFUSED message a few months ago, and I can't make it work. If I visit http://localhost:3000, it works fine, but I avoid developing against localhost for various reaions. I have tried every possible thing I can find on the internet (clearing caches etc), and nothing has made the error go away.
Anyone have any idea what can be done here?
In the browser, please clear host cache and then try it out. To clear host cache, follow the steps below
Open up Chrome browser and enter " chrome://net-internals/#dns " in the address bar without quotes
Click on the button Clear host cache
Restart your browser and try again
You need to disable the dns prefetching and network condition predicting services on chrome.
As chrome is trying to look for local.mysite.com in actual dns servers and not finding the local ip address.
You can see the below steps -
Go to chrome://settings
Click on "Show advanced settings..."
Unmark the Predict network actions to improve page load performance
box.
Check if the DNS prefetching is really disabled by going to
chrome://dns.
You should see there something like DNS pre-resolution and TCP
pre-connection is disabled.