I imported a certificate "from a certificate authority supported by FileMaker" on FileMaker Server 22.214.171.1240 and everything seemed to check out okay on both server and clients, except now we get the following message when trying any Perform Script on Server on any of the files.
The file “AnyFile.fmp12” could not be opened. Either the host is not available, or the file is not available on that host.
That is, the client is using “AnyFile.fmp12” and trying to execute Perform Script on Server on a script in the very same file. These same Perform Script on Server steps were working before the certificate import.
Also, the same Perform Script on Server on the same file hosted on another server running FMS14 with a certificate "from a certificate authority supported by FileMaker" works fine, but I do not have the option of upgrading or hosting those files on a production 14 server right now.
Anyone know a fix for server 13?
(The main reason we're not upgrading those files in production is that we haven't been able to test ESS and ODBC Import on the Oracle and MSSQL ODBC drivers on Windows Server yet.)
Oh well, I took a chance and just upgraded the server to 14 without being able to test ESS and ODBC Import on the Oracle and MSSQL ODBC drivers on Windows Server on our test server.
Nothing broke, but I forgot to save the certificates; so it looks like I have to create new requests and import the new certificate again.