Fix Permissions

This page explains the Fix Permissions screen in the GoAdmio Admin Panel. It lets you review and repair file and folder permissions for every domain on the server.

Location: Admin Panel → Accounts & Plans → Fix Permissions

Overview

The Fix Permissions page shows each domain on the server, its PHP handler (FPM), and its current permission scheme. It provides a one-click way to reset files and directories to the correct ownership and permission modes — without running chown and chmod by hand over SSH.

Incorrect permissions are one of the most common causes of:

• 500 Internal Server Error on websites
• 403 Forbidden when the web server cannot read a file
• Upload failures when PHP cannot write to a directory
• Security incidents when files are world-writable (e.g., 777)

What the Page Shows

| Column | Description |
|---|---|
| Domain | The domain whose permissions will be fixed |
| FPM | The PHP-FPM handler assigned to the domain (blank if not using FPM) |
| Permissions | The permission scheme that will be applied: |
| | 755 Dirs / 644 Files — standard, secure defaults |
| | 777 — world-writable (insecure, rarely needed) |
| | 555 — read-only (used for static or hardened setups) |

> Tip: The 755 Dirs / 644 Files scheme is the correct default for almost every website. Use 777 only temporarily and only when an application explicitly requires it. Use 555 only for directories that must not be modified.

Permission Schemes Explained

755 Dirs / 644 Files (Recommended)

| Type | Mode | Owner | Group | Others |
|---|---|---|---|---|
| Directories | 755 (drwxr-xr-x) | read/write/execute | read/execute | read/execute |
| Files | 644 (-rw-r--r--) | read/write | read | read |

This is the standard, secure configuration. The account owner can read and write; everyone else (including the web server, when it runs as a different user) can only read. Files cannot be executed as programs, which limits damage from uploaded scripts.

777 (World-Writable)

| Type | Mode | Owner | Group | Others |
|---|---|---|---|---|
| Directories | 777 (drwxrwxrwx) | read/write/execute | read/write/execute | read/write/execute |
| Files | 777 (-rwxrwxrwx) | read/write/execute | read/write/execute | read/write/execute |

> Warning: 777 lets any user on the server — including compromised accounts — write to and execute files in these directories. It is a common vector for website defacement and malware. Never use 777 on public directories unless an application absolutely requires it, and revert to 755/644 as soon as possible.

555 (Read-Only)

| Type | Mode | Owner | Group | Others |
|---|---|---|---|---|
| Directories | 555 (dr-xr-xr-x) | read/execute | read/execute | read/execute |
| Files | 555 (-r-xr-xr-x) | read/execute | read/execute | read/execute |

> Note: Use 555 only for directories that must never change — e.g., immutable static assets. Websites that need to write (WordPress uploads, cache directories) will fail with 555.

How to Fix Permissions

Fix a Single Domain

1. Log in to the GoAdmio Admin Panel.
2. Navigate to Accounts & Plans → Fix Permissions.
3. Locate the domain.
4. Select the permission scheme — usually 755 Dirs / 644 Files.
5. Click Fix (or Apply) for that domain.
6. Wait for the operation to complete.

Fix All Domains

If the page offers a bulk action (e.g., Fix All), it will apply the selected scheme to every domain in the list.

> Warning: Running a bulk fix across many domains can take time and briefly impact performance. Prefer fixing specific domains during low-traffic hours.

Via CLI

You can also fix permissions from the shell. GoAdmio provides commands for common operations; for a manual fix, use chown and chmod:

Fix ownership for a single account

```bash

Replace "example" with the account username