[Help] F2-221 IP Blocked and not able to login

[PaulB]

Hi, It has happened to me today.
Tried to login to my F2-221 on browser but got 'unable to login. IP blocked contact your Administrator’!
I am the Administrator!

Search of forum shows old answer (now locked ) is to login from another IP address. That is possible for a temporary fix, but my PC is on a
has an assigned LAN address that others use to access shared files, so I need to revert back to the assigned IP address and access the TNAS web page.

So how do I clear my blocked LAN IP address on the NAS? Presumably this is in a stored file somewhere in the OS. I had SSH access to the CLI so if I can find the file somewhere and remove my LAN address entry I should be able to login again. Can anyone point me to the location please?

Is this affected by remote login attempts from outside my LAN? I have tried unsucessfully to use the remote access to my NAS in the past but not got it working.

I can still access files locally using SMB fine and the server is running OK.

BT Paul

[TMLila]

Hi, It has happened to me today.
Tried to login to my F2-221 on browser but got 'unable to login. IP blocked contact your Administrator’!
I am the Administrator!

Search of forum shows old answer (now locked ) is to login from another IP address. That is possible for a temporary fix, but my PC is on a
has an assigned LAN address that others use to access shared files, so I need to revert back to the assigned IP address and access the TNAS web page.

So how do I clear my blocked LAN IP address on the NAS? Presumably this is in a stored file somewhere in the OS. I had SSH access to the CLI so if I can find the file somewhere and remove my LAN address entry I should be able to login again. Can anyone point me to the location please?

Is this affected by remote login attempts from outside my LAN? I have tried unsucessfully to use the remote access to my NAS in the past but not got it working.

I can still access files locally using SMB fine and the server is running OK.

BT Paul

Hello! Thank you for contacting TerraMaster!
We recommend that you follow these steps:
1、First, connect to the device via SSH and execute the command iptables -F to clear the current firewall rules;
2、Then, switch to using a mobile browser (it is recommended to switch to a mobile data network to ensure the IP address changes) to log in. After a successful login, go to Control Panel > General Settings > Security Settings, and remove the corresponding IP restriction from the "Account Blocking" list.
After completing the above steps, your access permissions should return to normal. If you encounter any other issues, please feel free to contact us at any time.

[deadrazy]

That usually happens after too many failed login attempts and the NAS auto‑blocks the IP. Since you still have SMB and SSH access, you’re in good shape.

On the F2‑221 (TOS), the block list is handled by the security/iptables rules rather than a simple text file you can edit safely. The easiest fix is to SSH in and either restart the firewall service or temporarily disable the IP blocking feature from CLI, then re‑enable it from the web UI later.

Also check if “Account Protection” or similar is enabled in Control Panel → Security once you regain access. Yes, failed remote login attempts can trigger a local IP block if the NAS sees them https://tropical-casino.com/ as coming from your public IP and maps it internally.

If needed, a quick NAS reboot often clears temporary blocks as well.