Search results

how about a simple phpinfo.php page ? and just remove <IfModule mod_php7.c></IfModule> ?

again, please refer https://www.litespeedtech.com/products/litespeed-sapi/php/suexec-processgroup "If you wish to use suEXEC Daemon mode for some users while using ProcessGroup for others, change Run On Start Up (WebAdmin console > Configuration > External App > your external application) to...

there is a similar user case some days ago. the reason was LVE failure, can find some error messages in /usr/local/apache/logs/error_log and stderr.log the root cause of this case was disk quota exceeded for many accounts and caused LVE failure. the host only assign about 250M(?) to each...

1. I read the wiki page, since only 1 line of RewriteCond, the last rewrite flag [NC,OR] should change to [NC] not sure if this will affect the final result. 2. to determine if a device is mobile or desktop can be very difficult or very complex logic. when you say have you confirmed manually...

if it's daemon mode, opcache will keep there unless lsws is restarted. however, for a share host will thousands of accounts, there are many factors will have WHM/cPanel restart web server. so opcache will restart along with web server restart.

in the wiki: "Important: Your rewrite rules must exactly match your backend's mobile detection" can you confirm ?

in the screenshot, you set Run On Start Up: suEXEC Daemon so it's Daemon mode.

do you know which suExec mode lsphp 7.1.2 is running ? Worker / ProcessGroup / Daemon ? (refer https://www.litespeedtech.com/products/litespeed-sapi/php/guide-to-suexec-setups for document)

have you changed Max Request URL Length (bytes) : 8192 Max Request Header Size (bytes):16380 in lsws web admin->Server->Tuning->Request/Response ? if not, that mean request header has exceeded default 16380 bytes, that's abnormal, and the error message shows that lsws has detected it and...

maybe you can take a look at xhprof : http://pecl.php.net/package/xhprof

you can set RewriteLogLevel 9 in httpd.conf ( http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriteloglevel ) and check error.log, to see the detail rewrite process to investigate why.

please try #yum install libmcrypt-devel then rebuild again

you might miss some code in .htaccess ? how do you tell web server to map /404/ to /path/to/404.php ? you can post the whole .htaccess here or PM me.

in case you've not read it yet, here's simple solution without cache plugin: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:no-plugin-joomla if the plgin out, will list on https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache

regarding absolute path, can you further confirm, it's relative to document root or absolute path on file system. for example, in .htaccess ErrorDocument 404 /my-path-to/404.php it should be relative path to document root, its absolute path in file system maybe...

how about ErrorDocument 404 /path/to/404.php ? is there a direct URL for 404.php ? assume it's /abc/404.php, then try ErrorDocument 404 /abc/404.php

if cPanel restart web server(apache or litespeed) after process bandwidth, web server will have to restart. you can ask for cPanel support, if this is a designed behavior by them.

yes, rewrite rule do the same trick. if you comment out and leave only block, it should work too.

that's because of browser cache. clear all browser cache or access it in another browser, see if it's fixed.

the rewrite rule has no problem, though I think no need to modify, just revert to original one would be good. what's your cache policy settings? have you followed https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:common_installation:cpanel-shared#cache_policy_settings ...