Opened 20 months ago
Closed 20 months ago
#12909 closed Bug report (worksforme)
Server Trust Certificate
| Reported by: | blackdouglas | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | trust certificate | Cc: | |
| Component version: | 3.62.3.1 | Operating system type: | Windows |
| Operating system version: | Windows 10 |
Description
My problem is exactly as described in Bug Report 12199, but I could not find an answer to it. When connecting to the server the certificate shows that it is not trusted and the buttons to override that and force trust are greyed out. If I use OK and move on it does connect.
I have had my ISP check that the certificate is correct, and it is. Sadly it cost me a lot of money to do that. See attachments.
I am using the latest Filezilla (it automatically updates, so that is always the case). This happens on both my machines which are Windows 10 Pro 22H2 and Windows 10 Home 21H2.
Attachments (1)
Change History (2)
by , 20 months ago
| Attachment: | blackdouglas.zip added |
|---|
comment:1 by , 20 months ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The FTPS server on that host, unlike the HTTPS server on that same host, only sends the leaf certificate during the handshake, but not any of the intermediate certificates to the root authority.
This results in the chain being lengthened using intermediate certificates from your system trust store. Unfortunately there are expired certificates in your system trust store for some reason.
Two things you should do:
1) Configure the FTP server to send the intermediate certificates as part of the TLS handshake, just like the HTTPS server on the same machine does.
2) Remove the expired certificates from your system trust store. Check your Windows manual for further instructions.