Real visitors get "Too Many Requests"
They share an address that went over a limit together with another signal, or the site is in Elevated or Under attack mode. Check the address on the dashboard: the signals show why. If the site is behind a proxy or CDN, turn on Behind a proxy, or everyone shares the proxy's address. Raise the limit for that kind of page, or allowlist your institution's network.
I banned myself
Bans apply to admin pages too. From another network, or with an address on the allowlist, lift the ban under the address's page. Or delete the ban from the database: UPDATE omeka_tg_bans SET unbanned_at = UTC_TIMESTAMP() WHERE ip_address = 'YOUR_ADDRESS'; (with your table prefix). Private network addresses are never banned when Always allow private networks is on.
Nothing shows on the dashboard
Only slowed-down and blocked requests are logged unless Log allowed requests is on. Requests from private networks are not checked at all when Always allow private networks is on: test from a public address, or turn it off for a moment.
Every request seems to come from one address
The site is behind a proxy or CDN. Turn on Behind a proxy, and make sure the proxy sets X-Forwarded-For.
A crawler I want is slowed down
Add an allow rule for its user agent (for example Googlebot) under Rules and allowlist.
MCP clients are slowed down
MCP Server requests have their own limit (240 a minute in Normal mode). An assistant working through many records can reach it; raise the MCP limit under Settings, or allowlist the address it connects from.
The site still works when Traffic Guard fails
Any error inside Traffic Guard lets the request through and is written to PHP's error log with [TrafficGuard], so a database problem never takes the site down.