Fixing "FTP 421 Home Directory Not Available – Aborting" by Ensuring Correct Permissions (Beginner Guide)

Contents: What Does This Error Mean? Step 1: Check If the Home Directory Exists Step 2: Create the Home Directory (If Missing) Step 3: Verify FTP Server Configuration Step 4: Restart Services and Test Step 5: Check SELinux or AppArmor Step 6: Check Disk Space Final Testing Summary Final Thoughts

Fix FTP 421 error by ensuring correct permissions

What Does This Error Mean?

The "421 Home Directory Not Available – Aborting" error occurs when a user tries to log in to an FTP server but cannot access their home directory. The problem is usually due to incorrect permissions, ownership issues, or configuration errors.

This guide will explain in simple steps how to diagnose and fix this error by ensuring correct permissions. Whether you are using vsftpd, ProFTPD, or Pure-FTPd, these solutions will work.

Step 1: Check If the Home Directory Exists

Before adjusting permissions, first confirm that the home directory exists.

Find the User's Home Directory

Each user has a home directory stored in the /etc/passwd file. Run this command to check:

grep username /etc/passwd

(Replace username with the actual FTP username.)

Example Output

username:x:1001:1001::/home/username:/bin/bash

The 6th field (/home/username) is the user's home directory.
The 7th field (/bin/bash) is the default shell.

Verify If the Directory Exists

Run this command:

ls -ld /home/username

Expected Output (If Exists)

drwx------ 2 username username 4096 Feb 10 12:00 /home/username

If you see:

ls: cannot access '/home/username': No such file or directory

The home directory is missing – you must create it (see Step 2).

Step 2: Create the Home Directory (If Missing)

If the home directory does not exist, create it manually.

Create the Directory

sudo mkdir -p /home/username

The -p flag ensures the directory is created without errors.

Assign the Correct Owner

Set ownership so the user has full access:

sudo chown username:username /home/username

Set the Correct Permissions

To prevent login failures, set the correct permissions:

sudo chmod 750 /home/username

750 Permissions Explained:

7 (Owner - username): Read, Write, Execute
5 (Group - username): Read, Execute
0 (Others): No access

Why 750?

Some FTP servers (e.g., vsftpd with chroot_local_user=YES) reject home directories with write permissions for others.

Note: If using ProFTPD, use 755 instead:

sudo chmod 755 /home/username

Step 3: Verify FTP Server Configuration

Each FTP server has different settings. You must ensure it allows users to access their home directory.

For vsftpd Users

If you're using vsftpd, open the configuration file:

sudo nano /etc/vsftpd.conf

Make sure these settings exist:

chroot_local_user=YES allow_writeable_chroot=YES user_sub_token=$USER local_root=/home/$USER

Save the file (CTRL + X, then Y, then ENTER) and restart vsftpd:

sudo systemctl restart vsftpd

For ProFTPD Users

If you're using ProFTPD, edit the configuration file:

sudo nano /etc/proftpd/proftpd.conf

Ensure this is set:

DefaultRoot ~

Save and restart ProFTPD:

sudo systemctl restart proftpd

For Pure-FTPd Users

If you're using Pure-FTPd, check your home directory settings:

sudo nano /etc/pure-ftpd/pure-ftpd.conf

Ensure this setting is enabled:

ChrootEveryone yes

Save and restart Pure-FTPd:

sudo systemctl restart pure-ftpd

Step 4: Restart Services and Test

After making changes, restart all services to apply the updates.

Restart FTP and SSH Services

sudo systemctl restart vsftpd sudo systemctl restart sshd

Test FTP Login

Try logging into your FTP server:

ftp yourserver.com

If login is successful, you will see:

230 Login successful.

If you still see the error, continue with Step 5.

Step 5: Check SELinux or AppArmor (For CentOS/RHEL Users)

If you are on CentOS or RHEL and the issue persists, SELinux might be blocking FTP access.

Check SELinux Status

sestatus

If SELinux is enabled, fix FTP access:

sudo setsebool -P ftp_home_dir 1 sudo restorecon -Rv /home/username

Step 6: Check Disk Space

If your server runs out of disk space, FTP users may not be able to access their home directories.

Check Disk Space

df -h

If /home is full, clean up space:

sudo rm -rf /home/username/tmp/*

Final Testing

Verify Home Directory Exists and Has Correct Permissions

ls -ld /home/username

Correct Output Example:

drwxr-x--- 2 username username 4096 Feb 10 12:00 /home/username

Test FTP Login

Try connecting again:

ftp yourserver.com

If Successful:

230 Login successful.

If Still Failing:

Check logs for additional errors:

tail -f /var/log/auth.log

Summary: Fixing "421 Home Directory Not Available - Aborting"

Step	Action
1	Check if the home directory exists (`ls -ld /home/username`)
2	If missing, recreate it (`mkdir -p /home/username`)
3	Set correct ownership (`chown username:username /home/username`)
4	Set correct permissions (`chmod 750 /home/username`)
5	Ensure FTP server settings allow access (modify `/etc/vsftpd.conf`, `/etc/proftpd/proftpd.conf`, or `/etc/pure-ftpd.conf`)
6	Restart services (`systemctl restart vsftpd` or `proftpd` or `pure-ftpd`)
7	Check SELinux/AppArmor if using CentOS/RHEL (`setsebool -P ftp_home_dir 1`)
8	Verify disk space is not full (`df -h`)
9	Test FTP login (`ftp yourserver.com`)

Final Thoughts

By following this guide, even beginners can troubleshoot and fix "421 Home Directory Not Available – Aborting" by ensuring correct permissions.

Fixing "FTP 421 Home Directory Not Available – Aborting" by Ensuring Correct Permissions (Beginner Guide)

What Does This Error Mean?

Step 1: Check If the Home Directory Exists

Find the User's Home Directory

Example Output

Verify If the Directory Exists

Expected Output (If Exists)

Step 2: Create the Home Directory (If Missing)

Create the Directory

Assign the Correct Owner

Set the Correct Permissions

750 Permissions Explained:

Why 750?

Step 3: Verify FTP Server Configuration

For vsftpd Users

For ProFTPD Users

For Pure-FTPd Users

Step 4: Restart Services and Test

Restart FTP and SSH Services

Test FTP Login

Step 5: Check SELinux or AppArmor (For CentOS/RHEL Users)

Check SELinux Status

Step 6: Check Disk Space

Check Disk Space

Final Testing

Verify Home Directory Exists and Has Correct Permissions

Correct Output Example:

Test FTP Login

Summary: Fixing "421 Home Directory Not Available - Aborting"

Final Thoughts

Hosting

Cloud Solution

For You

VDS

Website Builders

Our services

Client Area

Select Currency

Fixing "FTP 421 Home Directory Not Available – Aborting" by Ensuring Correct Permissions (Beginner Guide)

What Does This Error Mean?

Step 1: Check If the Home Directory Exists

Find the User's Home Directory

Example Output

Verify If the Directory Exists

Expected Output (If Exists)

Step 2: Create the Home Directory (If Missing)

Create the Directory

Assign the Correct Owner

Set the Correct Permissions

750 Permissions Explained:

Why 750?

Step 3: Verify FTP Server Configuration

For vsftpd Users

For ProFTPD Users

For Pure-FTPd Users

Step 4: Restart Services and Test

Restart FTP and SSH Services

Test FTP Login

Step 5: Check SELinux or AppArmor (For CentOS/RHEL Users)

Check SELinux Status

Step 6: Check Disk Space

Check Disk Space

Final Testing

Verify Home Directory Exists and Has Correct Permissions

Correct Output Example:

Test FTP Login

Summary: Fixing "421 Home Directory Not Available - Aborting"

Final Thoughts

Hosting

Cloud Solution

For You

VDS

Website Builders

Our services

Client Area

Выберите валюту