Question: Why do I see “403 Forbidden”? Print

  • best hosting provider, shared hosting guide, GHFS Hosting, SSD web hosting, GHFS web hosting, GHFS cloud hosting, DNS configuration guide, how to transfer a domain, managed hosting services, hosting knowledge base, domain and hosting tutorials, how to register a domain, hosting control panel tutorial, VPS hosting setup, email hosting setup, SSL installation guide, A record guide, DNS records explained, WordPress installation GHFS, MX record setup, CNAME configuration, WordPress migration guide, SSL certificate troubleshooting, optimize WordPress performance, fix internal server error, FTP upload guide, enable SSH access, Linux server commands, secure VPS server, DDoS protection GHFS, MySQL database tutorial, malware removal guide, PHP configuration guide, website security tutorial, firewall configuration VPS, secure hosting best practices, VPS hosting tutorial, cloud server configuration, how to manage Linux VPS, install Docker on VPS, Apache configuration guide, disable root login SSH, Nginx setup GHFS, MySQL optimization, Redis installation, hosting performance optimization, hosting troubleshooting guide, Node.js on VPS, Python hosting tutorial, SMTP configuration guide, secure website setup, server hardening tutorial, Plesk tutorial, SSL troubleshooting, cPanel tutorial, email deliverability guide
  • 0

This article explains the common reasons why a 403 Forbidden error appears on a website hosted with GHFS Hosting and how to resolve it. A 403 error means the server understands your request but refuses to allow access.


1. File and Folder Permission Issues (Most Common)

Incorrect permissions on your website files or folders can cause a 403 error.

Recommended permissions:

  • Folders: 755

  • Files: 644

How to check:

  1. Log in to Plesk

  2. Go to File Manager

  3. Select a file or folder

  4. Click Permissions (or similar depending on setup)

Incorrect permissions should be fixed immediately.


2. Missing or Incorrect Index File

The main homepage file is required for your site to load.

Your website needs an index file such as:

  • index.php

  • index.html

If this file is missing or renamed, you may see a 403 error.


3. IP Access Restrictions in .htaccess

Your .htaccess file may contain rules blocking access.

Common problematic entries include:

  • Deny from all

  • Allow from specific IPs only

  • Incorrect rewrite rules

If you recently edited .htaccess, try restoring a previous version.


4. Security Extensions or Firewalls Blocking Your Access

Security tools like:

  • ModSecurity

  • Fail2Ban

  • Firewall filters

may block access if they detect suspicious activity, even if unintended.

Contact support if you believe your IP is blocked.


5. Incorrect Ownership or Broken Permissions After Upload

If files were uploaded using:

  • Wrong FTP user

  • Incorrect ownership

Plesk may prevent access, resulting in a 403.

Uploading via Plesk File Manager usually avoids this issue.


6. Directory Listing Disabled

If a folder does not contain an index file and directory listing is disabled, you will see a 403 error.

Example:
Trying to open:
https://yourdomain.com/images/

If there is no index file, the server blocks access.


7. Blocked by Domain or Hosting Suspension

If your hosting account or a specific domain is suspended:

  • Website may show 403

  • Access to certain areas may be restricted

Check your GHFS Hosting account status if this may be the cause.


8. How to Fix a 403 Error

Step-by-step checklist:

  1. Ensure index.php or index.html exists

  2. Fix file permissions (755 folders, 644 files)

  3. Remove or correct .htaccess rules

  4. Check if your IP is blocked by security filters

  5. Re-upload corrupted or incomplete files

  6. Confirm your hosting subscription is active


9. When to Contact GHFS Hosting Support

Contact support if:

  • You cannot determine the cause

  • The error appeared suddenly after no changes

  • Security rules are blocking your IP

  • Permissions cannot be corrected

  • The site remains inaccessible after fixes

Support can check server logs and identify the exact reason.


Was this answer helpful?

« Back