Firewall Connection Issues Guide

If you have too many login failures from the same IP address during a relatively short period of time, you will trigger temporary automatic blocking within the firewall. When this happens, you will not be allowed to connect again for several minutes. This is an important security measure we have in place to prevent certain types of brute force login attacks.

Keep in mind that the auto blocking only affects your remote IP's ability to connect to the server that you had failed logins on. That server is still online, and your site is still online. Auto blocking does not take your site offline. You can check the status of your site with a 3rd party tool like Down For Everyone Or Just Me to make sure your site is still online.

If you cannot connect to your site and a 3rd party tool confirms your site is still online, you can contact us and ask us for help unblocking your IP address. You will need to let us know which server and site you are trying to access, and you will need to let us know what your remote IP is so we can remove it from the firewall. You can use What Is My IP to find your IP address. Please include all of this information in the email you send to support, and we will be happy to manually remove your IP address from the firewall temporary blocking list.

Avoiding Firewall Blocking

To avoid accidentally triggering the auto blocking, it is best to copy/paste your login details or to use the one-click login feature in the NSLH Admin section instead of trying to type your login details each time. If you do mistype your login details, don't do it over and over in rapid succession, because that will trigger the auto blocking.

If you triggered the firewall blocking while using FTP, it is possible your FTP client tried to open too many concurrent connections. We have seen some FTP clients try to open hundreds of simultaneous connections, which looks like a small denial of service attack to the firewall. Make sure your FTP client software limits of the number of connections to some reasonable number. For example, 5 concurrent connections from one FTP client is probably plenty of connections, but hundreds or thousands of connections per FTP client is definitely excessive and can trigger the firewall to block.