Mark Sealey
Level 2 (362 points)
Desktops

Q: Only for Google links: Safari Can't Open the Page

Safari Can't Open the Page "https:/www.gogle.com/url?xyz" because the server where this page is located isn't responding.

 

Of course the page is perfectly reachable; and always appears when I dismiss this error and reload.

 

This disappeared for a while, but now is back :-(

 

Only in Safari, only when clicking on links which are the result of Google searches.

 

GoogleError.jpg

 

Anyone any ideas, please?

 

TIA…

iMac with Retina 5K display, OS X Yosemite (10.10.5), Clean machine... no haxies; no Microsoft etc

Posted on Oct 29, 2015 4:06 PM

Close
Mark Sealey

Q: Only for Google links: Safari Can't Open the Page

  • All replies
  • Helpful answers

first Previous Page 3 of 6 last Next

  • by Mark Sealey,

    Mark Sealey Mark Sealey Nov 7, 2015 12:38 PM in response to Risco
    Level 2 (362 points)
    Desktops
    Nov 7, 2015 12:38 PM in response to Risco

    Risco - thanks!

     

    I suppose it's possible that Safari handles responses from Google servers differently from the way in which FireFox and Chrome do.

     

    And/or that Google works differently with different browsers.

     

    I suppose it could be that certain ISPs - at least three major ones acting (presumably independently?) on two continents (although I'm a  British expat in California!) - are independently either throttling or failing with only Google domains.

     

    But the more people who report this, the more my instinct tells me that it must be something specific about the way in which some software handles specific URLs like, 'https://www.google.com/url?…' followed by a lengthy series of (properly-formed? and properly-escaped?) parameters.

     

    I feel as though I should re-open my case. I'll gladly do Capture_data again. But I'll feel short-changed if the result that it's a network issue comes back.

     

    Perhaps this could help?

  • by Jonathan Payne1,

    Jonathan Payne1 Jonathan Payne1 Nov 7, 2015 3:02 PM in response to Risco
    Level 1 (44 points)
    Mac OS X
    Nov 7, 2015 3:02 PM in response to Risco

    Here's some new information.

     

    I created a second account on my computer and logged into it at the same time.

     

    Whenever a link fails on my account, I switch users to the other account and try the same link. So far it's worked immediately every time.

     

    When I switched back to my account, however, it also worked whereas usually it takes a little longer than that to fail. So I am not sure what this means yet but will keep experimenting.

     

    Things that make me go Hmmmm ....

  • by Risco,

    Risco Risco Nov 7, 2015 3:04 PM in response to Jonathan Payne1
    Level 1 (5 points)
    Nov 7, 2015 3:04 PM in response to Jonathan Payne1

    That is very interesting Jonathan. I am going to try this too, it HAS to be a software issue.

  • by Mark Sealey,

    Mark Sealey Mark Sealey Nov 7, 2015 3:26 PM in response to Risco
    Level 2 (362 points)
    Desktops
    Nov 7, 2015 3:26 PM in response to Risco

    Thanks, Jonathan and Risco

     

    I always find that reloading the page which has just failed serves it immediately. Every time.

     

    Would you say, Jonathan, that what you're now experiencing could really be considered the equivalent of that: after all, you're sending a second request to the Google domain servers to send you the page?

     

    (I've filed a bug report with Apple now.)

  • by Jonathan Payne1,

    Jonathan Payne1 Jonathan Payne1 Nov 7, 2015 3:53 PM in response to Mark Sealey
    Level 1 (44 points)
    Mac OS X
    Nov 7, 2015 3:53 PM in response to Mark Sealey

    Hi Mark,


    Reloading does not work for me. I can reload 10 times and nothing happens. I can click the external link 10 times and it opens 10 Safari windows and they all hang.

     

    However, so far, as soon as I switch to the OTHER user, it works immediately, and then when I come back to my own window, it also works immediately. I have a feeling there is some shared url cache in Mac OS X which is getting hung up for some reason. Actually, even that makes no sense, because why would switching to another user have impact on the original user unless it was a shared cache, in which case, why wouldn't the other user hang as well?

     

    Very confusing.

     

    My next test will be to switch to the other user but NOT open the link there. And then switch back. And see if the act of switching users is solving the problem.

     

    After that I will switch to my second user and click on a different link and see if that works or not. And if that impacts the original link on my user.

     

    And I just want to remind you that this only happens to me with t.co links, which is twitter's URL shortener.

     

    Strange stuff but the more information the better, in/when Apple takes a look at this.


    JP

  • by Jonathan Payne1,

    Jonathan Payne1 Jonathan Payne1 Nov 7, 2015 4:09 PM in response to Jonathan Payne1
    Level 1 (44 points)
    Mac OS X
    Nov 7, 2015 4:09 PM in response to Jonathan Payne1

    Weird to reply to my own message, but here's what I am going to try next:

     

    The next time my safari hangs, I am going to kill the process(es) called: nsurlstoraged using Activity Monitor.

     

    There appears to be one for each logged in user and one other one.

     

    I am going to see if killing the process owned by me fixes things.

     

    I am going to bed now otherwise I'd do it now ;-)

  • by Mark Sealey,

    Mark Sealey Mark Sealey Nov 7, 2015 10:28 PM in response to Jonathan Payne1
    Level 2 (362 points)
    Desktops
    Nov 7, 2015 10:28 PM in response to Jonathan Payne1

    Please do let us know how it goes, Jonathan; thanks!

     

    You're trying tests which - in theory - ought to reveal more than anyone else posting here has.

     

    If the Apple engineers are right that Google is actually responding to the http request but the machine is not responding to the response (they say b/c of the network - even though only for Google domains on Safari), will your nsurlstoraged procedure reveal that?

  • by Risco,

    Risco Risco Nov 8, 2015 2:35 AM in response to Jonathan Payne1
    Level 1 (5 points)
    Nov 8, 2015 2:35 AM in response to Jonathan Payne1

    OK just woke up the Macbook after sleeping overnight. Tried google and nothing happened, would not load at all. So I had made another account as mentioned by Jonathan and tried the same search and it worked fine. Went straight back in to my main account and it would not load. Flipped back and it loaded.

     

    So, something is happening after installation that is causing this problem. Again, this can only be a software issue.

  • by Mark Sealey,

    Mark Sealey Mark Sealey Nov 8, 2015 9:55 AM in response to Risco
    Level 2 (362 points)
    Desktops
    Nov 8, 2015 9:55 AM in response to Risco

    Hoping to help with the wider troubleshooting, may I just point out, please, that this all began for me when I got my new hardware in March, and was on Yosemite. I've kept the hardware (of course) and upgraded directly to 10.11.1.

     

    It doesn't seem related to version or OS-installation - at least to me.

  • by pejotl,

    pejotl pejotl Nov 8, 2015 1:52 PM in response to Risco
    Level 1 (0 points)
    iOS Apps
    Nov 8, 2015 1:52 PM in response to Risco

    I am in Poland and have the same problems.

     

    Regarding OS version, it started with upgrade to El Captain (in Yosemite lags happened only sometimes).

  • by Mark Sealey,

    Mark Sealey Mark Sealey Nov 8, 2015 2:34 PM in response to pejotl
    Level 2 (362 points)
    Desktops
    Nov 8, 2015 2:34 PM in response to pejotl

    Thanks; please also report it to Apple, pejotl.

  • by Risco,

    Risco Risco Nov 15, 2015 8:13 AM in response to Mark Sealey
    Level 1 (5 points)
    Nov 15, 2015 8:13 AM in response to Mark Sealey

    Anyone heard back from Apple yet?

  • by Mark Sealey,

    Mark Sealey Mark Sealey Nov 15, 2015 9:42 AM in response to Risco
    Level 2 (362 points)
    Desktops
    Nov 15, 2015 9:42 AM in response to Risco

    Risco,

     

    They closed my bug report as a duplicate with the note that it was acknowledged, reproducible and would be fixed soon.

     

    Others using 10.11.2 beta have found that TM backs up as intended regularly in that new environment.

     

    I'd say it was only a matter of… ahem, TIME :-)

  • by Jonathan Payne1,

    Jonathan Payne1 Jonathan Payne1 Nov 15, 2015 1:18 PM in response to Mark Sealey
    Level 1 (44 points)
    Mac OS X
    Nov 15, 2015 1:18 PM in response to Mark Sealey

    Um - Mark? Were you confused between this report and another one? This is the https URL issue, not some Time Machine issue.

     

    Meanwhile, to answer the original query, I have heard back from Apple in terms of asking me for more input on the issue. I even uploaded a video so they could see it failing in action.

     

    I hope to hear back from them ...

  • by Mark Sealey,

    Mark Sealey Mark Sealey Nov 15, 2015 1:32 PM in response to Jonathan Payne1
    Level 2 (362 points)
    Desktops
    Nov 15, 2015 1:32 PM in response to Jonathan Payne1

    Jonathan,

     

    Yes I was; you're right. My apologies. Wishful thinking, perhaps. As you were… :-)

first Previous Page 3 of 6 last Next