Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

40.0.0 regression: AutoConnect fails with Azure FTP servers

See original GitHub issue

FTP Server OS: Windows

FTP Server Type: Azure

Client Computer OS: Windows

FluentFTP Version: 40.0.0 - latest (42.0.1)

Framework: .NET 6

AutoConnect doesn’t work with Azure FTP servers. It worked in v39, but v40 broke it. The problem is due to ConnectModule.GetWorkingProfileFromHost returning a partial known profile (no host, credentials, etc.) which causes ConnectModule.LoadProfile to throw an ArgumentException due to profile.Host being null.

Logs :

# AutoConnect()

# AutoDetect(True, False)

# Dispose()
Status:   Disposing FtpClient object...
Unhandled exception. System.ArgumentException: Required parameter is null or blank. (Parameter 'profile.Host')
   at FluentFTP.Client.Modules.ConnectModule.LoadProfile(BaseFtpClient client, FtpProfile profile) in C:\Development\FluentFTP\FluentFTP\Client\Modules\ConnectModule.cs:line 442
   at FluentFTP.Client.BaseClient.BaseFtpClient.LoadProfile(FtpProfile profile) in C:\Development\FluentFTP\FluentFTP\Client\BaseClient\LoadProfile.cs:line 11
   at FluentFTP.Client.Modules.ConnectModule.ConfigureClient(BaseFtpClient client, FtpEncryptionMode encryption, SslProtocols protocol, FtpProfile knownProfile) in C:\Development\FluentFTP\FluentFTP\Client\Modules\ConnectModule.cs:line 314
   at FluentFTP.Client.Modules.ConnectModule.AutoDetectAsync(AsyncFtpClient client, Boolean firstOnly, Boolean cloneConnection, CancellationToken token) in C:\Development\FluentFTP\FluentFTP\Client\Modules\ConnectModule.cs:line 215
   at FluentFTP.AsyncFtpClient.AutoDetect(Boolean firstOnly, Boolean cloneConnection, CancellationToken token) in C:\Development\FluentFTP\FluentFTP\Client\AsyncClient\AutoDetect.cs:line 26
   at FluentFTP.AsyncFtpClient.AutoConnect(CancellationToken token) in C:\Development\FluentFTP\FluentFTP\Client\AsyncClient\AutoConnect.cs:line 19

Issue Analytics

State:
Created 10 months ago
Comments:11

Top GitHub Comments

1reaction

FanDjangocommented, Nov 17, 2022

Thanks. The fix will be in the next release.

1reaction

FanDjangocommented, Nov 16, 2022

Ok, then we’ll clear this up that way and then Robin can wrap it up in the next release. Sleeping now, tomorrow I’ll put together a quick fix as a branch and you will find it when your morning comes up. In the end, a better solution will need to be found, because I will just take back part of the V40 refactor.

Top Results From Across the Web

39.0.1 regression: AutoConnect fails with Azure FTP ...

Using AutoConnect to connect to Azure App Service FTP servers (*.ftp.p.azurewebsites.windows.net) has started failing with 39.0.1 -- times out.

FluentFTP/RELEASES.md at master

Fix: AutoConnect fails with Azure FTP servers due to profile handling ... 40.0.0. Please read the Migration Guide for help migrating to the...

Error while trying to connect to FTP server deployed on my ...

I am getting the following error while trying to connect to FTP server deployed on my Azure VM. Warning: Selected port (18183) is...

FTP connector in Azure fails

In this case, Azure would be the client and we want to pull in data from a third party's FTP server to analyze...

FluentFTP

Using AutoConnect to connect to Azure App Service FTP servers (*.ftp.p.azurewebsites.windows.net) has started failing with 39.0.1 -- times out. Guessing it's ...