This could be the case, if you used the first released version of the tool, which did not concatenate the certificate with intermediate certificates.
I wrote a personal email all, who downloaded the tool, to let you know that there is an updated version released.
Also, you can find instructions to how to fix, if you already renewed with the first version.
Yes.. I did get your email and used version 1.3.0
Thanks for the zippy reply btw.
Also, I'm getting no error on web direct connections. I believe you stated that the issue with your previous version had FMP working fine, but webdirect was not.
Try to open the certificate file in a text edit app.
You should see at least 2-3 blocks here, representing intermediate certificates as well as your custom certificate...
There was an issue with remote containers via WebDirect, if intermediate certificates was not concatenated with the certificate.
This can also be an issue for FMP/A or FMGO.
Also, you should try to restart your machine, since there could be something cached.
This is the best help, I can provide here.
If nothing of this help, I suggest you contact FMI support and please tell back to this thread, what results you get and what solutions you find with them.
Thanks Claus... we're in production, so I'll have to try again in the wee hours.
I will say... your tool was immensely helpful!
The CRT actually only has one block of text.
Did I miss a step?
That is your issue.
A manuel fix:
1) Open the .crt file in a text editor
2) Open the ca-bundle file, that you also received from Comodo in a text editor
3) Copy the content of the ca-bundle file
4) Insert this content in the .crt file above the current content.
5) Save the file. (just cmd+s)
Now you should have a certificate file, that you can import into the admin console, but it now has the intermediate certificates as well into a chain of trust.
Now I get this:
This certificate does not match the private key [/opt/FileMaker/FileMaker Server/CStore/serverKey.pem]. Error: 20621 (Key doesn't match certificate)
I am sorry you have so much trouble here and I feel a little guilty, that I do not have time enough to really help you through.
The error you get, suggest that either the server has a new private key (different from the one you used to create the CSR file with) or you selected the wrong private key during import, or you did make some kind of mistake, when you concatenated the certificate and the ca-bundle file.
I would re-check the certificate file to see that it looks correct (the blocks look a-like), make sure that you are using the korrekt private key and then try to re-import again.
If you still see errors, I would suggest that you do the process all over. (sorry)
You can get Comodo to reissue your certificate, so you don't have to pay again.
No problems Claus... I appreciate all of your assistance.
I'll run it through the process again.