Search results

I think it is a PHP issue, maybe a missing PHP module, if you use Zend extension manager, please make sure the permission of addition extension configuration directory have been set properly. Please check error.log and stderr.log for any error messages related.

Please PM me your login for the admin console if possible. I will take a quick look.

Since reverse DNS lookup will slow everything down, only IPs are logged, awstats has option to perform the DNS lookup when update the statistic results.

You need to add "index.php" to server or vhost level "Directory Index" configuration.

You can set the URI of Rails Context to /forum/, also remember to change the rails route configuration. it should work.

Thanks for the update. Since there is no standard way to set PATH_INFO environment variable, some server set it for some application, some servers do not. The best way to fix it is to test PATH_INFO env in Python and set it to the desirable value if missing.

check the rails log file, it returns 500 error, strace the ruby process see if you find out why. you can stace the webrick process as well and compare the strace log.

Please check the tips for trouble shooting. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:rails:troubleshoot

That's possible, admincp should be excluded from vbSEO, seems it has the rule to execlude it according to the posts from other users in the past. But, anyway, it should not cause PHP to crash, so you need to strace lsphp to find out why PHP crashed in the middle of that request. Just put...

Please download the 3.3.4 release by changing the version number in the download link.

What is your OS? which version of LSWS are you using? have you upgrade it recently? how about revert it back to previous version?

You really need to "strace" the lsphp process to see what is going on, if you run LiteSpeed in chroot jail, there might be missing libraries that required by lsphp. so, try it without chroot. And when using with cPanel, I don't think it is a easy task to make chroot lsws work properly, it is...

Please try sudo -u nobody /usr/local/bin/ruby /usr/local/lsws/fcgi-bin/RailsRunner.rbThen keep trying until you figured out the permission problem. :) Once it passes, your litespeed rails will work. Command sudo -u nobody strace /usr/local/bin/ruby...

Try changing "Ruby Path" under "Rails" tab to another ruby executable, if it was /usr/bin/ruby, change it to /usr/local/bin/ruby or vice versa.

Please contact site owner.

You should use "/" for the URI, it was "/usr/local/bin/ruby".

I think you will not notice big difference unless the I/O wait is higher than maybe 20%. nothing I aware of.

LSWS run Rails App in suEXEC mode, so if you run your app as root from command line, there might be permission problem, you should fix those problems. And you should start WEBrick or other RoR server as the user own the public directory of the app. Another difference is that LSWS by default...

Hosting control panels usually analyze the access log or dedicate traffic log and limit the usage. You can do the same with LiteSpeed. LiteSpeed internally will not provide this feature.

Do you have multiple Ruby installed on your server, make sure the right one used under the "Ruby" tab. Check your error.log and stderr.log, turn on debug logging if need.