Firewall change was rolled back or locked you out
On this page
Every firewall change made in the panel has a safety net: you must confirm it within 90 seconds, or the previous rules come back. That way a mistake can cut you off for a minute and a half at most.
Symptoms
- The Firewall page shows "The last change was not confirmed and was rolled back automatically at …".
- A port you opened, or a rule you added, is in the settings but does not work.
- Right after saving, the panel stopped loading.
Causes
- You did not click Keep these rules in time (most common): you left the page, or the confirmation was missed.
- The change cut off your own connection, so you could not confirm. The rollback then gave you access back.
- Your address is blocked by a rule, the Protection Shield, brute-force protection or a public attacker list.
Fix
You did not confirm
- Open Firewall (section Security) in the admin panel (
https://<server>:2087). - Check the settings and rules: after a rollback the page may not match what is running.
- Click Save & apply again, then Keep these rules in the yellow box. The box counts down the seconds left and the page refreshes by itself.
The change cut you off
Wait 90 seconds: the previous rules come back and the page loads again. Then correct the change. Common mistakes:
- Removing the port you use for SSH when it is not
22. - Turning on port filtering from an address that changes (mobile connections). Add your fixed office address with Always allow first.
Your address is blocked
Sign in from another connection (a phone hotspot) and remove the block. See how to unblock an IP address.
Still not working?
If you cannot reach the server at all and waiting did not help, use your hosting provider's console (the server's screen in the provider's dashboard), log in as root and remove the panel's firewall rules until the next change or restart:
nft delete table inet sahaab
Then sign in to the panel, fix the settings and save them again; saving puts the panel's rules back.
Good to know
- Removing a block never needs confirmation, because it cannot lock anyone out.
- Automatic blocks (brute-force protection, Protection Shield, attacker lists) are applied without the 90-second window.
- Ports 22 and 2087 can never be closed from the panel.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to configure the server firewall and open ports
Turn port filtering on, choose the open TCP and UDP ports, and confirm the change within 90 seconds so you can never lock yourself out of the server.
- How to block or allow an IP address in the firewall
Block an attacker's IP address or range on the whole server, or always allow a trusted address such as a billing server, permanently or for a set time.
- How to unblock an IP address (customer can't connect)
A customer or you cannot reach the server or log in: find which protection blocked the IP address and unblock it in the right place in the admin panel.
- How to restrict the admin panel to your IP addresses
Allow only your own IP addresses or ranges to open the admin panel on port 2087, and how to get back in with one command if you lock yourself out.