Search results

http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewritecond -f Is regular file. Treats the TestString as a pathname and tests whether or not it exists, and is a regular file. -F Is existing file, via subrequest. Checks whether or not TestString is a valid file, accessible via all the...

I did tests on a cPanel server test URL: domain.com/a.log <LocationMatch ".+\\.(?i:psd|log|cmd|exe|bat|csh|ini|sh)$"> Require all denied </LocationMatch> 200 OK for lsws but 403 forbidden for apache but if remove a \, i.e. <LocationMatch...

please refer https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:rewrite-logs to enable rewrite log to know which rule has been wrong another tip is to switch to apache, to see if it work as expected or not

I think the issue can be simplified as : when "Start By Server" set to "No", it succeeds. when "Start By Server" set to "Yes", failed to set up when lsws start up, so "403 Forbidden" error. you can check the initial error logs when lsws start up, it should have something about the failure.

not very clear about your question. for example, there is a backend URL https://showbox.cam/wp-content/uploads/2020/01/ShowBox-1-300x300.png what you want the front URL to be ? www.example.com/shop/wp-content/uploads/2020/01/ShowBox-1-300x300.png or...

can you follow https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:other-ext-apps:apache-mod-perl-equivalent to get any-file-name.pl to work it should be same as .jss

if you run /home/cginodetest/www/cgi-bin/cgi-node.js directly on command line, what's the output ?

again, create a phpinfo page, check "error_log" settings, set it as "error_log" instead of "/usr/local/apache/logs/error_log"

please create a phpinfo page, and compare open_basedir between litespeed and apache.

how much have you increased to ? please increase it further. if increase it until 50G, still fail(should be impossible), please let us know

you can PM the access, I can login to take a look

maybe mod_security caused the error. you can follow https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:waf:disable-waf-in-htaccess to disable mod_security temporarily to see if such 403 will be gone

how about "auto_prepend_file" -- https://www.php.net/manual/en/ini.core.php#ini.auto-prepend-file in .htaccess, add php_value auto_prepend_file my_acl.php

you're right: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:unsupported_apache_modules_by_lsws I think you can move the logic to the backend app.

the path of your .htaccess ?

can you create a .htaccess under /archiv/forum/ with content AddType application/x-httpd-php html see if it will work ?

can you check if timezonedb.so is there ? e.g., on one cpanel server: /opt/cpanel>find . | egrep "timezonedb.so$" ./ea-php70/root/usr/lib64/php/modules/timezonedb.so ./ea-php71/root/usr/lib64/php/modules/timezonedb.so ./ea-php56/root/usr/lib64/php/modules/timezonedb.so...

is your ea-php 5.4/5.5 installed on the server ? or only part of files are left on the server ? for example, check one directory ~>ls -al /opt/cpanel/ea-php54/root/usr/bin total 12056 drwxr-xr-x 2 root root 205 Apr 30 01:17 . drwxr-xr-x 8 root root 81 Feb 14 18:16 ...

lsws web admin -> Actions -> Real-Time Stats it's quite useful to check health status of the whole web server, including DDos attack.

litespeed is compatible with apache. you can refer apache document : https://httpd.apache.org/docs/current/mod/mod_expires.html