-
Notifications
You must be signed in to change notification settings - Fork 0
Banlist
Daniel Perna edited this page Feb 20, 2020
·
3 revisions
This section of the webapp provides you with an overview of currently banned IP addresses. IP addresses that show up here and exceed the configured banlimit within the configured ban time will get a 401 response to every request to the webapp. For those clients to regain access you either have to remove the IP address from the banlist, or the client has to wait for the ban time to expire.
At the bottom of the table you'll find a button to purge the whole banlist. If your application is online for a while you will find quite some entries from bots that scrape the web and get rejected. Purge the banlist to de-clutter the database once in a while.
- Clients that don't use the correct hostname in their request (e.g. they browse directly to your servers IP instead of what you have configured as
ORIGIN) - Requests to
/register/none(only after the first user (admin) has been created) - Attempts to register with an invalid token
- Login-attempts with invalid / non-existent usernames
- Login-attempts with invalid passwords
- Neither TOTP nor OTP token provided during login
- Invalid TOTP or OTP token provided during login