• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved FTP User of new domain doesn't works

Atomus

New Pleskian
Hi,

I have a VPS server with Plesk Onyx 17.8 on Windows Server 2012 R2, with 73 websites created and running.

When I added domain number 68, I did it, but I had one problem: that domain, pointed ip mail server to other IP server than website server. That is: mail server point to xxx.xxx.xxx.xxx and website server pointed to yyy.yyy.yyy.yyy. Until that, all was correct. I created that website, and one user for FTP access. Then, like I made with other websites in the same server, I configured FTP application with IP Server instead of Name Server (ftp.midomainname.com), the user, and password I had used. Never worked.

From that moment, I created up to 5 websites more (all pointing email and website servers to same server), and all of them are running fine, except for FTP access. None of them, are running.

When try to connect through FTP, I receive following error:

STATUS:> [19/06/2018 18:38:10] Getting listing "/httpdocs"...
STATUS:> [19/06/2018 18:38:10] Connecting to FTP server... xxx.xxx.xxx.xxx:21 (ip = xxx.xxx.xxx.xxx)...
STATUS:> [19/06/2018 18:38:10] Socket connected. Waiting for welcome message...
[19/06/2018 18:38:10] 220 Microsoft FTP Service
STATUS:> [19/06/2018 18:38:10] Connected. Authenticating...
COMMAND:> [19/06/2018 18:38:10] USER myftpuser
[19/06/2018 18:38:10] 331 Password required
COMMAND:> [19/06/2018 18:38:10] PASS *****
[19/06/2018 18:38:10] 530 User cannot log in, home directory inaccessible.
ERROR:> [19/06/2018 18:38:10] Not logged in.
STATUS:> [19/06/2018 18:38:12] Connection closed.

I have checked all permisions for thar user, and they are the same I have for ftp users that works.

Any ideas?
 
Hello, it is useful to enable debug on your FTP website and then check why exactly error 530 occurred.
Please take a look at this article: How to enable FTP debug logging in IIS
Then try to reproduce the problem again and look at C:\inetpub\vhosts\Servers\<FTPSITEID>\logs\FTPSVC<FTPSITEID>
There should be more details in the row with 530 error.
 
Hello,

I've found the solution for this problem.

After check ftp log, like PavelV said, I found that the problem was the following:

530 User cannot log in, home directory inaccessible

Reviewing Plesk Support and Plesk Docs, I have done the following to solve this issue:

1) Open IIS
2) Under IIS > Sites > <IP_address> > Basic Settings, see the Physical Path
3) Open Regedit
4) Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PLESK\PSA Config\Config
5) Check that Physical Path on IIS, and FTP_ROOT_D value on Registry are the same.
6) In my case was not the same path, and I updated value in Registry chain FTP_ROOT_D
7) Open DOS Command Prompt
8) Execute: plesk repair ftp
In my case, this command detect one error because new physical path doesn't exists. I answered Yes to create it.

After a couple of minutes, execution finished, and I tested my FTP connections.

They runs fine.
 
Back
Top