DirectAdmin File Manager and File Permissions Guide

DirectAdmin’s File Manager is the browser-based interface for managing every file in your account. Upload, edit, move, set permissions — most operations you’d otherwise need FTP or SSH for, all in a web UI. The permissions side trips up most newcomers; once you understand the three-digit chmod codes, every “403 Forbidden” or “500 Internal Server Error” becomes diagnosable in seconds. This guide covers the practical workflow plus the permissions reference.

Opening File Manager

DirectAdmin → System Info & Files → File Manager. You land in your home directory (/home/youruser/). The folder you’ll spend most time in is domains/yourdomain.com/public_html/ — that’s where the website files live.

Layout: left tree pane shows folder structure; right pane shows contents of the selected folder; top toolbar has actions (upload, new file, new folder, etc.).

Uploading files

• Single or few files: click Upload Files in the toolbar, choose files, upload.
• Many files / a whole site: zip locally, upload the zip, then right-click and Extract on the server. Much faster than uploading individually.
• Drag and drop: drag files from your computer onto the File Manager window — most modern DA versions support this.

Upload size limit: typically 32-128 MB depending on plan. For larger files (database dumps, large media), use FTP/SFTP — no upload size limit there.

Editing files

Right-click a text-based file → Edit. Editor opens in a new window with syntax highlighting for common formats (PHP, HTML, CSS, JS).

For binary files (images, archives, executables), no inline editing — download, edit locally, re-upload.

Tip: before editing any file you’re not sure about, click Copy first. Edit the copy; if you break it, the original is intact. After confirming the edit works, delete the copy.

Compressing and extracting

• Compress files: select files → right-click → Compress → choose format (.tar.gz, .zip, .tar) → archive created in current folder.
• Extract: right-click an archive → Extract → files appear in current folder.

Use ZIP for compatibility with Windows users; tar.gz for Linux-native workflows. Either format works fine on DA.

Showing hidden files

Files starting with a dot (.htaccess, .env) are hidden by default. Enable display: File Manager options or settings → Show hidden files. Toggle on, refresh.

.htaccess is frequently needed for Apache configuration, redirects, mod_rewrite rules — make sure hidden files are visible whenever you’re working on URL behavior.

Understanding file permissions (chmod)

Every file and folder has three “permission groups”:

• Owner — usually your DA account.
• Group — usually your DA account’s group.
• World / Others — everyone else (the web server, other users).

Each group has three possible permissions:

• Read (r) — can view the file’s contents or list folder contents.
• Write (w) — can modify the file or add/remove files in the folder.
• Execute (x) — can run the file (or, for folders, can enter it).

Each permission has a numeric value:

• Read = 4
• Write = 2
• Execute = 1

Add them up for each group: 4+2+1 = 7 (all permissions), 4+2 = 6 (read+write), 4+1 = 5 (read+execute), 4 = read-only.

The “chmod number” is three digits, one per group:

Rules of thumb:

• Files: 644.
• Folders: 755.
• Sensitive config files (wp-config.php, .env): 600.
• Never 666 or 777 — these are world-writable and are a common malware vector.

Setting permissions in File Manager

1. Right-click file/folder → Set Permissions (or sometimes labeled “Change Permissions” / “chmod”).
2. Either enter a numeric chmod (e.g. 644) or tick checkboxes for read/write/execute per group.
3. For folders, optionally check Recursive to apply to all contents.
4. Save.

Bulk-fixing a messed-up permission state:

• Right-click public_html → Set Permissions → 755 → check Recursive + “Apply to directories only” → Save.
• Right-click public_html → Set Permissions → 644 → check Recursive + “Apply to files only” → Save.

This restores the standard 644/755 pattern across everything. After this, individually re-set 600 on sensitive files (wp-config.php).

Common permission problems

“403 Forbidden” on a page. Folder permissions too restrictive. Folder needs 755 so the web server can enter and read. public_html itself can be 750 or 755 — never less.

“500 Internal Server Error” on PHP page. Often a permissions issue with the PHP file or the folder it’s in. Try 644 on the file, 755 on the folder.

“WordPress can’t update / can’t install plugin.” WordPress needs write permission on wp-content/. Verify it’s owned by your account (it should be by default on DA) and 755.

“.htaccess not being read.” Check it’s not chmodded to 000 or something unreachable. 644 is standard.

“Lost ownership of files after restore.” Sometimes happens with old backups. Open a support ticket — we can fix ownership with one server-side command.

File Manager limitations and FTP alternative

File Manager is fine for occasional work but tedious for heavy file operations. For larger workflows:

• FTP/SFTP client (FileZilla, Cyberduck, WinSCP) — much faster for many files. Use SFTP (port 22) for security, or FTPS (FTP over TLS).
• FTP accounts: DirectAdmin → FTP Management → Create FTP Account. Use the FTP account for SFTP login as well.

For developers needing version control: SSH access (if enabled on your plan) gives you git, command-line file operations, and full power. But for content-management and occasional fixes, File Manager handles the job.

What’s next

• SSL setup including .htaccess: DirectAdmin SSL guide.
• Backup files before risky changes: DirectAdmin backups.
• Database edits via phpMyAdmin: DirectAdmin databases.

The two key patterns: 644 for files, 755 for folders. Master those plus the File Manager basics and 95% of day-to-day site management is covered without ever opening an FTP client.