This site can’t be reached error on accessing my site

So you are using and

I don’t know about these numbers. Can you please where I can get these details?

If you don’t know them then nothing more. Works just fine on my end though…

Which well known bug?

1 Like

In which sense overused? I can’t understand where you are going…

It also works fine at my end when I pause the Cloudflare. Only issue is with when I enable it. That’s why I am looking for resolution.

1 Like

Yeah, but for me it works fine even when Cloudflare is active.

curl -I ""
HTTP/2 200 
date: Sun, 02 Jun 2019 13:21:21 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d932fade11bfa9f726f47fe6db75f88971559481679; expires=Mon, 01-Jun-20 13:21:19 GMT; path=/;; HttpOnly; Secure
x-powered-by: PHP/7.3.2
swift-performance: MISS
set-cookie: PHPSESSID=35a3227b6f81a4623bb7ce22ee530617; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
set-cookie: wp_woocommerce_session_ed89348de48e5b45344a3ad46d52b195=fd74950794ccba81fd0906ababcf68c9%7C%7C1559654481%7C%7C1559650881%7C%7C1c3cf88bbc41f813346e9014bb488238; expires=Tue, 04-Jun-2019 13:21:21 GMT; Max-Age=172800; path=/; secure; HttpOnly
link: <>; rel=""
link: <>; rel=shortlink
x-frame-options: sameorigin
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
strict-transport-security: max-age=31536000
referrer-policy: origin-when-cross-origin
content-security-policy: policy-definition
alt-svc: quic=":443"; ma=2592000; v="35,39,43,44"
x-turbo-charged-by: LiteSpeed
expect-ct: max-age=604800, report-uri=""
server: Cloudflare
cf-ray: 4e09bad30879be55-MXP
1 Like

That is an HTTP error though. If it were DNS the error would be very different. That is the server misbehaving. Would you mind checking which certificate it’s served?

It would be nice if you can take remote session over AnyDesk. That way you can check at your end. I don’t mind sharing the details now.

I can’t and I won’t. What is the result of the previous commands that @domjh told you to run?

1 Like

Server: UnKnown

Non-authoritative answer:

Pinging [] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Alright, this doesn’t make sense, but seems like it’s a DNS hijacking from the Wi-Fi captive portal.

This on the other end it’s the correct IP, but I guess you are blocked from doing ping from the same thing as above.

Can you use you phone as hotspot? Just to try. I think it will solve the issue.

PS: try also nslookup

1 Like

That plugin should have no effect whatsoever on the issue at hand…

1 Like

Here is the output from mobile internet:
Server: UnKnown

Non-authoritative answer:
Addresses: 2606:4700:30::6812:32fe

Pinging [2606:4700:30::6812:33fe] with 32 bytes of data:
Reply from 2606:4700:30::6812:33fe: time=152ms
Reply from 2606:4700:30::6812:33fe: time=201ms
Reply from 2606:4700:30::6812:33fe: time=146ms
Reply from 2606:4700:30::6812:33fe: time=152ms

Ping statistics for 2606:4700:30::6812:33fe:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 146ms, Maximum = 201ms, Average = 162ms

You are absolutely right. Same happened with us. Removing cloudlare fixes the issue right away.
Even if you try to access the site on vpn, it will work.

Its a bug on Cloudflare. Do you host site on aws as well?

And this confirms my theory. Open your website now.

Unfortunately that issue needs to be brought up with the Wi-Fi admin.

Given our tests above it wasn’t. If you have something similar open a thread and we’ll take a look, I suppose it could be something similar to this as well.

1 Like

3 posts were merged into an existing topic: This site cant be reached error

A post was split to a new topic: SSL not working on domain

This topic was automatically closed after 31 days. New replies are no longer allowed.