We have a couple of measures in place to protect against bots, but I suspect that legitimate members are being hit by these measures more often than they should be.
We have a couple of measures in place to protect against bots, but I suspect that legitimate members are being hit by these measures more often than they should be.
I guess it is a firewall, quite normal. I can accept this. It even happened to the Element14 Store site which refused me to shop. I reported to them and later it was improved.
I answered "never" because I *think* I've seen it once, but I'm not even sure if it was here or somewhere else, so the answer tends to never with 99.999% certainty
I had it a few times when I was getting 'Accesss Denied' messages from using Edge on Win 8.1. (BTW although this Edge is 'out of support', Microsoft are still patching it.)
Haven't seen it recently, though I've mainly been looking at the site with Vivaldi on Xubuntu 22.04 LTS (I haven't been using 24.04 LTS because it broke some of the design software I was using and it was simpler to go back to 22.04 for the moment). In recent weeks, I've sometimes been getting Access Denied messages at weekends (worse on Sunday) on Xubuntu, though today is alright so far. Last Sunday was particularly bad. Those only apply to Vivaldi, Firefox on the same machine can still see the site, though when the system is like that, your annoying gatekeeper (Mr Google) turns up and demands that I do some AI training in return for access, which I now refuse to do. Presumably something falls over and needs a little manual intervention to get going again. Doesn't matter at all - I don't need to be logged in for anything other than actual blog creation, and that can always wait for a day or two.
I got that page few minutes ago. After turning off the cloudflare warp application, after that the homepage loaded fine.
Hi,
Just for future reference, I was able to identify the root cause of the “Oops!” behaviour I reported earlier with the help of the maintenance team.
In my case, it was triggered while editing a RoadTest draft that contained a large number of image references pointing to non-existent paths (coming from externally generated HTML). This resulted in multiple 404 responses in a short time, which in turn activated the platform’s protection mechanisms and temporarily blocked my access.
After their explanation, the behaviour makes sense from a backend/protection perspective, so it’s not really a failure but more a side effect of how the system handles repeated errors.
I’ve adjusted my workflow accordingly (uploading images individually instead of referencing them externally), and the issue is no longer occurring.
Hope this helps add some context in case others run into something similar.
Thanks!