There are a few certificates listed on the FileMaker support web pages as tested for FM Server 17 and i am trying GoDaddy one as it is the cheapest one.

On 2 servers i tried so far, after more hustle then expected, i managed to install the certificates and now i got an ORANGE lock on both stating that the certificate is there but can not be trusted. Why is this happening? Could it be that they listed the certificate that is not really working well with FM Server?

I have been installing GeoTrust certificate on previous servers and never had these issues...

On the top of this, now it will not open my files and it is describing them as unencrypted even though they are encrypted.

Is there a good way to approach this in order to understand what is going on with FileMaker 17, certificates and encryption on the files, why is it not working smoothly.

I installed everything by the book and it simply does not work as expected.

 

Edited August 9, 20187 yr by milanm

I have a similar issue and today I finally traced it to the fact that even though I specify the domain to the server if I add the file as a favorite it will try to use the "server.local" path and show the orange lock. If, instead, I start to open the file, specify the domain, then right click on the file before opening it I can add it as a favorite and it holds the domain.

Here i found a good article from Wim Decorte and Steven H. Blackwell that covers the orange lock scenarios pretty well, it helped me resolve the issue:

https://support.filemaker.com/servlet/fileField?entityId=ka10H000000bwfr&field=Public_File_1__Body__s