![](/img/trans.png)
[英]AuthenticateAsServer - The remote certificate is invalid according to the validation procedure
[英]FluentFTP: The remote certificate is invalid according to the validation procedure
當我嘗試連接到我的 FTP 服務器以使用 FluentFTP 上傳文件時,我得到以下信息:
根據驗證程序,遠程證書無效。
然而 FileZilla 運行良好,沒有錯誤或警告。
我是不是做錯了什么,如果它實際上是服務器的問題,我怎么能忽略這個錯誤
這是我的代碼:
var credentials = new NetworkCredential(Username, Password);
FtpClient client = new FtpClient(Host, credentials)
{
Port = Port,
EncryptionMode = FtpEncryptionMode.Explicit
};
client.DataConnectionEncryption = true;
client.Connect();
var result = client.UploadFileAsync(FilePathName, RemotePathName, AllowOverwrite ? FtpExists.Overwrite : FtpExists.Skip, CreateRemoteDirectory, token).GetAwaiter().GetResult();
client.Disconnect();
我還嘗試添加事件client.ValidateCertificate += Client_ValidateCertificate;
private static void Client_ValidateCertificate(FtpClient control, FtpSslValidationEventArgs e)
{
e.PolicyErrors = SslPolicyErrors.None;
}
但我無法讓它工作,我仍然遇到同樣的錯誤。
這是 FileZilla 的輸出:
Status: Selected port usually in use by a different protocol.
Status: Resolving address of xxxxxxxxxxxxxxxxxxxxxx
Status: Connecting to xxx.xxx.xxx.xxx:xx...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing of "xxxxxxxxxxxxx"...
Status: Directory listing of "xxxxxxxxxxxxx" successful
Client_ValidateCertificate
需要像這樣手動接受證書:
private static void Client_ValidateCertificate(FtpClient control, FtpSslValidationEventArgs e)
{
e.Accept = true;
}
然而,盲目地接受任何證書確實是一個壞主意。 我最終做了這樣的事情:
private void Client_ValidateCertificate(FtpClient control, FtpSslValidationEventArgs e)
{
if (e.PolicyErrors == SslPolicyErrors.None || e.Certificate.GetRawCertDataString() == TrustedRawCertData)
{
e.Accept = true;
}
else
{
throw new Exception($"{e.PolicyErrors}{Environment.NewLine}{GetCertificateDetails(e.Certificate)}");
}
}
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.