Hello,
After installing an SSL certificate in FMS16, Filemaker Pro can not verify the identity of my server "s1.childnology.com:5003". 

Get(ConnectionState)  returning 2 but my FMS name is "s1.childnology.com" same as the SSL.

I opened the Inbound and Outbound TCP ports 80, 443, 2399, 5003, 16000 in Windows Server 2016 firewall.

If I use FM Web Direct I get a green padlock and no warning message appears

I have checked this and the TCP port 5003 is indeed accessible..... at this point I do not know what else to verify or try.

Please help

 

Edited October 27, 20178 yr by Gilbert13

It could be that you either used a certificate that is not supported.

The webserver support many more certificate types than the DB engine.

Another reason could be that you didn’t include a intermediate certificate or you have used a wrong one.

 I haven’t installed a GoDaddy myself, so I am not familiar with their process.

Hi Claus,

I just checked my godaddy certificate and it is indeed compatible with FMS16  "Go Daddy - Standard SSL"
I didn’t include a intermediate certificate, try following the steps in this link https://support.filemaker.com/s/answerview?language=en_US&anum=14176

Concatenate the root and intermediate certificates into a single file it was impossible, Go Daddy just provide a Security Certificate and a IIS_intermediates.P7B file

I do not concatenate the intermediate cert. There is a separate field in the FMS admin console when you import the certificate to specify the intermediate.

Download your certificate as other!!!     Great video solved my problem