Hi, I’m having this weird issue. All of a sudden my website ( gracious-wescoff-35e960) can’t be found on Safari. I get the error message:
“Safari can’t find the server”
In Chrome and Firefox the website shows up.
Does anyone have an idea what could be causing this issue? The website is already hosted some time on Netlify, and all this time it worked just fine in Safari.
Thanks for your help,
Anthony
Hi Anthony,
Hmm, that’s strange. I can get to your site using safari so maybe it’s a cache or weird cookie issue?
Can you try accessing your site using a Private Window in Safari? ( File > New Private Window ). If it loads that way, you may just need to clear your cache and/or cookies.
Thanks,
Seth
I want to echo what seth said - I am seeing it load perfectly in safari on my machine:
it must be something local - let us know if you figure it out!
Hi Guys, thanks for checking into this. I followed Seth’s advice and started a new Private Window in Safari. Now the website is showing up.
It was a client who signalled this issue with Safari to me. I also checked it on my iPhone and also there I get the “Safari cannot find server” error.
Greetings,
Anthony
Hi @acandael.
If a Netlify server is responding then we would ask for you to send us the x-nf-request-id header for the response.
As it would seem that there is no response that won’t be possible. These are the details that header replaces:
In order to troubleshoot, we’ll need as many of those details as possible. As we cannot reproduce the issue, we’ll need you to send us those details as we have no access to them.
Would you please send us a much of that information as you have available?
Hi,
I’m from the Philippines and I face the same issue.
I’ve recently DEPLOYED “https://everra.netlify.app/” and its not working on iPhones (see below):
the complete URL requested
→ https://everra.netlify.app/
the IP address for the system making the request
→ not quite sure. mobile is connected to Philippines ISP (Smart / Globle)
the IP address for the CDN node that responded (or the returned by the DNS lookup)
→ not quite sure how to retrieve this
the day of the request
the time of the request
the timezone the time is in
→ August 08, 2022 10:00 (Philippine Standard Time)
This is weird because it perfectly works on Android Mobile
Please suggest what actions can I take to resolve this issue.
Is it because I’m currently using a free tier hence the limited service to iOS?
Hi,
I face the same issue with iOS which is weird because it woks perfectly with Android (see below)
the complete URL requested
→ https://everra.netlify.app/
the IP address for the system making the request
→ not quite sure. mobile is connected to Philippines ISP (Smart / Globle)
the IP address for the CDN node that responded (or the returned by the DNS lookup)
→ not quite sure how to retrieve this
the day of the request
the time of the request
the timezone the time is in
→ August 08, 2022 10:00 (Philippine Standard Time)
Please advise how can i resolve this issue.
Hi,
I face the same issue with iOS (see below) which is weird because it works perfectly with Android
the complete URL requested
→ https://everra.netlify.app/
the IP address for the system making the request
→ not quite sure. mobile is connected to Philippines ISP (Smart / Globle)
the IP address for the CDN node that responded (or the returned by the DNS lookup)
→ not quite sure how to retrieve this
the day of the request
the time of the request
the timezone the time is in
→ August 08, 2022 10:00 (Philippine Standard Time)
Please advise how to resolve this issue
Hey there, @reuelsicatii 
I think you will find this thread useful, as it is related. https://answers.netlify.com/t/every-netlify-site-i-visit-cant-be-reached-from-the-philippines/49205/44
We believe that this issue is happening at your ISP.
I’m joining the fun. I deployed a site I’m working on. I works fine on Chrome, but doesn’t show up on Safari, even if I try the private window. I’m also traveling and I got the same issue in NY as I do in London.
https://astonishing-haupia-5c892f.netlify.app/
Thanks!
Hi, @mrdcmiller and @reuelsicatii. This is almost certainly your local ISP blocking the sites by blocking the DNS lookups.
Here is how I would test this:
everra.netlify.app)For the DNS debugging tool, you need something that can change resolvers. For example, something like this:
I’m not recommending that app specifically, but it does allow changing the DNS resolver and that is a requirement to debug this.
@mrdcmiller, you don’t sound like you are on mobile and if not, I would just recommend using dig for making these queries:
The only tool I recommend for debugging DNS is dig. If it is available on your platform I always recommend using it instead.
If your ISP’s resolver returns an error and Google’s resolver does not, this then proves the issue is a DNS issue at your ISP. If so, you should contact their technical support to resolve this.
If there are other questions about this, please let us know.
so i’m at a disadvantage, I’ve never used dig but I’m on a mac laptop running OSX, and it’s pre-installed and accessible via terminal. I ran dig https://astonishing-haupia-5c892f.netlify.app/ and I got a response. obviously I’m outside a browser so I’m not sure how to trouble shot browser/ISP issues.
but here’s what terminal returned:
<<>> DiG 9.10.6 <<>> https://astonishing-haupia-5c892f.netlify.app/
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54438
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;https://astonishing-haupia-5c892f.netlify.app/. IN A
;; AUTHORITY SECTION:
. 900 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022082402 1800 900 604800 86400
;; Query time: 22 msec
;; SERVER: fe80::32b1:b5ff:fe78:a125%6#53(fe80::32b1:b5ff:fe78:a125%6)
;; WHEN: Wed Aug 24 22:56:10 BST 2022
;; MSG SIZE rcvd: 150
It mentions ANSWER: 0 which seems odd. I’m not sure if that indicates an ISP issue?
and, I tried the site in Firefox and it worked as expected.
The correct command @mrdcmiller is (with the protocol)
dig astonishing-haupia-5c892f.netlify.app
When I run this I see
% dig astonishing-haupia-5c892f.netlify.app
astonishing-haupia-5c892f.netlify.app. 17 IN A 54.253.175.63
astonishing-haupia-5c892f.netlify.app. 17 IN A 54.206.202.192
ok! without the https:
; <<>> DiG 9.10.6 <<>> astonishing-haupia-5c892f.netlify.app
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51280
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;astonishing-haupia-5c892f.netlify.app. IN A
;; ANSWER SECTION:
astonishing-haupia-5c892f.netlify.app. 20 IN A 18.192.76.182
astonishing-haupia-5c892f.netlify.app. 20 IN A 34.159.75.132
;; Query time: 88 msec
;; SERVER: fe80::32b1:b5ff:fe78:a125%6#53(fe80::32b1:b5ff:fe78:a125%6)
;; WHEN: Wed Aug 24 23:12:46 BST 2022
;; MSG SIZE rcvd: 98
This response seems to be what’s expected?
Does it shed any light on my Safari issues?
So there is no issue with DNS resolution on your computer, or network.
I tried changing the user agent on safari but that didn’t do anything
That has nothing to do with DNS, or not locating of a server. Safari is finding the server, and trying to load the content. The issue, the error, is with your React app code.
This is what I see:
Please start a new thread on for assistance on this @mrdcmiller as it is separate issue to this thread.
