{"id":485,"date":"2021-07-27T23:19:55","date_gmt":"2021-07-27T23:19:55","guid":{"rendered":"https:\/\/hoganhost.com.ng\/blog\/?p=485"},"modified":"2024-08-12T13:34:44","modified_gmt":"2024-08-12T12:34:44","slug":"request-timeout-500-internal-server-error-on-litespeed","status":"publish","type":"post","link":"https:\/\/hoganhost.com.ng\/blog\/server\/litespeed\/request-timeout-500-internal-server-error-on-litespeed\/","title":{"rendered":"Request Timeout – 500 internal server error on Litespeed"},"content":{"rendered":"

\"\"<\/h1>\n

Run PHP without Timeouts<\/h1>\n
\n

This covers how to set up LiteSpeed Web Server so that a long-running PHP script will not be interrupted before it has finished.<\/p>\n<\/div>\n

Reason<\/h1>\n
\n

Some PHP scripts need to run for long periods of time without interruption. Examples include WordPress modules such as BackupBuddy, ImportBuddy, or any other module that relies on a WordPress built-in cron job. Whenever a PHP application rebuilds MySQL indexes, the process may run for a long time.<\/p>\n<\/div>\n

How-To’s<\/h1>\n
\n

Generally, allowing a PHP script to run forever is not desirable. Thus there are a number of features (in LSWS and built into PHP) that may prevent a PHP process from running long enough to finish. You may need to set up more than one of the following configurations to ensure your application works correctly.<\/p>\n<\/div>\n

Turn off aborting for a broken connection<\/h2>\n
\n

When a user closes a connection (by closing a window, for example), LSWS will abort processing that PHP script by killing the PHP process. This is to avoid wasting system resources and prevent certain types of DoS attacks.<\/p>\n

In some cases, though, it is preferable to not to abort the PHP script regardless of whether the connection has been closed. For example, WordPress built-in cron jobs start a background job by sending a request to\u00a0wp-cron.php<\/code>\u00a0then immediately closing the connection without waiting for response. In order for the cron job to complete, though, the web server must keep the PHP engine running without interruption.<\/p>\n

With Apache mod_php, the ignore_user_abort setting allows a user to trigger a long-running process and then close the browser or navigate away from the page without killing the PHP\/MySQL process. This setting is not supported by LSWS (or any Apache suEXEC setup).<\/p>\n

Aborting for a broken connection can instead be turned off at the server level in LSWS’s WebAdmin console or by using LiteSpeed’s \u201cnoabort\u201d environment variable.<\/p>\n<\/div>\n

Globally via the WebAdmin<\/h3>\n
\n

WebAdmin console > Configuration > Server > General > External Application Abort<\/p>\n

Set External Application Abort to \u201cNo Abort\u201d to stop all applications from aborting even when a connection has been broken.<\/p>\n<\/div>\n

Through the “noabort” environment variable<\/h3>\n
\n

Aborting for a broken connection can be turned off by using the request-level \u201cnoabort\u201d environment variable. This can be done in a rewrite rule or using the SetEnv\/SetEnvIf directives. \u201cnoabort\u201d is a LiteSpeed-specific environment variable, so all the following rules should be placed in<\/p>\n

<IfModule Litespeed> \r\n...\r\n <\/IfModule><\/pre>\n
The\u00a0[E=noabort:1]<\/code>\u00a0flag can be added to any rewrite rule. The rewrite rule can be in an Apache .htaccess file or vhost-level configuration file. The rewrite flag should usually be used for a single account only. If you need to do a server-level configuration that will apply to all accounts (though perhaps only for certain scripts), you should use the SetEnvIf directive.<\/p>\n<\/div>\n
Rewrite rule examples:<\/h4>\n
\n