Search results

great, thanks for the info!

I keep getting emails from LFD (cpanel install) that look like this: Time: Sun Jan 22 17:01:59 2017 -0500 Account: lsadm Resource: Process Time Exceeded: 17369408 > 1800 (seconds) Executable: /usr/local/lsws/bin/lshttpd.5.0.13 Command Line: litespeed (lshttpd) PID...

THANKS! That fixed it!

Unfortunately I'm still getting the same 404 errors.

Here is one: <Directory /home/site/public_html> <FilesMatch "\.(gif¦jpe?g¦png¦ico¦css¦js¦swf)$"> Header set Cache-Control "public" </FilesMatch> <FilesMatch "\.(ico)$"> Header set Cache-Control "max-age=29030400, public" </FilesMatch> # START E-Tag <ifModule mod_headers.c> Header unset ETag...

Unfortunately forcing the update still results in 404 errors on pages that are rewritten. This is a cpanel/WHM install, so public_html is under all accounts like /home/site/public_html. Regardless there are only two site that have rewrite rules in the pre_virtualhost_2.conf file.

The rules are contained in the apache pre_virtualhost_2.conf file. The directory is specified before each set of rules. i.e. <Directory /home/site/public_html> RewriteEngine On ...

This exact error has popped up again when going from 5.0.7 to 5.0.10, I just tried to go to 5.0.12, and it still happened. Any ideas?

I believe the "Fixed a regression in rewrite engine that broke some existing rewrite rules when upgrading from LSWS 4.2.x." that was fixed in 5.0.3 solved the issue I was having. Everything now works correctly in 5.0.4.

I checked the error logs and all they say is that there are not found errors. It's like the rewrite rules aren't being applied at all. I see that the file is being loaded by litespeed when it starts though.

After I update to 5.0.2 from 4.2.19 I'm getting 404 errors on all pages that have rewritten URLs. I use WHM and the the rewrite rules are in the Pre VirtualHost Include file. Any ideas?

now that vbseo is no longer supported, has anyone gotten this to work with DESEO? Just curious...

thanks for explaining :)

I forwarded that to the bug email address, btw... What happens to the bug report from there?

here we go: At [27/Mar/2014:13:17:02 -0400], web server with pid=16347 received unexpected signal=6, a core file has been created. A new instance of web server will be started automatically! Please forward the following debug information to bug@litespeedtech.com. Environment: Server...

ah, a clue: At [26/Mar/2014:21:32:23 -0400], web server with pid=11170 received unexpected signal=6, a core file has been created. A new instance of web server will be started automatically! Please forward the following debug information to bug@litespeedtech.com. Environment: Server...

I realize that installing a RC on a production server is probably a bad idea, but I did want to see how 5.0 would run. Unfortunately the number of lsphp5 processes jumped to about 50 and the load went through the roof. I didn't have it installed long enough to figure out why. I didn't change any...

Ah, I figured it out - it was actually an htaccess file that said 'deny from all' in it. Is there a setting that applies that recursively to all subfolders and files?

I still have one user that is getting a 403 message on image files that were uploaded (wordpress). Is there something else that could cause this?

ah, I knew I was missing a setting. Thanks!