• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Backup Manager Remote Storage via FTPS

RaSch

New Pleskian
Server operating system version
Ubuntu 26.04.1 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.82 Update #3
...still not possible to select passive mode :(
 
Well, the problem is neither using unsafe ftp in passive mode nor using ftps with ports open in firewall.
The problem is in activating passive mode for ftps, resulting in "Transport error: unable to list directory: Curl error: (28) Timeout was reached: The last FTP request: PASV: The last FTP response: 227 Entering Passive Mode".
Though it may not have the same reason (?) as Bug-ID PPPM-15485 the outcome seems to be pretty similar.
 
Hey @RaSch,

quick thought on this: The 227 Entering Passive Mode followed by a timeout usually means the passive handshake itself worked fine, but the actual data connection afterwards gets blocked. So "passive mode can't be activated" isn't quite what's happening, Plesk gets the 227, then tries to open the data channel and that's where it hangs.

A few things worth checking:
  1. Passive port range on the FTP server side. Opening port 21 alone isn't enough. The passive data ports need to be reachable too. Default range is usually 49152–65535, but check whatever your FTP daemon is actually configured for. If the target sits behind NAT, the daemon also needs pasv_address set to the external IP, otherwise it hands back an internal address the client can't reach.
  2. Test it manually from the Plesk box so we know whether it's Plesk or the network:
Code:
curl -v --ftp-pasv -u USERNAME 'ftp://TARGET-IP/'

If that works but Plesk still times out, it's likely something in the bundled component (there have been FTPS regressions in some 18.0.8x builds). If it also times out, it's firewall/NAT, plain and simple.

  1. Worth trying in /usr/local/psa/admin/conf/panel.ini:
Code:
[pmm]
ftpAllowPassiveIpChange = 1

Mostly meant for NAT/IP-change scenarios, but it can shake loose passive-mode negotiation weirdness.

On PPPM-15485: If manual curl works and Plesk doesn't, it's probably a separate issue and worth a fresh report. If manual curl also fails, then it's config and not the bug.

Regards
Tessa
 
Back
Top