Search results

I am running a few Wordpress websites with Cyperpanel (v2.0) and OLS (v1.7.5) on an Ubuntu 20.04 server (4GB, 2 vCPUs) at DigitalOcean. There are also a couple of nodeJS apps running on the same server. I just recently set up all the sites. I am the one generating most of the traffic right now...

Just saw LiteSpeed Cache has a TTL for status codes: I guess I can either: 1) Stop using WP Zero Spam (which I am doing for now). 2) Set the 403 TTL to 0 to disable caching. 3) Wait for the WP Zero Spam developer to fix it. It's good to have options.

Hi Steve, I'm guessing I was not clear enough with my description. I'm running OLS with CyperPanel on Ubuntu 20.04. Let's say a malicious host is trying to hammer my home page. WP Zero Spam sends back a 403: status_header( 403 )...

If I keep refreshing my website home page in a browser, I end up getting a 520 error from Cloudflare and I see the message in my server.log file: Is there a way to prevent this from happening?

The WP Zero Spam plugin sends a 403 with some text to block clients. I am observing that OLS is caching the blocked page and serving it to other clients. Is that expected? Does OLS cache pages with 403 status or does it not differentiate?

I figured it out. I got mysqli.inc from a more recent version of phplist and hacked a bit around to deal with old ereg* functions (using this helpful file).

Interestingly, lsphp74 on CentOS7 supports mysql but on Ubuntu, I get the following: My old website uses an outdated and customized version of phplist.

Turns out my old site runs fine with lsphp74 (when I could not get it to work at Cloudways with their PHP 7), so I should be able to move it to my Ubuntu server install.

Thanks for the reply. I am using lsphp74 on newer websites. The old website uses an inherited savant3 based template system that cannot be easily replaced. Is lsphp56 available on CentOS 7?

Is it possible to install lsphp56 on Centos 8? I tried the following: > rpm -ivh http://rpms.litespeedtech.com/centos/litespeed-repo-1.1-1.el8.noarch.rpm > yum install lsphp56 and got this error: Has php 5.6 support been removed from Centos 8?

I am looking for information on LSCache and REST API caching. A lot more plugins have started to use REST API calls, either for the admin interface or the front-end interface. How does LSCache know which ones can be cacheable and which ones should not be cached? If I have an external app doing...

The documentation suggests you can get ESI support with OLS if you also use QUIC.cloud:

Is v1.7.5 not supposed to be available on Ubuntu 20.04 this way? > sudo apt list '*openlitespeed*' Listing... Done openlitespeed-asan/focal 1.7.4-1+focal amd64 openlitespeed-debug/focal 1.7.4-1+focal amd64 openlitespeed-prof/focal 1.7.4-1+focal amd64 openlitespeed/focal,now 1.7.4-1+focal amd64...

I think you will need to give a bit more information to get a solution/resolution to your issue: What operating system are you using? What version of PHP were you using before? If you switch back, do you see the perf problem go away? How did you compile PHP 7.4.8? which extensions did you...

The recommendation is written in the help bubble for "Running As" in OLS webadmin panel. It says at the end: "A user/group of nobody is generally a good choice." >> you mean use template to create multiple vhosts on different users ? Yes >> you can set vhost name as the user name , then...

I have noticed the DigitalOcean OLS image uses www-data:www-data instead of the recommended nobody:nobody (or nobody:nogroup). Could you clarify why there is a discrepancy? I am also wondering if it is possible to run multiple sites using the same virtual host template with different users/groups.

The ordering should also be clarified in the UI. What does 1/2/3 mean? Does 1 have priority? Does 3 have priority? Are context processed in order from low to high, or high to low?

Below is an example Context List. Looking at it, you cannot tell which ones are set as accessible and which ones are set are not accessible. Adding a column reflecting the Accessible setting status would give the web admin a clear view of the current status of the most important aspect of each...

It would be great if the Context List had an 'Accessible' column to see quickly if a particular context has been marked as accessible or not.

Here is the webadmin help bubble: