Forbidden
You don't have permission to access /
on this server.
============
### Troubleshooting: "You don't have permission to access / on this server."
This error message, often a **403 Forbidden** error, indicates that the web server has received the request but is refusing to fulfill it. This is a common issue that can be caused by several factors related to file configuration and permissions. This guide will walk you through the most common causes and how to troubleshoot them.
-----
### Cause 1: Incorrect File Permissions (CHMOD)
File permissions (also known as CHMOD) control who can read, write, or execute files and directories on your server. If these permissions are set incorrectly, the web server may be unable to read the files, leading to a permission denied error.
#### **Troubleshooting Steps**
1. **Connect to your server** using an FTP client (like FileZilla) or via SSH.
2. **Navigate to your website's root directory.** This is usually `public_html` or `www`.
3. **Check permissions:** Right-click on your directories and files to view their permissions.
* **Directories** should typically have permissions set to **755**. This allows the owner to read, write, and execute, while others can only read and execute (which the web server needs).
* **Files** should typically have permissions set to **644**. This allows the owner to read and write, while others can only read.
4. **Correct permissions:** If the permissions are incorrect, change them to the recommended values. In most FTP clients, you can do this by entering the numerical value (e.g., 755) in the permission settings.
-----
### Cause 2: A Missing Index Page
When you access a directory (like your domain's main folder), the web server looks for a default "index" file to display. Common names for this file include **`index.html`**, **`index.php`**, **`default.html`**, or **`home.html`**. If no such file exists, the server may be configured to deny access to prevent a directory listing, resulting in a 403 error.
#### **Troubleshooting Steps**
1. **Connect to your server** with an FTP client or file manager.
2. **Navigate to the directory** where you are getting the error.
3. **Look for an index file:** Confirm that an index file with a correct name exists. The file name must be lowercase and spelled correctly.
4. **Upload or rename the file:** If the file is missing, upload a new one. If it has an incorrect name (e.g., `Index.html` instead of `index.html`), rename it to the correct, lowercase format.
-----
### Cause 3: Misconfigured .htaccess File
The **`.htaccess`** file is a powerful configuration file that can override global server settings for a specific directory. A common misconfiguration that causes a 403 error is a `Deny from all` directive, which blocks all access to the directory it resides in.
#### **Troubleshooting Steps**
1. **Connect to your server** via FTP or file manager.
2. **Locate the `.htaccess` file:** This file is a hidden file, so you may need to enable "show hidden files" in your FTP client settings.
3. **Examine the file:** Open the `.htaccess` file in a text editor. Look for any rules that might be blocking access, such as:
```
Order deny,allow
Deny from all
```
4. **Test the file:** If you suspect the `.htaccess` file is the cause, rename it to something else (e.g., `htaccess.bak`) and try accessing your site again. If the error goes away, you know the `.htaccess` file is the problem.
5. **Edit or replace the file:** You can then either edit the file to remove the problematic directives or replace it with a clean, default version.
