chris_cross
New Pleskian
Dear colleagues,
I experienced an issue using an external backup repository on Plesk 12.0.18 machines using ftps. The ftp server uses ftps (explicit) connections.
Plesk 11.5 works fine (and ordinary ftp client like Filezilla as well), Plesk 12 throws the following error when trying to add the server via the web interface:
Unencrypted connections will work. Plesk 11.5 machines (with the same settings) will work.
I've analyzed the problem and got so far:
The backup manager tries to connect using "regular" transfer method + ssl, not ftp-ssl explicit.
Is there a chance to force Plesk using explicit ftpes connections? Or is there another work around?
Some additional infos about the (ftp) server:
The ftp server is running ProFTP 1.3.4d, uses port 2000 for the control port and has a port range (2001 - 2100) for the passive connections.
I tried to add the server using the address field of the gui IP:2000 and checkboxed "passive mode" and "ftps".
I experienced an issue using an external backup repository on Plesk 12.0.18 machines using ftps. The ftp server uses ftps (explicit) connections.
Plesk 11.5 works fine (and ordinary ftp client like Filezilla as well), Plesk 12 throws the following error when trying to add the server via the web interface:
Code:
Curl error: Login denied
Unencrypted connections will work. Plesk 11.5 machines (with the same settings) will work.
I've analyzed the problem and got so far:
The backup manager tries to connect using "regular" transfer method + ssl, not ftp-ssl explicit.
Is there a chance to force Plesk using explicit ftpes connections? Or is there another work around?
Some additional infos about the (ftp) server:
The ftp server is running ProFTP 1.3.4d, uses port 2000 for the control port and has a port range (2001 - 2100) for the passive connections.
I tried to add the server using the address field of the gui IP:2000 and checkboxed "passive mode" and "ftps".