Note: This guide needs root access to the server. It is for VPS and dedicated server owners. It applies to the LiteSpeed web server.
What does the message mean?
A web server is the program that sends web pages to visitors. LiteSpeed is one kind. A context is a rule for one folder or web address, such as /image/. An ACL, or access control list, is a list that says who may enter and who may not.
So the message means a visitor was refused. The visitor's address was not allowed by the ACL on the /image/ context. You see it in the error log. Visitors may see a "403 Forbidden" page.
Warning: Do not simply open access to everyone. Find out who should be allowed. Take a backup of any file before you change it.
Common causes
- A context has an "Accessible" list that does not include the visitor's IP address. An IP address is the number that names a computer on the internet.
- A "Denied" list blocks the address. Maybe a security tool added it.
- An old
.htaccessfile hasDeny from allorRequire all deniedlines. - Hotlink protection is blocking images used from other sites.
Steps to fix it
- Find the real error. Read the LiteSpeed error log.
tail -n 50 /usr/local/lsws/logs/error.log
This shows the last 50 lines of the log. Look for the IP address that was blocked.
- Log in to the LiteSpeed WebAdmin Console. Its address and login come from your server setup.
- Go to Virtual Hosts and pick your site.
- Open the Context tab and click the
/image/context. - Look at the Access Control section. Check the Allowed List and Denied List.
- Add the right address to the allowed list, or remove it from the denied list. Use
ALLonly if the images should be public. - Save, then do a Graceful Restart.
- Check for an
.htaccessfile in the image folder.
cat /home/user/public_html/image/.htaccess
This prints the file so you can read it. Remove or fix any lines that deny access.
- Check file permissions. Folders should be 755 and files 644.
Quick recap
- The message means the ACL of the
/image/context refused a visitor. - Read the error log to see which address was blocked.
- Fix the allowed and denied lists in WebAdmin, then restart gracefully.
- Check
.htaccessand file permissions.