Bottom line: Can anyone suggest what I need to do to help CloudFlare not mis-identify my system as being in China?
[Some URLs edited to allow me, as a new user, to post with the 2-url limit]
I have several (tunneled via Hurricane Electric) IPv6 blocks, but it appears that CloudFlare thinks the GeoLoc for my primary proxy (physically on the US East coast) is in China and is returning a verification page that I cannot even read (and sometimes doesn’t even include the Captcha that I can enter to bypass the bad GeoLoc).
From a quick test I can see that both connect to the same V6 CF IP, but get different results for an otherwise identical request:
The site used is just an example from a recent search result, I have been seeing this consistently on many sites that use CF (the URL used is HTTPS to the HOST www.curtainandbathoutlet.com in the variable substitutions below):
% curl -vsi ${URL}
- Trying 2606:4700:20::6819:196e:443…
- TCP_NODELAY set
- Connected to ${HOST} (2606:4700:20::6819:196e) port 443 (#0)
[…]GET / HTTP/2
Host: ${HOST}
user-agent: curl/7.67.0
accept: /
- Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 403
HTTP/2 403
[…]
Whereas an identical request from a different system in a different IPv6 block gives a correct-looking response with the same server IP:
% curl -iv -6 ${URL}
- Trying 2606:4700:20::6819:196e…
- TCP_NODELAY set
- Connected to ${HOST} (2606:4700:20::6819:196e) port 443 (#0)
[…]GET / HTTP/2
Host: ${HOST}
User-Agent: curl/7.64.1
Accept: /
- Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 200
HTTP/2 200
[…]
Can anyone suggest what I need to do to help CloudFlare not mis-identify my system as being in China?
Thanks,
Philip