Composr CMS has a rate limiting feature which can be controlled in config_editor.php .

This file stores IP addresses which have been rate-limited (and when).

Thanks for the information. I think with there being a single IP in there it was more confusing than if there had been several. Actually thought it might be related to the Composr news RSS or something as the file isn't present in the Git Repo for master/.

I am getting a 404 when trying to access config_editor.php. Not seeing it in Admin Menu's if I'm not supposed to access directly. Okay, it's called Installation options in Menu, so that'll be why I couldn't find it. Logged in, and "The cookie domain must either be blank or start with a dot." Pretty sure it's whatever the default is as I haven't changed anything there.

$SITE_INFO['cookie_domain'] = 'mediafeeder.net';
$SITE_INFO['cookie_path'] = '/';

Stuck a dot in there and I can now access the options. Interestingly, rate limiting is not even selected so no idea why it is active.

That is weird. Maybe it was previously active at one point? Or you ran the test suite?

I never use the test suite, never felt the need. Didn't even know rate limiting was a thing. Just noticed the file in data_custom and was curious.

Going to close this for the time being. If you're having any issues with the rate limiter, please let me know. Note that in beta9 the behaviour is changing. Instead of a single rate_limiter.php file, they are now spread across JSON files in a new rate_limiter folder, named by IP address. This will help with I/O because with a single file, multiple requests could be locked out while waiting for the filesystem to finish (as only one I/O operation can be performed on a file at a time). Now with each file being per-IP, there won't be nearly as much lock-out.