Facebook
Twitter- Server operating system version
- Alamalinux 10.2
- Plesk version and microupdate number
- 18.0.7x
Hi
I know plesk say they not support openlitespeed https://support.plesk.com/hc/en-us/...ed-Web-Server-or-LiteSpeed-installed-manually
But, for my needs, I'm working on a free and open-source extension to run OpenLiteSpeed on any Plesk domain, with its limitations, of course (limited .htaccess support).
The extension will be available for download from GitHub once it passes some testing, but I'm not sure if Plesk will have any issues including it in its Plesk extensions due to a conflict with LiteSpeed Enterprise.
There's no way to remove/disable Apache without breaking Plesk and Web Repair. Luckily, I've found a clean way to have OpenLiteSpeed in Plesk, without breaking Plesk, Apache, Nginx, or any domains with special .htaccess rules that aren't supported by OpenLiteSpeed. It's not a replacement solution like LiteSpeed Enterprise, but I think it could develop into something quite stable.
The basic idea is: Do you need OpenLiteSpeed and lsapi/lsphp on a specific website? Then activate it without breaking anything or affecting other websites.
Perhaps in two or three weeks I'll have something ready if anyone wants to try it. It's nowhere near production-ready yet, but my idea isn't to have a commercial module. In fact, it costs me time and money, but it's essential to have the benefits of lsapi/lsphp and lscache on some websites without paying for a full LiteSpeed enterprise and without breaking Plesk in the attempt . Being able to have it on a few domains that I think will support it without affecting the rest will be interesting.
Please excuse my poor English; I've had to translate this a bit, as it's not my native language.
I know plesk say they not support openlitespeed https://support.plesk.com/hc/en-us/...ed-Web-Server-or-LiteSpeed-installed-manually
But, for my needs, I'm working on a free and open-source extension to run OpenLiteSpeed on any Plesk domain, with its limitations, of course (limited .htaccess support).
The extension will be available for download from GitHub once it passes some testing, but I'm not sure if Plesk will have any issues including it in its Plesk extensions due to a conflict with LiteSpeed Enterprise.
There's no way to remove/disable Apache without breaking Plesk and Web Repair. Luckily, I've found a clean way to have OpenLiteSpeed in Plesk, without breaking Plesk, Apache, Nginx, or any domains with special .htaccess rules that aren't supported by OpenLiteSpeed. It's not a replacement solution like LiteSpeed Enterprise, but I think it could develop into something quite stable.
The basic idea is: Do you need OpenLiteSpeed and lsapi/lsphp on a specific website? Then activate it without breaking anything or affecting other websites.
Perhaps in two or three weeks I'll have something ready if anyone wants to try it. It's nowhere near production-ready yet, but my idea isn't to have a commercial module. In fact, it costs me time and money, but it's essential to have the benefits of lsapi/lsphp and lscache on some websites without paying for a full LiteSpeed enterprise and without breaking Plesk in the attempt . Being able to have it on a few domains that I think will support it without affecting the rest will be interesting.
Please excuse my poor English; I've had to translate this a bit, as it's not my native language.
