-
-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get implicit FTPS connection on linux #550
Labels
Comments
Is it this : #347 Can you try Explicit TLS/SSL |
Also try AutoDetect/AutoConnect methods on FtpClient and see if it finds a working profile. |
When you respond I will reopen this. |
@genyx what was your fix in the end? We are experiencing the same issue. |
@tonykaralis as mentioned above, i use CoreFtp |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FTP OS: Debian 10 client, Windows Server
FTP Server: FileZilla Server (managed by other company)
Computer OS: Debian 10
FluentFTP Version: 32.2.2 via nuget
I wrote a program on my windows machine and it works fine. However, as it got deployed on a debian 10 server (same dotnet core version 3.1.102) the execution of Connect() fails by timeout. The last line of the
# Connect()
log below stays for (length of "ConnectTimeout") and nothing more happens.Can confirm that the server should have responded the correct message. The server is configured to strictly only allow connections on the specific ports (990-993) and only to my IP.
The connection is established, i can tell because i am able to download the actual SSL certificate and chain when i define a custom
ValidateCertificate
eventhandler. So it is not a firewall problem.Also i tried the library CoreFtp which works exactly as expected. But sadly is not that "fluent" to use like this one.
I tried reproducing it:
My suggestion is that it has to do with connections via implicit FTPS, the port negotiation or the SSL certification, but since there is no further log, i can't tell. Maybe you can.
It may still be a problem with the servers firewall, but since this is a third partys network infrastructure i can't tell. I have added the filezilla server configuration that i have from the network admin below.
Client config:
Logs :
The text was updated successfully, but these errors were encountered: