Recently upgraded to Version: 2025.1.2.79 and my Download Tool configurations no longer work to communicate with our SFTP, whether download (GET / FTP) or upload (PUT).
I receive an error on the first attempted transfer (need to do 24 total) --
Previously, I used only the "Connection" tab username/password (username is an email address, so contains an @ symbol) and passed a field for Basic > URL formatted: sftp://ftp.hostedftp.com/foldername/subfolder/filename.csv
I haven't changed the way the URL is formatted at all, but feel like DCM is 🥲
No variation of this base URL (ftp.hostedftp.com) yields success now that DCM is enforced. I've tried it with https:// and sftp://
If I try to configure the DCM base URL = ftp.hostedftp.com, I can't proceed due to error "Validation failed due to the invalid input format." AKA it seems to require a prefix with ://
I've also tried variations of the base URL where / is included on the end, and / not included, instead just having / as the first character of the path field now that "values from the field will be appended to the base URL specified in the connection"
I've tried running with "Resolve on Payload" checked, and unchecked.
I've tried with "Encode URL Text" checked, and unchecked.
Headers tab> I have no Headers / values from these fields configured
Payload tab > HTTP Action = PUT, "Take Query String/Body from Field" = Blob
Connections tab >
No matter what I do, the workflow errors on the first URL with the same message: "URL using bad/illegal format"
I'm able to connect with no issue in Filezilla. First connect prompts me to trust the SSL key so I select the checkbox “Always trust this host, add this key to the cache”.
The hostedFTP service we connect to has good info out on what connection params to use: https://help.hostedftp.com/help-2/connecting-with-an-ftp-client-3/
Has anyone else had SFTP upload/download workflows they've used for years break since 2025.1.2.79 requiring DCM?
I am sure you must have tried it but see if anything from below helps.
Setup the DCM for sftp://ftp.hostedftp.com alone, then add the remaining path (/foldername/subfolder/filename.csv) in a text input tool. This path will get appended to the base URL coming from DCM.
user name with @ can also give this error. Try encoding your credentials in dcm directly. Alternatively, you can also try using %40 as replacement of @ in your user email. Though, try with DCM encoding of email and password.