Panel access by address
Accept panel users only from the IP addresses and networks you trust, without blocking agents, deploy hooks, billing systems or plugins.
Panel access by address lets people use the panel only from the addresses you list, such as your office or VPN. Everyone else sees a page saying the panel does not accept their address, and signing in and the browser terminal are refused too. It is off by default.
Turn it on
Open Security > Authentication and find Panel access by address. It needs settings.manage (owners and admins).
Add your own address first
The card shows Your address, as the panel sees it. Click Add it to put it on the list.
Add the other addresses
Add each IP address or network, with an optional note, for example 203.0.113.7 or 203.0.113.0/24 for an office. IPv4 and IPv6 are both supported, up to 50 entries.
Choose who it applies to
| Scope | Effect |
|---|---|
| Everyone | Staff and hosting customers can only use the panel from these addresses |
| Staff only | Staff can only use the panel from these addresses; hosting customers sign in from anywhere |
Turn it on and save
Tick Only accept these addresses and click Save panel access.
The panel refuses to save a list that leaves out the address of whoever saves it, so you cannot lock yourself out from the page. The change is recorded in the audit log as security.panel_access.
What is never blocked
These have their own credentials and keep working from any address:
- server agents,
- push-to-deploy webhooks,
- billing systems using a billing API key,
- plugins using their own token,
- the panel's own server, over loopback.
A request refused by the list gets IP_NOT_ALLOWED.
Behind a reverse proxy
The panel must see people's real addresses. Behind a reverse proxy or a CDN such as Cloudflare, everyone appears with the proxy's address unless VAULTPANEL_TRUST_PROXY in the panel's .env names the proxy.
Locked out
If your address changed and no allowed address is left to you, turn the list off from the panel's server:
Turn the check off
Add VAULTPANEL_PANEL_ACCESS=off to the panel's .env (/opt/vaultpanel/.env on a panel installed with the installer), then restart the panel:
sudo vaultpanel restartWhile it is set, the card shows that the list is not applied.
Fix the list
Sign in, add your new address under Panel access by address, and save.
Turn the check on again
Remove the VAULTPANEL_PANEL_ACCESS line from .env and restart the panel again.
Sign-in and two-factor
Protect panel accounts with two-factor sign-in and recovery codes, require it by policy, manage signed-in sessions and understand lockout and rate limits.
Audit log
The append-only record of every sign-in, change, denial and operation in VaultPanel, what each entry holds and how to filter it.