What the message looks like
Too many requests
There were too many requests from your network. Retry later or contact your administrator if this is an error.Common causes
- Several wrong passwords from the same address, for example a sync client or a phone with an old password.
- A reverse proxy or Cloudflare hides the real addresses, so every user shares one IP (see
trusted_proxies). - Many users sit behind one office address (NAT).
- A script or app polls with wrong credentials.
- An attack really is running against the login.
Check
- What does the log say about the address?
grep -i bruteforce /var/www/nextcloud/data/nextcloud.log | tail -n 10 - Does Nextcloud see the real client address? Check the trusted proxies
- What does the web server log show for failed logins?
grep 'POST /login' /var/log/nginx/access.log | tail -n 20
Fix
- Reset the address:
sudo -u www-data php occ security:bruteforce:reset 203.0.113.5. - Fix the proxy setup so Nextcloud sees real addresses, see reverse proxy header.
- Whitelist a trusted network such as the office:
sudo -u www-data php occ config:app:set bruteForce whitelist_0 --value=192.0.2.0/24. - Find the client with the old password (sync client, phone, script) and update it, preferably with an app password.
- Keep the protection on. Do not switch it off just to silence the message.
Typical scenario
In an office of 25 people behind one shared public IP, a colleague's old phone keeps syncing with an expired password. Soon the login page shows "Too many requests" for everyone. nextcloud.log contains "Bruteforce attempt from … detected for action login" with the same address each time. Search there for the user name and the userAgent to find the client that keeps failing.
FAQ
How long does the block last?
The delay grows with the number of failed attempts and fades after a while without new ones. Resetting the address removes it at once.
Why does it hit everyone at once?
If the proxy's address is what Nextcloud sees, all users count as one visitor and share the delay.
Can I simply switch off the brute-force protection?
Technically yes, with 'auth.bruteforce.protection.enabled' => false in config.php. That only makes sense as a short test, because you lose protection against password guessing. It is better to whitelist trusted networks and fix the failing client.
How do I find the device that keeps failing?
nextcloud.log records user name, address and userAgent for every failed login. That tells you whether it is a desktop client, mobile app or script. Then remove the device in the user's security settings or update the stored password there.
Does the message come from Nextcloud or from my nginx rate limit?
Look at who answers. Nextcloud's throttling returns the message as a Nextcloud page and leaves an entry in nextcloud.log. An nginx limit_req shows up in the nginx log instead and answers with 503 by default unless you changed limit_req_status.