beeing blocked by Cloudflare

[bit-refresher]

sorry for taking this way - I wasn't able to find another way to get in contact (https://letscontrolit.com doesn't provide an impressum?).

Since two days, any attempt to visit https://letscontrolit.com leads to "Sorry, you have been blocked ..." delivered by Cloudflare. Seems that my public ip adress is blocked - I'm not having any idea about the reason. As I should "include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page." I can tell that I did absolutely nothing than trying to visit https://letscontrolit.com respectively subpages.
Some Cloudflare Ray IDs according to this issue: 9df2b3f049418f33, 9df2e4386ff7243e. 9df2b7b09d91c518 & 9df2b6c70b19dc59.

It would appreciate to get information about the reason and I would love beeing able to visit https://letscontrolit.com.

tnx in advance

[tonhuisman]

Please read about our on-going struggles with scrapers and bots in #5398

[bit-refresher]

@tonhuisman: tnx for your immediate response and for the linked thread. By knowing the background, it's easy to understand that defensive measures are necessary.

Assuming that I'm a 'regular user' the remaining question is "how can I get access to https://letscontrolit.com/ again" without using my cellular phone. The public ip address of my wired network is quasi-static.

[TD-er]

Can you give the (IPv4) subnet you're coming from?
I don't need the exact IP, just the subnet.

In Cloudflare there are several layers of blocking. Some are using their "AI botnet detection" (or however it is called)
And those I added manually are based on the AS-number of a subnet.
This is like the 'owner' of the subnet.
When I know your subnet, I can look for the AS-num and remove it from the block list.

[bit-refresher]

Thank you very much for your assistance and thank you very very much for ESPEasy! My ipaddress is in range 178.27.x.y. If you prefer one level deeper (x), please let me know.

…

Gesendet: Freitag, den 20.03.2026 um 10:24 Uhr Von: TD-er ***@***.***> An: letscontrolit/ESPEasy ***@***.***> Cc: bit-refresher ***@***.***>, Author ***@***.***> Betreff: Re: [letscontrolit/ESPEasy] beeing blocked by Cloudflare (Issue #5517) TD-er left a comment (letscontrolit/ESPEasy#5517) Can you give the subnet you're coming from? I don't need the exact IP, just the subnet. In Cloudflare there are several layers of blocking. Some are using their "AI botnet detection" (or however it is called) And those I added manually are based on the AS-number of a subnet. This is like the 'owner' of the subnet. When I know your subnet, I can look for the AS-num and remove it from the block list. -- Reply to this email directly or view it on GitHub: #5517 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[TD-er]

That's enough, it is AS31334
Only problem right now... Apparently Cloudflare itself is under attack, as I can't login to the backend right now.
The login page will not load.

[TD-er]

Hmm I was now able to login at CF, however that network number is not in the block list.
Could it be you're now at a different IP subnet compared to when you got blocked?

[bit-refresher]

My ip address didn'd change; another attempt to visit your server is still followed by

Sorry, you have been blocked
...
Cloudflare Ray ID: 9df70a6aa9df9a2a • Your IP: 178.27.x.y • Performance & security by Cloudflare

[TD-er]

Can you try again?
Problem is that Cloudflare used a different AS-num
I was able to find the block reason using your Ray ID.

[bit-refresher]

It works - thank you very much, good job!

[TD-er]

Great!
Now let's hope there won't be AI bots swarming in again from your subnet. (not your IP, but others from that subnet)