Search results

We need to check the real URL having this problem to find out what happened.

You can try the suggestion by NiteWave, but you may need to update cPanel default template as it already has ErrorDocument configured to /404.shtml in /usr/local/apache/conf/includes/errordocument.conf

Please do rm /home/cpeasyapache/ls.src/php-litespeed-6.7.tgz then do force rebuild matching PHP. No configuration changes, just need to rebuild matching PHP. Are you using PHP selector? Are you using PHP 5.3.29?

Please force reinstall 4.2.14, then force build matching PHP. it should be taken care of.

If you switch back to Apache temporarily, will it show suspended page? Maybe server side page cache is enabled? please check the response header for "X-LiteSpeed-cache: hit" with browser developer tool.

You need to update PHP to 5.4 with litespeed API 6.6+, you can install it from Remi repository.

No, maybe in the future.

which version of cPanel are you using? which version of LSWS enterprise? LiteSpeed redirect access to suspend account to http://domain.name/cgi-sys/suspendedpage.cgi, works the same way as Apache. It is working fine in our lab environment. Maybe we need to login to take a look if you are...

Latest 4.2.14 build should be able to take care of this.

Please try again, the updated package was not uploaded properly.

The newly created vhost must be adding "php_admin_value include_path ... " to the vhost configuration, it is could be due to vhost configuration change.

Please force reinstall to try latest build of 4.2.14, added error logging when a rule has been hit and SecDebugLogLevel is not 0.

oops! we will have it fixed, you can just patch the source code at lsws/admin/html/utility/build_php/buildconf.inc.php

added, will be in next release.

You just need to change the threshold in the comodo ruleset.

One related bug has been fixed with latest 4.2.14 build. Please force reinstall 4.2.14 see if the issue has been addressed or not.

Are you using cageFS? try disable CageFS for this user temporarily see if it works. Maybe the Locale files are missing under that cage, causes PHP failed to set the locale. Otherwise, please add "sleep(30)" at the beginning of the script, then you can locate the process serving the script and...

Also, you need to make sure to get latest 4.2.14 build with /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.14

The key is that lsphp need to exactly match Apache's PHP, module configuration wise. Need to comparing phpinfo output, add missing modules, match runtime configurations.

I think we have to login the server to investigate what causing it.