Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:config:understanding_500 [2018/09/20 13:32]
Jackson Zhang [Bad PHP Code]
+++ litespeed_wiki:config:understanding_500 [2019/12/10 19:33] (current)
Lisa Clarke [Use Debug Logging to find out the real cause] Copyediting
@@ Line 71: / Line 71: @@
 The correct syntax is the following and it should fix the 500 error for Apache:
   Header always set Strict-Transport-Security: "max-age=63072000; includeSubDomains; preload"
+==== Example 5 ====
+Syntax wrong for the following:
+  Options All –Indexes
+It should be:
+  Options -Indexes
+==== Example 6 ====
+''php_value'' and ''php_flag'' are for mod_php handler. Most of the time php-fpm or lsphp will be used and mod_php has been deprecated most of the time. When you use ''php_value'' or ''php_flag'', Apache will return 500 error. However, lsphp supports php override in .htaccess without any problem and there is no 500 error when running LSWS.
 ===== Different level of Rewrite rules misplaced to the wrong level =====
@@ Line 130: / Line 138: @@
 It will bring the website to 500 immediately.
 This is only one example. Many times, wrong PHP syntax will lead to a 500 error.
+Another example is:
+  <?php
+  phpinfo():
+  ?>
+A typing error '':'' in phpinfo page , which should be '';'', will lead to 500 error.
 ===== PHP Code with wrong php configuration settings =====
-Sometimes, 500 error may be not easy to locate. If you move .htaccess to .htaccess.bak and move php.ini to php.ini, the 500 error still happens, it might be something wrong in the PHP code and it might be hard to find.
+Sometimes, a 500 error may be not easy to locate. If you move ''.htaccess'' to ''.htaccess.bak'' and move ''php.ini'' to ''php.ini.bak'', and the 500 error still happens, it might mean there is something wrong in the PHP code. That can be hard to find.
-We experienced a case with WHMCS. In configuration.php, someone placed wrong php setting there:
+We experienced a case with WHMCS. Someone placed an incorrect setting in ''configuration.php'':
   $display_errors = E_All;
-"E_All" is an incorrect value for PHP setting "$display_errors" and it is for "$error_reporting". "$display_errors" should be either "true"/"false", or "on"/"off". Changed it to the following as "true" and it fixed the 500 error.
-  $display_errors = true;
+''E_All'' is an incorrect value for the PHP ''$display_errors'' setting. Rather, it is meant for the ''$error_reporting'' setting. ''$display_errors'' should be either ''true''/''false'', or ''on''/''off''. We changed it to ''true'', and that fixed the 500 error.
+  $display_errors = true;
 ===== PHP Handler Not Set =====
@@ Line 148: / Line 161: @@
 ===== CloudLinux LVE Limit Reached =====
 When using CloudLinux, If the site is limited by memory or process limits, then the user may receive 500 errors because the server cannot execute the script. [[https://docs.cloudlinux.com/index.html?lve.html| Learn more.]]
+For example,  you might see some error like the following:
+-01-11 00:14:23.330946 [ERROR] [APVH_xsrvnecw_Sulsphp56:]: Failed to start one instance. Resource limit reached!
+The above indicates an Error by Cloudlinux. Increasing the LVE for that user may fix the issue.
 ===== PHP Upgrade =====
@@ Line 247: / Line 267: @@
 </code>
 You can check the example [[https://users.cs.cf.ac.uk/Dave.Marshall/PERL/node196.html|here]].
+===== OWASP ModSecurity rule set may trigger 500 when using Imunify360 together =====
+If you use LSWS ealier than 5.4.1 build 7, you may see 500 error when both OWASP and Imunify360 used at the same time. LSWS 5.4.1 and above version should have fixed this issue and LiteSpeed user can use both rule sets at the same time.
+OWASP rule set may conflict with the Imunify360 default rule set on a server running LiteSpeed Web Server. Please choose only one mod_security rule set.
+For OWASP rulesets, in crs-setup.conf:
+  SecAction "id:900990, phase:1, nolog, pass, t:none, setvar:tx.crs_setup_version=302"
+in /etc/apache2/conf.d/modsec_vendor_configs/OWASP3/rules/REQUEST-901-INITIALIZATION.conf
+  SecRule &TX:crs_setup_version "@eq 0" "id:901001, phase:1, auditlog, log, deny, status:500, severity:CRITICAL, msg:'ModSecurity Core Rule Set is deployed without configuration! Please copy the crs-setup.conf.example template to crs-setup.conf, and include the crs-setup.conf file in your webserver configuration before including the CRS rules. See the INSTALL file in the CRS directory for detailed instructions.'"
+crs-setup.conf has to be loaded first then the rest of rules including REQUEST-901-INITIALIZATION.conf.
+Imunify360 could break the loading order of the above rule set and lead to "500" errors.
+===== Use Debug Logging =====
+Debug logging is helpful when looking for the cause of 500 errors. To begin capturing debug logs, please see [[ https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:bug-reporting#how_to_toggle_debug_logging_and_capture_output|How to Toggle Debug Logging]].
+You can investigate these logs further, or you can forward them to our Support Team for assistance.