Installing OttoFMS on Windows Server 2022 with FileMaker Server v21.1.1.40 I receive an error upon attemping to activate the license key “License not accepted. Reason “missing””.
I do see in the ‘otto-info’ log file the entry “Error checking license self-signed certificate in certificate chain” everytime I attempt to apply the license key.
The FileMaker server is running under a wildcard SSL cert issued by DigiCert and upon checking our firewall/antivirus nothing is blocking access to any sites/services.
Welcome to the community! I suspect that OttoFMS is getting upset from the Digicert certificate. If you install that root certificate on the server and add it to the NODE_EXTRA_CA_CERTS env variable, does that fix it? See docs for how to set this up here.
I did add the root certificate to the server and to the env variable as requested but see no change after restarting the service. I still receive the ‘Error checking license self-signed certificate in certificate chain’ error in the log file.
If you turn on debug logging (you can do this from the OttoFMS config settings) and restart the server, you should see a set of log lines in the otto-debug.log file during startup that walk through the cert loading process. Could you send me the otto-debug.log for this server after running a restart?
I think I misunderstood the original support request. I’ve reapplied the root certificate setting and can now use OttoFMS. Thank you very much! I look forwarding to using this amazing product.