From nxinx_apache to OpenLiteSpeed, possible issues?

[sunsunshining]

I am considering switching from nxinx_apache mode to OpenLiteSpeed and I wonder if there is anything I should be aware of.

For example, will .htaccess permalink rules work for Wordpress? Will DocumentRoot setup be maintained if extra rules have been added?

Has anybody tried it with existing sites?

 

[Ohm J]

Becarefully,

Deny from all
Require all denied

will not work anymore, it's use to make the private directory.

 

[sunsunshining]

Where is that code, and what does it affect?

 

[Active8]

We have done it few times for our customers, not big changes some special codes can give problems in htaccess file you must load it now with php.ini.
We had never need for that , but just in case test it

Regarding changes, when you add or edit htaccess file it would not pickup automatically , you have to restart the OLS
However you can create a cron for that as mentioned here :

General | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

 

[Ohm J]

And.... some wordpress plugins that's using "auto_prepend_file" might stop working, like wordfence. Or other cms still using special directive value could go wrong.

 

[sunsunshining]

Thank you, very useful, there seems to be a solution, edits to php.ini can be made via DA panel per specific site or per php version? Is there a specific path for DA OpenLiteSpeed php.ini?

Enable WordFence | PHP | Configuration | OpenLiteSpeed Documentation | OpenLiteSpeed Documentation

Configuring PHP to enable WordFence in OpenLiteSpeed

docs.openlitespeed.org

 

[Active8]

1. edits to php.ini can be made via DA panel per specific site or per php version?

Yes (login with FTP or so and create php.ini)
Yes (if there is an need, just use the file corresponding to your php version with file editor )

Is there a specific path for DA OpenLiteSpeed php.ini?

No

some wordpress plugins that's using "auto_prepend_file" might stop working, like wordfence

Wordfence is working fine with OLS