#PROBLEM WITH FIREFOX NOT RESPONDING WINDOWS#

Go to about:networking#dns to check if the DNS record is cached.ДЇWIW, we delegate the DNS resolution to OS. In about:config to 0 or small enough numbers Network.dnsCacheExpiration and network.dnsCacheExpirationGracePeriod Is you URL bar changed after your ISP brings you to the search page? If no, you may try a hard refresh. Shift-refresh will re-do the DNS, bypass the cache. So basically Firefox is sending out a request which doesn't cause a connection error and looks totally successful to it and it's just wrong because it asked the 'pre-VPN' nameserver instead of the 'post-VPN' nameserver.

I really think this issue is something about which nameserver is being queried first. I am attaching a log (log5) with one request before I connected and one after. Unfortunately the private browsing window behaves the same. So it looks like a successful connection but it's really a failure to get to the true destination website. When I type a non-existing URL into my browser (when the hostname doesn't exist) my ISP sends me to it's own 'search page'. (In reply to Tim Murphy from comment #42) Therefore, the server side will have more information to debug, instead of randomly guessing the cookie setting.

#PROBLEM WITH FIREFOX NOT RESPONDING WINDOWS#

To close all processes, you simply have to open Windows Task Manager within your PC. In order to fix it, you have to close all processes related to Firefox. The good sample is a 302, forwarding to another page. Firefox Is Already Running But Is Not Responding Sometimes, this error comes up during the issue of Firefox not opening. The failure sample is a non-keepalive 200, which kinda indicates 'reject to connect' The only difference from request header is Cookie, and we get different result from server is text/html, possible with some script, which cannot be examined at our side.Д¬ompared to the success sample in Comment 35. Now I believe it's not a network/cache issue.

However, both connections did there job well, send all their data to child.ДЇor the second connection, we got 19:16:38.104299 UTC - : D/nsHttp HttpChannelChild::Cancel Try to reconnect again, connection goes to cache, and it's not working for some weird reason. We prune all the dead connections (included we just connect which should not regard as dead). Maybe we're already under VPN before the first connect, but event goes later. It confuses me why the first connection is good to connect. If Firefox will load pages normally, then narrow.

Safe Mode disables all hardware acceleration, extensions as well as changes the theme to the Firefox default. Safe Mode is a good spot to kick off troubleshooting Firefox Not Loading Pages issue because it helps extremely narrow down the causes. However, per comment 31, we can only access the site under VPN. Solution 1: Start Troubleshooting in Safe Mode. This channel went to get resource from cache. 19:16:38.039335 UTC - : D/nsHttp Creating nsHttpChannel This channel succeeded to get resource from network

Problem with firefox not responding