What to do if Imunify360 blocks your access

In another article we cover how Imunify360 works, one of the security systems configured on our servers.

This system analyses various events and may temporarily block an IP when it exceeds certain thresholds. The scope depends on the rule and the service affected; a connection error does not by itself prove that Imunify360 is the cause.

If you see an Imunify360 verification page when you open the domain, complete the challenge from the same IP. When it does not appear, first check your public IP, the service and the exact message before requesting an unblock; the block could come from another layer.

Passing the challenge may remove that web block, but it does not guarantee that every service is unblocked, nor does it fix the cause of the failed attempts. Check the passwords saved in email clients, FTP or applications so they do not cause failures again.

If you need to authorise a legitimate IP, apply a narrow, temporary exception. Do not add broad ranges or keep a whitelist as a substitute for diagnosis.

Tell the type of failure apart

Note down the domain or server, the protocol, the time and the error. A challenge when opening the website, a 403 error from an application and a rejected SMTP connection do not show the same block.

If another connection of your own works, compare the public IPs without repeating attempts from an application with old credentials. The test helps narrow things down, but it does not by itself identify the rule responsible.

Contact support if you cannot complete the challenge or the failure continues. Give us the IP and those details, without passwords. Once it is resolved, repeat the original operation and check whether a device in the background causes the block again.