Search results

Because you are using a control panel. LSAPI_MAX_PROCESS_TIME is only available if LSWS is used native without any CP.

Whenever you check your page at Pagespeed or any other test sites, check before if to be tested page is already cached, but note Pagespeed doesn't check the loading time. It only tests the "display time". There is big difference.

A bit more information please. Which kind of web server do you use? OLS or LSWS? Do you use quic.cloud? Which cache plugin do you use?

I am afraid that unfortunately I cannot offer more, sorry.

How about this? https://docs.litespeedtech.com/lsws/cp/cpanel/wp-protect/ https://docs.litespeedtech.com/lsws/cp/cpanel/tunings/#maxconnperclient

Did you check if mod_speling is installed?

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

FYI: Almost all setting options that you can find in the LiteSpeed documentation are only relevant if you don't use a control panel. This means that the relevant settings must be made in the relevant control panel. The only exceptions to this are a few setting options.

@AndreyPopov FYI: Almost all setting options that you can find in the LiteSpeed documentation are only relevant if you don't use a control panel. This means that the relevant settings must be made in the relevant control panel. The only exceptions to this are a few setting options.

This forum is for LiteSpeed Enterprise. For OLS please use OLS forum: https://forum.openlitespeed.org/

Have you already looked at the error_log?

The input for max_idle_time takes place in seconds.

Have you tried changing the behavior of Lynx with the connection_timeout parameter? Or check this: https://docs.litespeedtech.com/lsws/extapp/php/configuration/control/#max-idle-time

Then it's up to the function of your script. Is shell_exec mandatory for the script?

Try both, but in case you don't know it. PHP version in console or for cron is not the same as for the frontend lsphp and LSWS is not in use in console or for cron In console or for cron everthing is controlled by control panel, so your issue has nothing to do with LiteSpeed.

If the script also aborts prematurely as cron, then ask DA. DA is weird in some ways...

Yes, in .htaccess. If you only have LiteSpeed running <IfModule Litespeed></IfModule> is optional.

There is usually no timeout limit in the console, so you shouldn't have any problems in the console. However, it makes a difference whether the PHP script actually runs as cron or you run the script manually in the console, because then there is a SSH timeout. Regardless, try this timeout code...

Yes, but needs extra cache vary settings in .htaccess, if this plugin sets a cookie depending on country. It would also work without cookies, but then requires the GeoIP database. For more information, please contact Cache Plugin Support on the Wordpress Forum, as this forum does not support the...

I don't want to completely rule it out, but based on your description, the cause could most likely be the plugin. Regardless, you should contact LiteSpeed Support directly. support@litespeedtech.com