FTP Upload task can't connecting (FTPS).

[SteveSteglitz]

I try to upload some files to FTPS. The Provider is IONOS (1&1).
The login data are:

• Server / Host: accessXXXXX.webspace-data.io
• Protokoll: FTPS
• Port: 990

I can login in Filezilla, but the FTP Upload task in my pipline yml file failed.

Starting: FtpUpload
Task : FTP upload
Description : Upload files using FTP
Version : 2.157.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/ftp-upload
connecting to: accessXXXXX.webspace-data.io:990
[debug]Connected to 212.227.192.101:990
[error]Error: Timeout (control socket)
[debug]Processed: vso[task.issue type=error;]Error: Timeout (control socket)
[debug]task result: Failed
[error]Ftp Upload failed
[debug]Processed: vso[task.issue type=error;]Ftp Upload failed
[debug]Processed: vso[task.complete result=Failed;]Ftp Upload failed
[section]Finishing: FtpUpload

My taksk in der yml file:
..
task: FtpUpload@2
inputs:
credentialsOption: 'inputs'
serverUrl: 'ftps://accessXXXXX.webspace-data.io:990'
username: 'XXXXX'
password: 'XXXXX'
#rootDirectory: '/'
filePatterns: '**'
remoteDirectory: '/'
clean: false
cleanContents: false
preservePaths: false
trustSSL: true
...

My provider support only ftps access.

A test with a other FTP (only ftp) worked correct.

I don't know what is my error?

[bdgit]

The same issue found today. Used classic definition.
FTPS with and without PASV
Server: ftps://server:990
Credentials Used
Works with Filezilla Passive FTPS

[leoniDEV]

I have the same issue, also I with Ionos provider, it seems that the V1 of the task resolve the issue

[vbreuss]

I also have the same issue (with 1&1 Ionos), but also using V1 of the task didn't help.

[ghost]

The same issue with v2, v1 does nothing

[mmarseu]

I have a hunch this is because the FTPUpload task is suppressing the underlying basic-ftp package's feature to connect using implicit TLS negotiation.
I've had the same issue and was only able to solve it because my FTP server also supports explicit TLS. You might want to check that, too. I suppose most modern servers would support explicit TLS on port 21.

Basically, the basic-ftp client has an option named "secure", which can be either "true" (explicit TLS), "false" (no TLS) or "implicit" (implicit TLS). The FTPUpload task won't use the "implicit" option, though. It will either set it to "true", if your server URL starts with "ftps://" or false, otherwise.

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[jokoast]

Still not working in 2022, same issue

[mchaari]

any idea please ?

[mmarseu]

any idea please ?

This issue is closed. You can't expect the situation to change by itself. Either create a new issue or fix it yourself and submit a PR.

If you're opting for the latter, see my comment above for my idea what the problem might be.

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days