does filemaker pro server 13 works on windows 10

However, it is important to me that the connection is properly encrypted because the information is sensitive. I can reassure them and persuade them to manually override the warnings. So could anyone help me out here? If I get it wrong, can I roll back simply by removing the certificates? Does the fact that I have a warning and a struck through https prefix mean that the connection is not encrypted? How can I check?Ĭan anyone run me through which certificates I need to import to the Filemaker CStore and what they need to be named? For instance, I am pretty sure that the Certbot privkey.pem file needs to be renamed PrivateKey.pem When I tried to upload the other certificates I got into problems and was locked out of the site! At present I am still using the Filemaker supplied certificate.

I don’t really mind this because I am only sharing the database with a few select individuals and I can reassure them and persuade them to manually override the warnings. I am aware that Filemaker does not recognise Certbot as an authorised CA and as such comes up with warnings (just as it does with its own development certificate). I recently managed to obtain certificates for my MacMini running Filemaker Server 15.0.3 within my LAN using a dyndns Host Name.

Does filemaker pro server 13 works on windows 10