Search results

This issue is likely fixed in our 4.1.7 release. We got positive feedbacks from a customer experiencing similar problem.

I think you should switch back to Apache, and make sure everything work properly, then start to trouble shoot LiteSpeed. Make sure LiteSpeed is running as the same user that Apache running as. If Apache is not running as "nobody", you should not change owner to "nobody". To change that, you need...

Please check /usr/local/lsws/logs/ap_cmd_param.log see if there is anything logged during the restart.

check permission of /home/prandah

The license need to be released then register a new key. who order the license should be able to release it from client area.

checked the server, it is cpanel request graceful restart every 2 hours, maybe for log rotation, check /usr/local/cpanel/logs/safeapacherestart_log

not possible now due to the complexities of combination of shtml and cache layers.

Once you know how to setup it up properly, put it on your busiest server, you will be amazed by the result, unless all of your servers are under loaded.

WHM plugin works properly for me. Just login to WHM, go to "plugins"->"LiteSpeed Web Server", then click "Build Matching PHP Binary" link. If you still have problem let us know.

you can get volume discount if you need more than 4 licenses.

PM a temp root access, I can take a look if you want. The WHM plugin should not break. which version of cPanel are you using?

If "litespeed" is running, you can use command /usr/local/apache/bin/httpd uninstall service httpd start to switch back to apache. then, you can remove /usr/local/lsws directory, then start over.

do not use the "uninstall.sh", just use the uninstall link in WHM plugin.

Make sure you did not install mysql-* rpm, If you do, you have to unisntall them. cpanel must use MySQL-*.rpm from cPanel. switch back to Apache, then run cpeasyapache. then build matching PHP.

just build matching PHP from WHM LSWS plugin.

It turns out to be misconfiguration in apache conf.

you can try "traceroute", could be network configuration issue.

Please give latest 4.1.6 a try, and if problem persist, we can do more investigation if you can provide a test server that can be taken down for a while.

We tested custom error page feature, it is working fine. I think rewrite rule may messed up the error page URL, as the URL will be injected into rewrite engine when processed. You can enable rewrite log only first, see if you can figure something out. You can dynamically turn on/off DEBUG...

You'd better changing cPanel's vhost template, otherwise, cPanel may overwrite the change when need to regenerate httpd.conf.