• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

530 User cannot log in, home directory inaccessible.

Joe Storm

New Pleskian
Hi,

I am very new to Plesk and Windows Server.

All users created in Plesk control panel CAN access FTP and connect to the domain folders.
In IIS Sites>192.168.xx.xx (Default Ftp Site) which is binding to port 21, the FTP Physical path is pointing to "C:\Inetpub\vhosts\Servers\6" and the localuser folders is only those users created through Plesk.

But the problem is those users created in Windows Server (Server Manager > Local Users and Groups) and the default user (before installing Plesk) cannot connect to FTP with the error message :

"530 User cannot log in, home directory inaccessible."

I am trying to understand how Plesk FTP affects the default MSFTP users (those not created under Plesk). Why only users created out of Plesk cannot access FTP? Has it anything to do with Active Directory? I read somewhere Plesk restrict users of AD, etc...

What is the cause and how do I fix this problem?
 
1) Check whether you are using active directory or not. If so please use FTP username as hostname\ftp_username (open cmd and run hostname to get the hostname of the server)
2) Checked the number of characters in your hostname, if it is more than 15 characters. Change the hostname to one it has less than 15 char

3) Check the physical path for FTP sites in IIS > Web sites > IP address > Basic settings > Physical Path. This should be part of FTP_ROOT_D from the previous step.

4) Verify that the system user folder (FTP user) of a subscription exists in the FTP site path (see Cause). For example, C:\inetpub\vhosts\Servers\8\localuser\system_user\domain.tld\. If it does not, find a folder which contains this folder, for example C:\inetpub\vhosts\Servers\7\, and change the Physical Path accordingly.


Also check the issue with the kb http://kb.odin.com/en/124094
 
Back
Top