I am running a single Mac OSX Sierra server with FMS 16 and a GoDaddy certificate Standard SSL with 'server.domain.com' set-up.

The certificate is installed correctly according to the Admin Console, and yet if I navigate to the WebDirect, the browser is showing the FMI Default Certificate and is blocking the user. I have gone round in circles for two days so hoping someone can point me in the right direction.

How do I stop the default FMI certificate from being used by WebDirect or FMPro users for that matter?

Did you install the cert using the proper import dialog?  Did you include the intermediate cert?  Did you restart FMS after installing the cert?

Wim - Yes to all. I installed via the Admin Console rather than Terminal commands. I am using a Standard SSL certificate with a sub-domain (which worked before with FMS 14) rather than a wildcard certificate. By upgrading from 14 to 16, it has stopped working. Would this make the difference?

 

Edited July 12, 20196 yr by maverik_uk

If you upgraded but did not follow these exact steps, it might have re-used some old left-over files:

- stop the FMS processes (sudo launchctl stop com.filemaker.fms)

- uninstall FMS14

- rename the leftover "filemaker server" folder in /Library

- reboot

- install FMS16

- import SSL cert

- reboot

 

The step in bold is what most people don't do and it causes issues like the one you're seeing.

Thanks for your help Wim. You're right, I didn't rename the folder... will report back.

Renaming the folder did the job, much appreciated Wim!

Thanks for posting back and closing the loop.  It'll help the next one down the line.