⚑
LiteSpeed

LiteSpeed Access Control: Blocking and Allowing IPs

πŸ“… 10 October 2026 ✏️ 10 October 2026 ⏱ 5 min leestijd

Learn how to use LiteSpeed access control to block or allow IP addresses via Plesk, .htaccess and server-level settings for better security.

LiteSpeed access control is the functionality that determines which IP addresses do or do not get access to your website. This is useful for keeping out malicious visitors, bots or countries, or for allowing management only from specific IPs. This article shows how to configure this via Plesk, .htaccess and at server level, and what you need to know about the differences between these methods.

What is LiteSpeed access control

LiteSpeed Web Server has a built-in access control layer that is separate from the regular firewall. This means that requests from blocked IP addresses are already rejected before they reach the actual website or application. This saves server load, as the request is denied immediately without PHP or the database being invoked.

Access control can be configured at multiple levels: globally for the entire server, per virtual host (website), or per directory. You can work with an allow list (only approved IPs are allowed in) or a deny list (specific IPs are blocked while the rest retain access).

Visitor IPLiteSpeedaccess controlAllowedBlocked

Blocking IPs via Plesk

If you use Plesk, setting up access control is usually easiest through the panel itself, without having to edit configuration files. Plesk automatically translates your settings into the correct LiteSpeed configuration.

1

Open your domain in Plesk

Log in to Plesk and go to the overview of your websites. Click on the domain for which you want to restrict access.

2

Go to IP Address Banning or Apache & nginx Settings

Look in the menu for the access management option. Depending on your Plesk version, this is called ‘IP Address Banning’ or the option is located under the web server settings.

3

Add the IP address

Enter the IP address or IP range you want to block or allow. You can also use CIDR notation here for entire network ranges.

4

Save the changes

Plesk applies the configuration immediately. A restart of the web server is usually not necessary.

If you manage multiple websites, this is also a good time to check whether your web hosting package offers enough space and resources for extra security rules and growing traffic.

Access control via .htaccess

If you don’t have Plesk access or want to configure this per directory, you can also do it directly in an .htaccess file. LiteSpeed supports the classic Apache syntax, which makes it easy if you’re already familiar with Apache.

An example to block a specific IP address while the rest retain access:

Require all granted
Require not ip 203.0.113.5

If you want to give access to only one IP address, for example for a staging environment:

Require ip 203.0.113.5

Place these rules in the .htaccess file of the folder you want to secure. Note: changes in .htaccess take effect immediately, but an incorrect rule can make the folder (or entire site) unreachable. Always test first from a different IP address or device.

πŸ’‘ Tip: Before making changes, always make a copy of the original .htaccess file, so you can quickly restore it if something goes wrong.

Common applications

In practice, access control is used for various purposes. Some common situations:

Shielding management environments: make login or admin pages only accessible from a fixed office IP, so brute-force attempts from outside have no chance.

Blocking malicious IPs: if you repeatedly see suspicious access attempts from the same IP in log files, you can block it immediately before it causes further damage.

Shielding test environments: make a staging or development environment accessible only to the team, so search engines and visitors don’t accidentally index or visit it.

Email-related security: it can also be wise to apply access control for webmail access, especially in combination with a well-configured business email environment with strong authentication.

If you’re unsure whether your settings have been applied correctly, check this in Plesk under the web server logs, or contact your provider’s support channels. At Tandata, you’ll find these settings under the domain settings in Plesk, and you can always reach out via the knowledge base with any questions.

Frequently asked questions

Does access control also work for entire countries?

LiteSpeed itself works at the IP level, not the country level. For country blocking you need a GeoIP module or external service that links IP ranges to countries.

Can I block multiple IPs at once?

Yes, you can specify both individual IP addresses and entire ranges (CIDR notation), both in Plesk and in .htaccess.

Can I lock myself out if I make a mistake?

That can happen, especially with a too strict allow list. Therefore, it’s best to test changes from a second device or network before making them permanent.

Is access control the same as a firewall?

No, access control works at the web server level and filters HTTP requests, while a firewall checks all traffic to the server at the network level.

Do I need to restart the server after a change?

With changes via Plesk, usually not. With manual changes to server configuration files, a reload of LiteSpeed may be necessary.

Conclusion

LiteSpeed access control is a powerful and accessible way to protect your website against unwanted visitors, without depending on heavy security plugins. Via Plesk you can set this up quickly without any coding, and with .htaccess you have fine-grained control per directory. If you’re considering switching to a provider where this kind of security is already well set up by default, check out the options for switching to Tandata.

View web hosting β†’

Was dit artikel nuttig?