Search results

Thanks, but still a little confused. Is the ALL still needed or just the trusted IP's? Any advanced to the file over the GUY or do they both end up doing the same thing?

We're going to be enabling client throttling for a client, but we need to white-list (trust) a couple of IP.s. Do we simply add the ip's like 1.1.1.1T,1.1.1.2T,1.1.1.3T to the allow list and leave the deny list empty or is it ALL,1.1.1.1T,1.1.1.2T so the trusted IP's never get throttled? TIA

That worked perfectly.

We're currently running 5.4.x on cPanel server. Logged into the LSWS interface and went to the version manager. Clicked Download/Upgrade for the 6.0.5 release and it timed out. In looking through the hung up processes it's hung up tring to download the lsws_whm_plugin.tar.gz. I can manually...

It just does not seem to be working. I just checked one of our servers and Max Idle Time is on the default of 60 seconds. Here is a notice from LFD: While I have no way to check it, in 90 minutes, you'd think it would have been idle for more than 60 seconds. This site is also not that busy...

Sorry if this has been discussed, but it's not easy to search for this one. We have an on-going issue where PHP processes are getting hung and just run 'forever'. They are getting detached (i.e. the parent process is 1). Our max execution time is set to 30 seconds. I know that this is more...

To follow up (as others I'm sure will run into this) We ran "Restart Detached PHP Processes." from within the WHM LSWS plugin. Put in a request to cPanel to do that automatically for php.ini changes, PECL /PEAR module installs etc. Thanks again for the guidance.

One other interesting note. I have a phpinfo page on two sites on this VPS that both use EA PHP 7.2. The build date (2nd item in phpinfo) is different between the two sites. That seems somewhat impossible as there is only one EA PHP 7.2. in /tmp/lshttpd the APVH_###_Suea-php72.sock files...

Hello, There are no PHP processes for that user. It's running under cPanel/EAV4 running cgi/suexec. Thanks

Yea, it's just really odd. lsphp -i as the user shows APCu installed. Other sites running PHP 7.2 show it in a phpinfo page. I don't see a php.ini or .user.ini etc. that would be removing the module.

Hello, No, the server is not running CloudLinux.

We have a server with cPanel/EAV4 and LSWS. We installed APCu via PECL (from WHM) for PHP 7.2. If I run the PHP 7.2 from command line with -i parameter, I can see that APCu is installed and active. When I create a phpinfo() page on a site running PHP 7.2 I don't see APCu. I can see that the...

Just following up on this. After a log of digging through their 1000+ line .htacess file, it was an issue with the .htaccess file, not LSWS.

Will do, but we'll prob. have to wait off-hours to do that. It's a fairly busy server. As soon as we can get debug log, we'll get it posted.

There is nothing in the sites error_log. In the main Apache error_log the only thing is that it can't find the sites 403.shmtl page (cPanel default). There is nothing in the stderr.log and it's not getting caught by modsecurity. Thanks

We have a customer that migrated a web site from Windows/.asp to a WordPress based site. They started adding .htaccess code to redirect the old .asp pages to the new corresponding WordPress page. Any .asp page in LiteSpeed simply returns a 403 error. I've checked their .htaccess and I don't...

OK, tracked it down with LSWS support. We had created a cPanel account on this server and it got UID 1000. The account is for 'management' purposes, so it's quota was very small. The LSWS tarball extracted with UID 1000. Because of that the tarball could not fully extract and therefore...

Hello Pong, We've installed LSWS a few dozen times before. Running as root and the file system as 1.9 TB of free space (1% utilization). I also checked and root quota is unlimtied (as it should be).

Exact same error re-installing.

Hello, Yes, fresh install on a brand new cPanel server. Just seems very odd that it got quota errors when the account does not have a quota. Plenty of room in the filesystem etc.