Blocked IP Addresses
The Blocked IP addresses page lists the IP addresses that Weissr has blocked automatically after repeated failed sign-in attempts, and lets you release any of them. It is managed in Administration → Security → Blocked IP addresses and applies to the whole environment. This guide is for administrators who are responsible for access to their Weissr environment.
Before you start
You need the following in place:
The Administrator global permission, which grants access to the Administration page.
IP blocking activated for your environment. It is switched off unless someone turns it on, and doing so is a server-side change, so contact Weissr support if you are unsure whether it is active.
Users who sign in with a Weissr username and password. IP blocking does not cover SSO, as explained below.
📌 Note: While IP blocking is switched off, no address is ever blocked and this page stays empty.
How an IP address becomes blocked
Weissr counts failed sign-in attempts per IP address. When the same address reaches the allowed number of failed attempts, that address is blocked and anyone signing in from it is refused, whichever username they use.
The count covers failed attempts from one IP address, not from one user account.
A successful sign-in from that address clears the count back to zero.
While an address is blocked, the sign-in page shows the message Too many wrong attempts.
Blocking applies to signing in with a Weissr username and password. It does not stop traffic from reaching Weissr in any other way.
📌 Note: You cannot block an address yourself. The page has no way to add, import or edit an address, because every entry is placed there by Weissr in response to failed sign-ins. If you need to refuse traffic from an address permanently, that belongs in your own network or firewall rules.
If your users sign in through SSO
IP blocking does not apply to single sign-on. When a user signs in through an identity provider such as Entra ID, they enter their password in your identity provider rather than in Weissr. Weissr never sees the failed attempt, so it cannot count it and no address is ever blocked here.
For an environment where everyone signs in through SSO, this page stays empty permanently. That is expected.
📌 Note: Protection against repeated failed sign-ins for SSO users belongs in your identity provider. In Entra ID this is handled by its own sign-in protection, such as smart lockout and conditional access policies. Configure it there, with the team that owns your identity provider.
This page is still worth watching in a mixed environment, where some accounts sign in through SSO and others use a Weissr username and password. It covers the second group only.
👉 Learn more about SSO configuration
What the page shows
The page is a list of the addresses blocked right now.
Column | What it shows |
|---|---|
Blocked IP Address | The IP address that is currently blocked. |
Unblock | A button that releases the address on that row. |
An empty list means no address is blocked at the moment.
💡 Tip: The list is loaded when you open the page and does not update by itself. Reload the page to see the current state.
Unblocking an IP address
Unblock an address when you recognise it as a colleague who has simply mistyped a password, and you do not want to make them wait.
Go to Administration → Security → Blocked IP addresses.
Find the address in the list.
Click Unblock on that row.
The address is released at once and disappears from the list. There is no confirmation step, so check the row before you click.
📌 Note: Unblocking sets the failed-attempt count for that address back to zero. It does not exempt the address in future. If the failed attempts continue, the same address is blocked again.
When a block ends on its own
You do not have to unblock every address by hand. A block also ends when either of these happens:
The blocking period passes. Each address is released automatically a set time after its last failed attempt, so an address that stops being used stops being blocked.
The Weissr server restarts. Blocks are held in memory, so a restart or an upgrade clears the whole list.
Blocked addresses and locked user accounts
Weissr has two separate protections against repeated failed sign-ins, and they produce different messages on the sign-in page.
What is blocked | Message the user sees | Where you manage it |
|---|---|---|
The IP address | Too many wrong attempts | This page |
The user account | We cannot log you in now. Try again later or click Forgot password? to reset it | Nowhere. The account releases itself after a waiting period, or when the user signs in successfully after it. |
A user who has forgotten their password normally hits the account message, not the address message. Resetting the password through Forgot password? is the quickest route back in.
👉 Learn more about users and user groups
Troubleshooting
Symptom | Likely cause | What to do |
|---|---|---|
The page is always empty | Your users sign in through SSO, so failed attempts happen in your identity provider and never reach Weissr. Alternatively, IP blocking is not activated for your environment | Expected for an SSO environment. Otherwise contact Weissr support to confirm whether IP blocking is active |
The page is empty, even though a user reported being refused | The block has already ended, either because the blocking period passed or because the server restarted since | No action needed. If users are still being refused, note the time and contact Weissr support |
A user reports Too many wrong attempts but the address is not in the list | Someone unblocked it, the blocking period has since passed, or the user is behind a different address than you expect | Ask the user to try again. If it recurs, note the time and contact Weissr support |
Everyone in the office is refused at once | Your network presents all users to Weissr under one shared address, so one person's failed attempts blocked everyone | Unblock the address to restore access at once, then contact Weissr support to review how addresses reach Weissr |
An address reappears shortly after you unblocked it | The failed sign-in attempts are still going on | Find out who or what is signing in from that address before unblocking again |