The "failed to create" was a permissions error. Somehow CSTORE was set to read only for fmsadmin group.
I finally got it working by regenerating a new key, resubmitting to godaddy, getting a new cert and importing it. THEN restarting. Not just the FMS Service, but the whole bleeping box. Is it me, or should servers only need to be recycled in case of crisis or crash?
I didn't see anywhere in the fms13_help or Gettting_Started docs that a reboot of the server itself is required to apply changes to certificates. Must've been in the same paragraph that tells us FMS understands SHA-1. OK, testiness and snarkiness over now. But I can't be only one frustrated by the documentation or lack thereof.
Thank you for the post.
I’m glad you were able to solve the issue.
For others who may encounter this thread, the fmsadmin group is read-only by default. Instead of changing the groups permissions, running the command as sudo would produce the same result.
“I didn't see anywhere in the fms13_help or Gettting_Started docs that a reboot of the server itself is required to apply changes to certificates.”
We are always trying to improve our documentation; however, page 71 of the FileMaker Server 13 Help guide in reference to “Require secure connections” states:
“Note: If you change this setting, you must restart the Database Server again for the change to take effect. See Starting or stopping FileMaker Server components.”