• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue 403 Forbidden errors

zain

New Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Plesk Obsidian 18.0.53 Update #1
Hello,
I get 403 Forbidden errors when the browser sends lots of requests fast to the server. For example, when opening a gallery page with tens of images, the server starts to respond with 403 and half of the images doesn't show.
How can I change this behavior?
Thanks
 
The "403 Forbidden" error you're encountering when loading a gallery page with many images can be caused by several factors related to your server configuration and security measures.

1. Check File Permissions (CentOS with Plesk):
  • Access your server via SSH or the Plesk control panel. exclamation
  • .Use the ls -l command to view directory and file permissions.
  • Example: ls -l /path/to/your/gallery/directory
Interpret the output:

  • The first character represents the file type (d for directory, - for regular file).
  • The next three characters represent owner permissions (read, write, execute).
  • The following three represent group permissions.
  • The last three represent other permissions.
Adjust permissions if necessary:

Example: To give the owner full permissions and others read and execute permissions, use:
chmod 755 /path/to/your/gallery/directory
chmod 755 /path/to/your/gallery/images/*.jpg
# Replace *.jpg with the actual image extension

2. Review Security Settings:
  • Log in to your Plesk control panel.expand_more
  • Navigate to Security > Hotlink Protection.
  • Disable hotlinking protection if needed.
OR

  • Configure hotlinking protection to allow access from your domain.
  • Navigate to Websites & Domains > your domain > Security > ModSecurity.
  • Search for rules related to image requests or hotlinking.
  • Disable or adjust specific rules cautiously.
3. Check Cloudflare or CDN Settings:

  • Log in to your Cloudflare account (if applicable).expand_more
  • Disable security settings temporarily to check if the issue persists.exclamation
  • Consult Cloudflare documentation or customer support for specific troubleshooting steps.
4. Additional Troubleshooting:

Clear your browser cache and reload the page.

Before you make any changes, make sure you know what you're doing, and always back up your data.
 
Back
Top