Bobcares

FTP error 530 user cannot log in home directory inaccessible – Quick Fix

by | Jan 2, 2020

Are you receiving FTP error 530 user cannot log in home directory inaccessible? We can help you fix it.

While trying to connect to the FTP server we may run into this error message. In most cases, this error occurs only when FTP authorization rules for default FTP site are not set.

At Bobcares, we often get requests from our customers regarding FTP errors as part of our Server Management Services.

Today, let’s get into the details on how our Support Engineers fix the FTP error for our customers.

 

Why FTP shows 530 user cannot log in home directory inaccessible error?

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

When connecting locally from Windows Server via FTP using a subscription FTP user, the operation fails with the below error.

FTP error 530 user cannot log in home directory inaccessible

Depending on the FTP client the error message appear as “Failed to retrieve directory listing” or “Home directory inaccessible” error as well. There might be a few reasons for running into this error.

Now, it’s time to see the reasons that cause 530 FTP anonymous messages.

 

Top causes for “530 User cannot log in, home directory inaccessible”

From our experience in managing servers, we often see customers experiencing problems like “530 User cannot log in, home directory inaccessible”.

Let’s check the common reasons one by one and see how our Support Engineers fix it.

 

1. Authorization rules

In most cases, this error occurs only when FTP authorization rules for default FTP site are not set. For that, we set the Authorization rule by the following the below steps.

a. Initially, we log in to the VPS via Remote Desktop connection as an Administrator user.

b. Then we open IIS and expand Sites option from left pane.

c. After that we select the default FTP site in site list and click the FTP Authorization Rules option.

d. From the right pane, we click on Add Allow Rule.

e. Then we select the option of All Users and tick the check box of Read and Write permission.

f. Finally, we click on Ok button to save the changes and Restart Microsoft FTP Services to reflect them.

 

2. The user is not able to access to the home directory.

This is the another root cause of the error. We make sure to select the directory that the users can access by selecting IIS > FTP site > FTP User Isolation and select the FTP root directory.

 

3. NTFS permissions

We make sure that the FTP users have permissions on the physical folder. For that, we right click the folder > Properties > Security tab and check the user permissions.

Even after making the changes, sometimes to reflect the changes we need to restart Microsoft FTP Services. Here is the steps to restart the FTP service.

1. Open Services and select the service named Microsoft FTP Service.

2. Then click on Restart link from the left pane option.

After that we log in to the FTP account. If everything is fine, then no error will appear while connecting to the FTP account.

 

[Need assistance in fixing the error? – We will fix it for you.]

 

Conclusion

To be more accurate, “530 User cannot log in, home directory inaccessible” error happens due to various reasons like incorrect rules, permissions and many more. Today, we saw common causes for the error and also saw how our Support Engineers fixed it.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF