FTP Error: 530 User cannot log in, home directory inaccessible Print

  • 293

The File Transfer Protocol (FTP) is a standard network protocol that transfers computer files from one host to another over a TCP-based network. FTP is built on Client-Server Architecture and uses separate connections for control and data.

FTP client connects with the FTP server with a standard username and Password information called FTP Login details. Following is a complete flow of the FTP client-server connection establishment process.

  1. The FTP client sends a DNS query for the domain name to get the FTP server IP address (if you use ftp.domain.com as the FTP hostname).
  2. DNS responds back with the IP address.
  3. FTP client and server complete the three-way handshake process.
  4. The FTP server then sends a 220 response to indicate that the FTP server is ready to accept a login.
  5. The FTP client sends a username through the USER command and a password through the PASS command.
  6. The FTP server verifies the provided login information.
  7. The FTP server will send a welcome message if the provided login details are correct.
  8. The FTP client requests a directory listing.
  9. The FTP server transfers the requested listing.

After specifying the FTP credentials, if the FTP user does not have the required privileges, you may receive the following error message in the FTP client:

Status: Resolving address of ftp.xxxxx.com
Status: Connecting to xxx.xxx.xxx.xx:21...
Status: Connection established, waiting for welcome message...>
Response: 220 Microsoft FTP Service
Command: USER Administrator
Response: 331 Password required for Administrator.
Command: PASS ***************
Response: 530 User cannot log in, home directory inaccessible.
Error: Critical error
Error: Could not connect to server

In most cases, this error occurs only when FTP authorization rules for the default FTP site are not set.

How to fix this error by changing FTP authorization rules?

  1. Log in to the VPS via a Remote Desktop connection as an Administrator User.
    Please refer to How to connect windows VPS using RDP for more details.
  2. Open IIS
    [Start → Administrative Tools → Internet Information Service].
  3. Expand the Sites option from the left pane.

Open IIS Manager and go to Sites

4. You will see a Default FTP Site in the site list; expand this website.

Go to Default FTP Site from the List

5. Now, double-click on the FTP Authorization Rules option from the center pane.

Select FTP Authorization Rules Option

6. From the right pane, click on Add Allow Rule.

Click on Add Allow Rule... Link

7. Select the All Users option, and tick the check box for the Read and Write permission.

8. Click on the OK button to save the changes and Restart Microsoft FTP Services to reflect them.

Select All Users Option and Assign Read, Write Permissions

Follow the below-mentioned steps to restart Microsoft FTP Services –

  1. Open Services [Start → Run → type services.msc and press Enter].
  2. Select Microsoft FTP Service.
  3. Click on the Restart link from the left pane option.

Restart Microsoft FTP Service

 

Now, try to log in again to the FTP account.
If everything goes fine, you should not receive any error while connecting to your FTP account.

The FTP accounts should be created with appropriate permissions to avoid such errors.

We have linked the article to set up the FTP account from IIS.

 

→ Looking for any other help with FTP?
Don't forget to check out our Complete FTP Guide.

→ Are you facing an FTP error at FileZilla?
Please refer to the Fix FTP error for more details. 

→ Are you facing an FTP with too many connection errors?
Please refer to Fix FTP for too many clients error for more details.

→ Looking for any other help with FTP?
Don't forget to check out our Complete FTP Guide.

→ Are you facing an FTP error at Filezilla?
Please refer to Fix FTP error for more details. 



Was this answer helpful?

« Back

chat