IP Filter

The IP filter restricts which addresses may sign in. It is the first check of a sign-in: even with the right password, a request from an address not on the list is refused.

One field

Field	Description
Allowed IPs	The permitted addresses, up to 1024 characters

Addresses are separated by a comma, a semicolon or whitespace. Either a single address or a CIDR block may be given:

10.0.0.0/8, 192.168.1.50, 203.0.113.0/24

Leaving it empty turns the filter off

With Allowed IPs empty, every address may sign in. There is deliberately no separate “enabled” switch: emptying the list is how the filter is turned off, so the misleading state of “a full list with the filter off” cannot arise.

You can lock yourself out

Forget to include your own address and you close your own sign-in the moment you save.

The one exemption is loopback: a sign-in from the server itself (localhost) is never blocked. But in most installations that is not the escape hatch it sounds like — when the platform runs behind a reverse proxy the client address is never loopback, it is the real client’s. So if you connect from outside through the proxy, the loopback exemption will not help you; you need local access to the server.

Before changing the list, make sure your own address is in it.

When a change takes effect

The setting is not read from the database on every request but served from a short-lived in-memory copy. A change takes effect within a second.

Why it is cached

This check is the first step of authentication, and behind a reverse proxy it runs on every authenticated request. Measured, it was costing an extra SQL statement and a noticeable delay on each one — overwhelmingly to be told that no filter is configured. The decision itself did not change; only where the row comes from.

Related

• Login Page — the sign-in screen’s appearance
• Auth Log — sign-in attempts