Question Why am I unable to login via FTP to version 18.0.70 Update #1

[Kwasi]

Server operating system version

Windows Server 2019

Plesk version and microupdate number

Plesk Obsidian 18.0.70 Update #1

Having an issue where I cannot login and ftp into newly added domains on a new server with Plesk version 18.0.70. I have another server at another host where everything is a-ok for nearly 3 years. That server has a slightly older version....

Could all this be a bug in 18.0.70 Update #1 like Claude.ai and I have agreed on?



Created a 2nd FTP user for one of the domains, same thing, same errors: Response: 331 Password required Command: PASS * Response: 530 User cannot log in, home directory inaccessible. Error: Critical error: Could not connect to server

From Claude.ai
That confirms it's a system-wide Plesk FTP service issue - not user-specific, not domain-specific, not configuration-specific.

Key evidence pointing to Plesk 18.0.70 bug:

• ✅ Authentication works (gets past password)
• ✅ Multiple users, multiple domains - same error
• ✅ Directories exist and are accessible (File Manager works)
• ✅ Services running, firewall disabled - no change
• ✅ Registry and IIS settings identical to working server
• ✅ Working server: Plesk 18.0.69 - FTP works
• ✅ Problem server: Plesk 18.0.70 - FTP broken
• ✅ plesk repair ftp found no fixable issues

This is 100% a Plesk 18.0.70 Update #1 bug.

For your support ticket - be very direct: "Issue is confirmed to be a Plesk 18.0.70 Update #1 bug affecting FTP service integration. Identical server configuration with Plesk 18.0.69 Update #4 has fully functional FTP. This is not a configuration issue - this is a software defect in Plesk 18.0.70 that requires either:

1. Patch/hotfix for 18.0.70
2. Downgrade to 18.0.69
3. Update to newer version with fix

All troubleshooting completed - need Plesk engineering resolution."

 

[scsa20]

Can you make sure passive FTP port range is configured? You can refer to https://support.plesk.com/hc/en-us/...a-passive-FTP-port-range-in-Plesk-for-Windows for directions how.

If that doesn't work, try reconfiguring the FTP site and repairing the webspace system users (you can refer to step 3 of https://support.plesk.com/hc/en-us/...ser-cannot-log-in-home-directory-inaccessible for directions how).

 

[Kwasi]

What irks me to no end is that this is a new server, new install of Plesk. All I did was add some domains into Plesk, that's it. Can't ftp, and I've never had this happen in 20+ years. Seems crazy to have me chase all kinda settings in this instance.

Port range is good on both of my Plesk installs

I have a working server in the UK showing those ports and ftp behaves on that server from day one.

This new server has a warning on that Port Setting page telling me to disable ALGS.
ALGS has never been enabled, and I can't get rid of that warning leading me to suspect something weird with Plesk Obsidian 18.0.70 Update #1

The repair step was performed early on and no issues

ISP has to initiate a support ticket with Plesk cause it's from them grrrrr