blocked from cloudflare

hey how do i find out why the ip of my Root server is blocked from cloudflare cant even ping 1.1.1.1

20 Replies

Alf•7mo ago

?waf-block

Flare•7mo ago

If you are blocked by a website that uses Cloudflare, you need to contact the website owner to appeal or investigate the block. Cloudflare is configured by the site owner, and Cloudflare will not overwrite the configuration of any customer. Nobody in this Discord nor any Cloudflare employee will be able to help you. The site owner can investigate why you were blocked through your ray id.

Alf•7mo ago

@Henne ⬆️

HenneOP•7mo ago

Nope 1.1.1.1 doesn’t work so it isn’t waf

Alf•7mo ago

oh you dont get any message?

HenneOP•7mo ago

Nope the server doesn’t reply to the ping

Alf•7mo ago

weird

Chaika•7mo ago

very unlikely to be a block. Only time CF says it'd do a straight up IP blackhole/ip jail is in the case of a really large DDoS Attack (you'd have to be actively attacking them). Otherwise you'd always get a block page or some more info I would try v6 1.1.1.1 addresses, traceroute to see how far it gets, check local net config, etc

HenneOP•7mo ago

I router the trafic via a other ip with Tailscale and it worked

Chaika•7mo ago

that really doesn't say anything, you're going though another network entirely Does it work via the same network over IPv6 to Cloudflare? It's all requests to Cloudflare, on any Cloudflare Network Resource? For example, can't access discord.com, or gitlab.com, or anything If you run a traceroute, how far do you get before the icmp is dropped? etc

HenneOP•7mo ago

traceroute -m 90 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 90 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 shortened because of the exact same result
90  * * *

traceroute -m 90 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 90 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 shortened because of the exact same result
90  * * *

traceroute -m 90 cloudflare.com
traceroute to cloudflare.com (104.16.133.229), 90 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 shortened because of the exact same result
90  * * *

traceroute -m 90 cloudflare.com
traceroute to cloudflare.com (104.16.133.229), 90 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 shortened because of the exact same result
90  * * *

discord.com and gilab.com result in the same as above the server sadly dosnt have an ipv6 address

HenneOP•7mo ago

with My Traceroute for 1.1.1.1

Chaika•7mo ago

That looks like a local issue, perhaps it could just be ICMP being blocked but if it's http as well then most likely related. If it was Cloudflare blocking your traffic entirely you would expect to see the hops all the way from your provider's local network, into transit/ix/etc, and then disappear somewhere after that. If you have nothing at all, that's on your side

HenneOP•7mo ago

resolved my hosing provider uses ddos protection from aurologic.net dont know why it ist kicking in if the server was down for 8 hours+ and i am only trying to ping cloudflare

Chaika•7mo ago

🤔 so it was their ddos prot?

HenneOP•7mo ago

jup

Chaika•7mo ago

who are you using that has aurologic, hostbrr or something? Just curious, it makes sense it was on their end but that's a curious cause

HenneOP•7mo ago

zap-hosting

Chaika•7mo ago

well that's interesting, at least a semi-easy fix I guess

HenneOP•7mo ago

thank you for your help without you i wouldn't have solved the problem

Gaming

Programming

blocked from cloudflare