At the end of June, beginning of July 2025, we're switching the web servers of the shared hosting environment from Apache to Litespeed. This switch makes websites considerably faster. Especially the heavier WordPress websites will notice this difference, both on the public website and in the WordPress admin area.
Litespeed claims that the transition runs without any issues, but in practice Litespeed turns out to handle certain settings slightly less smoothly than Apache did on a few points. Below you can read which points you should check.
.htaccess
In the root directory of most websites there is a file called .htaccess. This is where you set general settings at website level. Apache simply ignored a number of these rules, but Litespeed is more sensitive to this.
Take a look at the example below:
AddHandler application/x-httpd-ea-php70 .php .php7 .phtml
This rule never had any effect and was always redundant. Unfortunately, Litespeed can't handle this well and shows an error message if this rule is in your .htaccess file. You can either remove the entire rule, or put a # in front of it. This turns it into a comment and the server will ignore the rule.
A similar example that you should also remove or comment out with a #:
<IfModule mime_module>
AddHandler application/x-httpd-ea-php74 .php .php7 .phtml
</IfModule>
The easiest way to edit the .htaccess file is with the File Manager in the DirectAdmin control panel. This article explains where to find the File Manager:
Where can I find the File Manager in DirectAdmin?
mod_security
Do you use page builders in WordPress, such as Elementor, Divi or Beaver? Then error messages may suddenly appear. This is most likely caused by the mod_security module in Litespeed. Apache also had this module, but it was apparently less strict.
The error messages in the web server log file will tell you exactly which rule(s) are causing the error(s). Based on this, you can disable the relevant rules in mod_security. Do you keep your WordPress installation well maintained, do you have the latest version installed and do you install security updates right away? Then you might consider disabling mod_security entirely.
You can find the mod_security settings in the DirectAdmin control panel. This article explains exactly where: