When you generate a self-signed certificate at "Server->Settings->SSL Certificate Manager" in WingFTP. Wing FTP will automatically generate three files in your directory, with extension of ".crt", ".key" and ".csr" respectively.
The ".key" file is your private key file.
frhey wrote:Hello
Is a sollution for this problem founded?
I have the same problem: "invalid SSL certifacte file"
I have a digitally signed certificate from a CA in the format ".pem". It's only 1 file.
I put the pem-file into certificate path AND into privat key path, like written in the help.
But the result ist: "invalid SSL certifacte file"
I changed the pem-file manually into a crt-file like written in the knowledge base:
viewtopic.php?f=5&t=54
But the result ist: "invalid SSL certifacte file"
In other applications, f.e. IIS, ISA, I can import and use my pem-file without problems.
My pem-file is importet in certificates.msc, too. And works fine (inclusive path to Intermediate CA and Root CA).
Could you help me, please?
best regards
Frank
frhey wrote:Hello.
I have no "self-signed" certificate, it is an "official" digitally signed certificate from a CA.
The CSR-file was not made by wingFTP.
It was made by Microsoft Internet Information Server and used first in another (old) FTP-server-product. There it works fine. But I changed now to wingFTP, it is the better software :-) The old FTP-server is completely deinstalled. Only wingFTP is running on the server. The server hosts https://file.mydomain.de/ with the old ftp-software, and now with wingFTP, too. The certificate ist made for https://file.mydomain.de/.
I tried to create a self-signed certificate in wingFTP for file.mydomain.de and changed the crt-file with my pem.
Or create a new crt-file with the content of the pem-file.
But the result is always: "invalid SSL certifacte file"
best regards
Frank
Users browsing this forum: No registered users and 2 guests