I can't connect to one website in FF but can in IE. Had the problem on my XP machine and fixed it, but the fix does not work on my Win8 machine.
I had connected to Rackspace.com on both my XP and Win8 machines. Then about 1 week ago, I started to get connection timed out messages. Initially I thought it could be the site was down so waited a few days and tried again with the same result. I then used IE and was able to connect on both machines so it wasn't the web site. I went in to FF support and cleared my history, not just cookies and cache - everything with a time range of everything (that's what happens when one misreads the instruction) - no change. I even tried it a second time selecting only cookies and cache this time. I then went to "Firefox can't load websites but other browsers can". I first tried the network connection settings in the advanced tab. On my XP machine I set the option from "use system proxy settings" to "auto-detect proxy settings for this network" and it worked. Yeah! Thinking I had solved the problem I went to the Win8 machine and made the same change - didn't work. I then set it to "no proxy" - no joy. I then went out to see what the IE proxy settings were - IE had no proxy settings so the "no proxy" option in FF should have worked. Since it didn't I went and added FF to my trusted applications in my anti-virus. I removed it from my firewall and added it back - no change. I ran a Malware check with MalwareBytes - none detected. MalwareBytes is set to be active all the time and updates automatically. It has not alerted me of detecting malware or blocking malicious websites (when FF does not catch them). I added FF to the list of excluded domains in the anti-Malware just to be sure - no luck. I have had no messages from FF about blocking known malicious websites. I checked the "Troubleshoot FireFox issues caused by malware" and have not experienced any of those issues. I tried disabliing iPv6 and DNS Prefetching - nada.
Valgt løsning
It seems that whatever was happening, has stopped. A very weird experience.
Thanks everyone for the suggestions and input. I learned some new things as a result so it was worthwhile even though the problem wasn't identified.
Læs dette svar i sammenhæng 👍 0Alle svar (12)
Ok. Now I can't access Rackspace.com on my XP machine. During the time since I corrected the problem FF updated from ver 43.0.3 (43.0.8?) to ver 44 and the message changed from connection timed out to "unable to connect". I can still access Rackspace.com on IE on the Win8 machine, but not the XP machine. This is frustrating.
Seems to be working here.
What security software do you have?
Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) to see if that helps in case your security software is blocking the website.
Just an observation The site rackspace.com is pretty slow to load for me taking about 4 seconds with cache but about 18 without, and that is on a Windows 7 . I will try it shortly on a slower XP & post again if using XP is a problem for me.
I was asked what security program I am running. I have the two machines set up differently. Because of that, I don't think it is my security programs. I did boot up into safe mode with no change in outcome.
XP machine: Kaspersky Internet security which has a firewall and antivirus. It does not do well with malware even though it it says it does so I use Malwarebytes for malware protection.
Win8 machine: Windows firewall, Bitdefender AV, Malwarebytes.
Ok, this is strange. Rackspace started to not load on IE, but when I had IE run a connection diagnostic it came back with no problems and then loaded Rackspace. If I then closed IE and immediately start FF, Rackspace would load. This was true on both machines, but closing FF and restarting it ends up with connection timing out. So now the more interesting thing which reflects your observation that Rackspace takes a lot of time to load. I have multiple tabs open when FF starts and Rackspace was in the middle. I noticed that FF starts loading with the first tab and moves down the line. When I moved the tab for Rackspace, it loads with no problems. All tabs indicate they are loading from startup, but since the tabs are given priority sequentially by the time it gets to the Rackspace tab a few seconds have passed before it gets priority. Couple that with the long load time for Rackspace it times out before completing connection.
But prior to a week ago, Rackspace loaded just fine in the middle. Also if all the other tabs are loaded and I open a new tab and try to load Rackspace it will still time out even though it has priority, which also stopped a week ago.
Just ran a test by closing the Rackspace tab, opening a new tab, moving the new tab to the first position and then trying to connect to Rackspace and it timed out. So problem is not completely fixed. Next I will close FF then restart to see if it loads on startup.
Right now Rackspace is now seems to be loading on the Win8 machine without having to open IE first. I can shut down FF and start it again and Rackspace loads. I have not tried shutting down the tab opening a new one to see if it still loads, so hold on a second while I try. Now it is not loading on startup.
Since this is inconsistent (at least tonight) I think some of this could be due to my internet connection possibly on the slow side. But before tonight it was quite consistent in not loading Rackspace any longer. So that would indicate there is some interaction between some as yet unidentified issue an my internet connection.
Due to issues with my previous internet provider, I currently do not have DSL and am using a wireless AT&T wifi device. That could be a problem, but when I first got the device, my connection speeds were faster than with my previous provider, however that could have changed. Currently there are no high speed direct providers in my area outside of my previous provider.
I am going to shut down FF and restart to see if Rackspace loads again on startup.
This is weird.
The inconsistency continues. I am now back to if I can load Rackspace on IE, I can then open it in FF. I had a couple of instances where it did not load in IE and would also not load in FF. That would seem to point to some kind of internet connection problem, Rackspace server problem, or some kind of settings issue, or a combination of them.
So I am going to try FF mobile using the same internet device.
My older (2-3 yrs) Samsung Note 8 tablet, android device would not load Rackspace after about 10 seconds, but loaded Amazon in less than 1 second, weather.com in about 2 seconds and national weather service in about 2 seconds.
My newer Samsung note 5 phone loaded Rackspace in about 2 seconds.
The more I look, the more it seems the problem may be related to my machine speed in combination with the internet connection and Rackspace server. Phone is faster than Win8 machine which is faster than the XP machine which is faster than the Samsung tablet. This seems to be borne out with phone loading in 2 seconds or less, the Win8 machine loading a little less consistently (but I can get it to load fairly often), the XP machine loading with great difficulty, and the tablet doesn't load at all.
Any ideas on how to address this possibility?
John99 said
Just an observation The site rackspace.com is pretty slow to load for me taking about 4 seconds with cache but about 18 without, and that is on a Windows 7 . I will try it shortly on a slower XP & post again if using XP is a problem for me.
It did load on XP but not immediately on the first attempt. Also I am outside the USA and it offers me a UK version of the site but I declined.
Note if you use keyboard shortcut
Ctrl + Shift + Q
The network tool will open. That has a Timings tab With the network console open you will be able to watch the progress of the website loading. You may well need to use the Reload Icon {On the end of the Address Bar} Red squares are a failure, Green circles success, and Orange triangles are sucessfull cache use.
It may help if you try to follow and reply to Cor-el's question, but it may just be a slow site or slow connection.
cor-el said
Seems to be working here. What security software do you have? Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) to see if that helps in case your security software is blocking the website.
Starting off. I did perform Cor-El's suggestions and booting into safe mode did not make any difference, Rackspace still did not load. I also provided the security programs I use on each of the machines.
So your suggestion. I did ctrl + shift +Q and got to the network tool. At first I did not see a timing tab. I loaded the Amazon website to see what would happen and had clicked on one of the lines and the sidebar with the timing tab opened up. I have attached screen shots of the results of my attempt to load Rackspace.com. Rackspace 1 is an attempt with iPv6 and DNS Prefetch enabled. Rackspace 2 is an attempt with iPv6 and DNS Prefetch disabled.
It's not XP.
I am running 38.6.0 ESR (extended support release) and the site loaded instantly. I'm running XP Professional.
Hello to all
any luck with Google Public DNS 8.8.8.8 and 8.8.4.4( for IPv4) OR 2001:4860:4860::8888 and 2001:4860:4860::8844 (forIPv6)
thank you
Stephen Fox said
It's not XP. I am running 38.6.0 ESR (extended support release) and the site loaded instantly. I'm running XP Professional.
I agree mainly due to the fact that I am having the same problem with my Win8 machine. This is a puzzling problem because it is inconsistent. Sometimes it loads, but most of the time it doesn't. Ten days ago I did not have this problem and the website loaded very quickly, It is possible that a FF update triggered this problem except for the fact that IE will time out sometimes just not as frequently. IE implies there is a connection problem and offers to troubleshoot the problem, but when I do have it troubleshoot the problem it cannot find any issues. So it seems to me that the problem is in my internet connection or the company's server or more likely there is a problem with the newest FF version and the company's server.
Valgt løsning
It seems that whatever was happening, has stopped. A very weird experience.
Thanks everyone for the suggestions and input. I learned some new things as a result so it was worthwhile even though the problem wasn't identified.