Originally Posted by beetlejuice
just tried this: https://byet.host/
free ftp hosting. So it is not only nfo i guess....
(Peer certificate cannot be authenticated with known CA certificates).
Closest match I found for a valid hostname towards them is "ftp.byethost7.com".
This one is exactly like NFO, "self signed certificate" && "expired".
CA stands for Certificate Authority, and the error output above means that the certificate isn't certified by a proper certificate authority that your system trusts.
If they were doing the exact same towards their public website https://www.nfoservers.com
- then you would be seeing warning in your browser, similar to this one:
Originally Posted by ThatOneGuy
I've submitted a support ticket to NFO on the issue in hopes they will look into it, as that may affect a quite a number of users. Thanks for the information. If they are unwilling to update their certificates, I will have to go the alternate route of disabling the verification.
With certificate authorities like for example https://letsencrypt.org
- there is no reasons for NFO and others not to use their certificates for such services as FTP servers.
There are already a billion (... well, many!) scripts available so far, that can automate the certificate renewals with LE.
Any decent FTP(S) client should also warn you just like the SM plugin does.