Error 522: different results on two PCs in the same network

Website, Application, Performance DNS & Network
1

I’m trying to access https://www.360pano.eu from two PCs on the same network. On one computer IPv6 is configured, on the second only IPv4.

  • PC with IPv6 accesses the site without any problems.
    Tracing route to www.360pano.eu [2606:4700:3031::ac43:8280]: 
4     9 ms    14 ms    11 ms  ae9-720.RT.ELN.TLL.EE.retn.net [2a02:2d8:0:b003:232a::]
5    43 ms    44 ms    38 ms  RT.LIM.WAW.PL.retn.net [2a02:2d8::57f5:e0a7]
6    51 ms    28 ms    32 ms  2400:cb00:73:2:9002::2 
7    35 ms    40 ms    35 ms  2606:4700:3031::ac43:8280
  • PC with IPv4 gives error 522.
    Tracing route to www.360pano.eu [172.67.130.128]: 
4     6 ms    13 ms     7 ms  ae9-720.RT.ELN.TLL.EE.retn.net [87.245.242.82]
5    38 ms    32 ms    39 ms  ae6-4.RT.NTL.KIV.UA.retn.net [87.245.233.143]
6    35 ms    33 ms    32 ms  GW-CloudFlare.retn.net [87.245.247.169]
7    31 ms    31 ms    31 ms  172.67.130.128

If I disable Cloudflare the site opens without problems.

image
image835×623 24.7 KB

2

I’m not able to reproduce the error. However, here’s the guide to fix:

3

You cannot reproduce, but I see what I see: on a computer with IPv6 the site opens, but with IPv4 still not

image
image818×622 23.8 KB

And if you look at the trace routes I provided, it goes to different CF nodes.

4

And the advice that you gave is incorrect in this case, since the site opens on the second computer.

5

No, I think the 522 instructions pretty much cover it. It’s an issue connecting to the origin. Not every visit will route through the same IP address, which you already pointed out. An origin server or network hardware can treat those requests differently.

If you’re on a paid plan, you can open a ticket. Support may be able to track down the actual error coming from the origin.

1 Like
6

I asked hosting administrators if there were any changes in the settings recently and received the answer that nothing had changed. The site is working now. Looks like it was a problem on the Cloudflare side.

Tracing route to www.360pano.eu [104.21.3.84]

4    34 ms    21 ms     6 ms  ae9-720.RT.ELN.TLL.EE.retn.net [87.245.242.82]
5    33 ms    38 ms    31 ms  ae6-4.RT.NTL.KIV.UA.retn.net [87.245.233.143]
6    49 ms    32 ms    46 ms  GW-CloudFlare.retn.net [87.245.247.169]
7    32 ms    31 ms    31 ms  104.21.3.84