I tried saving them as primary.cer and secondary.cer. Double-clicked each of them and the Keychain installed them.
Thanks. When you then checked the cert from a web browser did it show as valid and no longer generate warnings to customers after you did that? Did you have the Mac OS Server app installed?
Thawte has a checker for their certs at https://ssltools.thawte.com/checker/views/certCheck.jsp
I had the Server app installed originally from when I was running it with FMP12 and IWP but uninstalled it at the advice of FMP support. I did get my cert to work but oddly only by removing the serverCustom.pem file after running the import command for the cert. Leaving that file in blocked all access to my database through both WebDirect and FMP Clients. Removing that file allowed access again and kept my cert intact despite the fact that its removal should have caused it to revert to the FMI cert. Tech support couldn't make sense of it and neither could I but at the end it works.
Great post on instructions. They are the same steps for a Thawte cert as well. FMP needs to update their guidance on installation along those lines.
You are ABSOLUTELY CORRECT SIR!
I thought I had it all figured out when I saw that Green Address Bar at the top. Guess what, all my databases are gone. Did what you did, drag my serverCustom.pem out of the CStore folder, restarted the server and voila!
Hear that FMP Team?
I wish I could say this is the end of it. I just had to repeat the process to install a new cert using all the previously discussed steps that worked for me last time and this time around no luck. The cert installed and predictably the customServer.pem caused all access to my database to be blocked. However, this time when I removed the customServer.pem file my databases came back but it also removed my Thawte cert and replaced it with the default FMI cert.
I'm now two hours in on trying to resolve this any way I can and FMP tech support has no idea. I'm pissed because I had it actually working but had to redo it because of the files I had to share with FMP tech support and now it will not work again.
My advice is if you need to use SSL with your own cert so your users are not getting scared away by browser warning messages then FMP13 is not an option until FMP get's its act together to fix this most basic of functions which worked fine in FMPS12 with IWP.
How I wish I've seen this before I removed my cert for testing another server. I'm not going to install my cert on my FMS 13 until Friday, so hopefully FileMaker would have an update by then. Good luck man.
Removing customServer.pem worked for me when I had similar problems, but with:
- Windows Server 2012
- public cert from GoDaddy
- no other intermediary certs has been installed
After server restart everything looks OK so far.
Thank you lads!