My site does not respond under the main browsers, but still works from under the VPN

My site does not respond under the main browsers, but it still works from under the VPN. It also passes tests of ping and others. No changes were made to the site files or to the mysql database.
I got ERR_CONNECTION_TIMED_OUT
What should I do? How to fix? Can somebody please help me?

I don’t know what’s going on…

Pretty sure there’s a 522 #CommunityTip on that, but the answer is in your hosting providers log files, here are the steps I found:

  • (Most common cause) Cloudflare IP addresses are rate limited or blocked in .htaccess, iptables, or firewalls. Confirm your hosting provider whitelists Cloudflare IP addresses.
  • An overloaded or offline origin web server drops incoming requests.
  • Keepalives are disabled at the origin web server.
  • The origin IP address in your Cloudflare DNS app does not match the IP address currently provisioned to your origin web server by your hosting provider.
  • Packets were dropped at your origin web server.

From https://support.cloudflare.com/hc/en-us/articles/115003011431#522error

Dear sir, [cloonan]!

  • (Most common cause) Cloudflare IP addresses are rate limited or blocked in .htaccess, iptables, or firewalls. Confirm your hosting provider whitelists Cloudflare IP addresses

Сhecked, ip is not in the blacklist

  • An overloaded or offline origin web server drops incoming requests.

Сhecked, origin web server not overloaded

  • Keepalives are disabled at the origin web server.

Сhecked, keepalives not disabled at the origin web server

  • The origin IP address in your Cloudflare DNS app does not match the IP address currently provisioned to your origin web server by your hosting provider.

Сhecked, origin IP address in my Cloudflare DNS application matches the IP address currently provided to my source web server by my hosting provider.

  • Packets were dropped at your origin web server.

Сhecked, packets are not dropped on the origin web server.

UPD. Still have ERR_CONNECTION_TIMED_OUT in browsers without vpn,
in browsers with vpn my site opens successfully

Which operating system are you using?

Can you post the output of these commands?

ping kigurumi-party.ru
nslookup kigurumi-party.ru
ping www.kigurumi-party.ru
nslookup www.kigurumi-party.ru
1 Like

I use windows 10.
ping kigurumi-party.ru
Packet exchange with kigurumi-party.ru [104.24.98.106] with 32 data bytes:
Timed out request.
Timed out request.
Timed out request.
Timed out request.

Ping statistics for 104.24.98.106:
Packets: sent = 4, received = 0, lost = 4
(100% loss)

nslookup kigurumi-party.ru
╤hyЁтЁЁ: UnKnown
Address: fe80 :: 8226: 89ff: fe67: 78ef

Unreliable answer:
╚ь: kigurumi-party.ru
Addresses: 2606: 4700: 30 :: 6818: 626a
2606: 4700: 30 :: 6818: 636a
104.24.98.106
104.24.99.106

ping www.kigurumi-party.ru
Packet exchange with www.kigurumi-party.ru [104.24.98.106] with 32 bytes of data:
Timed out request.
Timed out request.
Timed out request.
Timed out request.

Ping statistics for 104.24.98.106:
Packets: sent = 4, received = 0, lost = 4
(100% loss)

nslookup www.kigurumi-party.ru
╤hyЁтЁЁ: UnKnown
Address: fe80 :: 8226: 89ff: fe67: 78ef

Unreliable answer:
:Ь: www.kigurumi-party.ru
Addresses: 2606: 4700: 30 :: 6818: 636a
2606: 4700: 30 :: 6818: 626a
104.24.99.106
104.24.98.106

Alright, resolution seems to work.

Next step, whats the output of these commands?

powershell (Invoke-WebRequest -Uri 'http://kigurumi-party.ru').Headers
powershell (Invoke-WebRequest -Uri 'https://kigurumi-party.ru').Headers
powershell (Invoke-WebRequest -Uri 'http://www.kigurumi-party.ru').Headers
powershell (Invoke-WebRequest -Uri 'https://www.kigurumi-party.ru').Headers

powershell (Invoke-WebRequest -Uri ‘http://kigurumi-party.ru’).Headers
Invoke-WebRequest : Unable to connect to remote server
line: 1 character: 13

  • (Invoke-WebRequest -Uri ‘http://kigurumi-party.ru’).Headers
  •  + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
    eption
     + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
    
    

powershell (Invoke-WebRequest -Uri ‘https://kigurumi-party.ru’).Headers
Invoke-WebRequest : Unable to connect to remote server
line: 1 character: 13

  • powershell (Invoke-WebRequest -Uri ‘https://kigurumi-party.ru’).Heade …
  •         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
      eption
    • FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

powershell (Invoke-WebRequest -Uri ‘http://www.kigurumi-party.ru’).Headers
Invoke-WebRequest : Unable to connect to remote server
line: 1 character: 13

  • powershell (Invoke-WebRequest -Uri ‘http://www.kigurumi-party.ru’).He …
  •         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
      eption
    • FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

powershell (Invoke-WebRequest -Uri ‘https://www.kigurumi-party.ru’).Headers
Invoke-WebRequest : Unable to connect to remote server
line: 1 character: 13

  • powershell (Invoke-WebRequest -Uri ‘https://www.kigurumi-party.ru’).H …
  •         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
      eption
    • FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Which Windows 10 version are you running? Apparently your version does not support that call.

However I just noticed your pings failed.

Whats the output of these commands?

tracert kigurumi-party.ru
tracert www.kigurumi-party.ru

Which Windows 10 version are you running?
Windows 10 pro ver 1903 assembly 18362.418

tracert kigurumi-party.ru

Tracing the route to kigurumi-party.ru [104.24.98.106]
with a maximum number of jumps of 30:

1 <1 ms <1 ms <1 ms myhome.ru [192.168.1.1]
2 1 ms <1 ms <1 ms ptrtest128.mksbalashihi.ru [95.64.128.1]
3 1 ms 1 ms 1 ms 194.135.70.54
4 3 ms 3 ms 4 ms 195.9.94.202
5 3 ms 3 ms 3 ms 195.9.94.201
6 3 ms 3 ms 3 ms 10.254.242.182
7 4 ms 3 ms 3 ms 94.29.127.190
8 4 ms 4 ms 4 ms 10.109.11.6
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace completed.

tracert www.kigurumi-party.ru

Tracing the route to www.kigurumi-party.ru [104.24.99.106]
with a maximum number of jumps of 30:

1 <1 ms <1 ms <1 ms myhome.ru [192.168.1.1]
2 3 ms 1 ms 2 ms ptrtest128.mksbalashihi.ru [95.64.128.1]
3 2 ms 1 ms 1 ms 194.135.70.54
4 3 ms 2 ms 4 ms 195.9.94.202
5 4 ms 3 ms 3 ms 195.9.94.201
6 4 ms 3 ms 4 ms 10.254.242.182
7 3 ms 3 ms 3 ms 94.29.127.190
8 4 ms 3 ms 4 ms 10.109.11.6
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace completed.

It would appear as if your ISP does not route the request to Cloudflare.

Either there is an issue or they blocked that particular address. The latter is not uncommon in a Russian context. Just use the search here and you will find plenty of threads.

Thank you for your time!
Good time to you!