My IP is blocked: too many failed logins (how to unblock)

Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Still not working?

The server blocks addresses that keep failing to sign in or that attack websites. Blocks are temporary and lift themselves, but an administrator can remove one at once. Often the "attacker" is an old phone or app with a wrong saved password in your own office.

Symptoms

  • The login page says "Too many failed login attempts. Your IP is temporarily blocked."
  • From your network (and only from it), the website, the panel, webmail or SSH do not open at all — the browser waits and times out. From mobile data everything works.
  • Your mail app suddenly cannot connect, after someone changed a mailbox password.

Causes

There are four kinds of block:

BlockTriggered byDefault length
Panel login block5 failed logins to the panels or the API in 15 minutes15 minutes
Mail, SSH and FTP ban6 failed sign-ins in 10 minutes to SSH, email (IMAP, POP3, SMTP) or FTP1 hour
Protection ShieldPassword guessing on websites (WordPress, Joomla…) or attacks by the web application firewall60 minutes, 24 hours when it repeats within a day
Firewall ruleAn administrator blocked the address or rangeAs set

A panel login block is also applied at the firewall for every service, unless the administrator turned that off. That is why the website stops loading too.

Fix

Find your address

Search for "what is my IP" from the blocked network, or (administrators) see Your IP: on the Firewall page.

If you are a customer

  1. Wait until the block expires (see the table).
  2. Before trying again, correct the saved password on every phone, computer and mail app that uses it.
  3. If it is urgent, contact your hosting provider with your address; they can lift the block.

If you are the administrator

Sign in from another network (mobile data) if your own address is blocked, then:

  • Brute Force Protection (section Security) → Blocked IPs → Unblock. This also removes the matching firewall block.
  • Protection Shield (section Security) → Addresses blocked now → Unblock.
  • Firewall (section Security) → Brute force bans lists bans for SSH, outgoing mail (SMTP auth) and IMAP / POP3. Click the × (Unban) next to the address.
  • Firewall → Rules → Remove for a block rule.

An FTP ban is not listed on that page. From the server's console (as root), any of these bans can be lifted with fail2ban:

fail2ban-client set sshd unbanip 203.0.113.10
fail2ban-client set dovecot unbanip 203.0.113.10
fail2ban-client set postfix-sasl unbanip 203.0.113.10
fail2ban-client set pure-ftpd unbanip 203.0.113.10

If you cannot reach the server at all, use your server provider's web console, or wait 15 minutes.

Prevent it

  • Add your office address to Firewall → Allow or block an IP → Always allow (never blocked at the firewall by the panel or the Protection Shield), and to Whitelisted IPs (comma separated) on Brute Force Protection (never blocked at the login page).
  • Anyone who signed in to the panel in the last day is never blocked by the Protection Shield.
  • Billing systems: add the billing server's address to the allow list; wrong API tokens count as failed logins.

Still not working?

If no list shows your address but you still cannot connect, the problem is elsewhere: run Site Check (customers) or check Service Manager (administrators), and see Control panel does not open.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.