#Site took too long to respond chrome download
I then connected to the wireless ISP and did the same test, and I got speeds of 2.52 download and 1.15 upload.Īll this is on the same computer, using the same browser, no reboots or anything, just connecting to different systems. I thought it must be to do with speeds, so I did a speed test on the sim card, and it gave me really slow speeds of 1.06 download and. So I disconnected the adsl and connected to the sim card, and Firefox went straight into the site, no problem, no handshake freeze, nothing. Firefox is my default browser and the website was sent to me as a link, so when it went into firefox I got the TLS handshake ‘freeze’, as I call it. I disconnected the wireless network, and connected to the adsl line, same thing. This morning I needed to get to a website which gave me the ‘this site can’t be reached’ error. On the adsl line, sometimes it works, and sometimes it doesn’t. When I looked it up, everything said it was to do with my profile being corrupted, and I should create a new one, which I did. Firefox gives me that TLS handshake thing where it stays on that forever. My ISP is mystified, or incompetent, but they can’t solve it. In the past couple of months, some sites give me ‘this site can’t be reached’ error when I’m using the wireless connection. a wireless connection to my ISP, also only 2mb. I live in the middle of nowhere, and have three options for connecting to the internet:ģ. Now You: Did you experience the issue in Chrome? If things went well, the page should load now. Step 5: Close the overlay, and reload the page if it threw an error on connect previously. The list of allowed cookies should be empty in the end. This removes all cookies set by that particular domain. Step 4: Select all sites one after the other, and hit the remove button each time. This opens an overlay on the page listing all allowed and blocked cookies. Step 3: Click on the link underneath Cookies that displays the number of cookies from that site. Step 2: Click on the little icon in front of the Microsoft web address.Ĭhrome displays the number of cookies set by the site. Step 1: Go to the Microsoft website, or a page the error is thrown on. You may want to do the following instead: While you could go ahead and clear all cookies, something that you do by using the shortcut Ctrl-Shift-Del, making sure "Cookies and other site and plugin data" and "the beginning of time" under Obliterate the following items are selected, it is overkill as you will delete all cookies not just the ones set on Microsoft sites. Paul Thurott mentioned the issue on Twitter, and a solution was found eventually that seems to resolve the issue for most users.Īpparently, it is a cookie issue that is prevent Chrome from connecting to select Microsoft's sites and web pages. It appears however that many users are affected by the issue.