If there is such a file, it should be moved temporarily: # cat /etc/sysconfig/kcare/systemid It is necessary to check if there is a separate file on the server, from which KernelCare gets the incorrect server ID.
No valid key-based license found # kcarectl -u If mod_security rules are enabled, they may be triggerred for 403 error.On a server with Imunif圓60, KernelCare patches cannot be installed and the KernelCare license cannot be verified due to errors: # kcarectl -license-info In most cases your IP address will be denied in the system firewall (iptables, firewalld etc) and you need to remove your IP address in order to avoid the error. are enabled, depending on what and how many requests you are doing for a particular website, the firewall can block you. If Mod Security, WAF, fail2ban, CPHulk, etc. To fix the problem, either change all files user:group to user:user ( in the above example, that would be jsmith:jsmith), or disable Force Strict Ownership in LSWS Admin. If it is different, a 403 Access Denied error will be returned. If it is enabled, the web server will check if the owner of the file being served is the same as the owner of the virtual host. The Force Strict Ownership setting in LSWS Admin specifies whether to enforce strict file ownership checking. home/jsmith/public_html>ls -ald images/detailedĭrwxrwxrwx 51 jsmith jsmith 4096 Apr 11 13:16 images/detailedĭrwxrwxrwx 48 jsmith jsmith 4096 Mar 31 16:30 images home/jsmith/public_html>ls -ald images/detailed/130ĭrwxrwxrwx 2 nobody nobody 36864 Apr 14 15:12 images/detailed/130 rw-rw-rw- 1 nobody nobody 103609 Apr 12 11:21 images/detailed/130/Untitled-1-Recovered_urba-uz.jpg home/jsmith/public_html>ls -ald images/detailed/130/Untitled-1-Recovered_urba-uz.jpg Switch back to LiteSpeed Web Server, and keep reading! Even though it is not a server problem, we have provided the following troubleshooting documentation that we hope will help you to find the solution. If Apache experiences the same problems, then the issue is not a LiteSpeed Web Server issue. Please open a ticket from your client area or email and provide as many details as possible, so that we may assist you. If the error could not be triggered under Apache, then the problem is likely to be a LiteSpeed server issue. Repeat the steps that originally led to the issue.Īre you able to reproduce the error under Apache? NO ¶.If your server is running on an Apache control panel, such as cPanel or Plesk, there is an easy way to determine whether an issue is caused by your LiteSpeed server: It is rare for the web server to be the cause of a 403 error, but just to be safe, you should rule that out first thing by checking whether the error occurs with Apache as well.
Have you checked your log files? They usually show you the cause of the error!Įrror 403 Forbidden can be triggered by many things, including permission issues, configuration restrictions, security settings, etc. LiteSpeed Memcached LiteSpeed Memcached.
0 kommentar(er)
