Search results

The autoindex script will index the symlinked directory, it was not protected, but user cannot access any file under the symlinked directory. This is issue will be addressed in 4.0.19 release. 4.0.19 build has been uploaded, if you want to give it a try, just change the version number in the...

How does it work? If it served by LiteSpeed web server directly as static file, we will look into this. If it is served via a PHP shell or other script, it has nothing to do with this feature, the script runs in its own process, not controlled by LiteSpeed security. Just want to make sure you...

Please check the PID in the error log file, see if it is a lshttpd process or a helper process. Some thing is killing that process with signal SIGTERM. It is not caused by litespeed bug. Does it happen regularly? or after a graceful restart? should tell from log file.

increase http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout

You should contact Hawkhost support regarding your issue.

just hit <enter> when prompt for Destination.

Please check the phpinfo() page output, see if SERVER["MAGE_RUN_xxxx"] variables are set or not. if not, adjust php.ini to let PHP create those variables from environment.

LiteSpeed wont be able to control external web scripts, if you use PHP for the web script, it is likely the open_basedir configuration of php to prevent the script from accessing /etc/*. you can compare phpinfo page between 4.0.18 and 4.0.17.

It shows 408 timeout, you need to increase "connection timeout". http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout

you need to check /usr/local/apache/logs/stderr.log and error_log

Anything in the /usr/local/apache/logs/error_log around 11:15am, before you manually start the server. Maybe try a reinstall from the WHM plugin.

Looks like your script just copy the file from one location to another, the file has been uploaded successfully to the server? If the script takes long time to finish and PHP is not run in suEXEC mode, you need to increase LSAPI_MAX_PROCESS_TIME http://www.litespeedtech.com/php-litespeed-sapi.html

Please try the latest 4.0.18 build. If you use 4.0.18 already, try "Force reinstall" from web console.

How much memory used by LSWS 4.1 release? How many accounts hosted on that server? Want to know how much memory 4.1 saves.

for cpanel server, it is /usr/local/apache/logs/error_log and /usr/local/apache/logs/stderr.log

Sorry, the previous fix is not right, updated again, please give it a try.

Please try the updated 4.0.18 package.

Please update again, the previous build may stop logging into access log files.

This issue should be addressed with updated 4.0.18 build.

You can try our 4.1RC4 build, it should reduce the memory usage dramatically. http://www.litespeedtech.com/packages/4.0/lsws-4.1RC4-ent-x86_64-linux.tar.gz i386 package is available as well.