Can't Create Webhook - Failed Error: self-signed certificate. code: -2

OttoFMS
1

I’m trying to create a webhook but getting the following error when testing the webhook:

{
“error”: “Error: self-signed certificate. code:-2”
}

I checked in the FileMaker Server Admin Console and there is a custom SSL cert installed and using the FileMaker Pro client I get the green padlock in the top right hand corner.

We’re using OttoFMS 4.16.1 which is the latest version.

I’ve run out of things to try at this point - appreciate any suggestions for how to resolve this.

2

Hey Andrew,

If you’re using a custom certificate you should follow the instructions in the custom cert docs for setting up OttoFMS to recognize them. Let me know if you have any issues getting that set up!

-Kyle

3

Thanks Kyle - I’ll pass that on the m clients IT person to action.

Just curious as I’ve never had to do this before with my other OttoFMS deployments. I checked the cert and it is from Sectigo Limited which is the same vendor that I have used for my own certificates. I thought all FMS SSL certs that you install would be classed as a “custom cert” and would have to follow the steps in the page you linked to?

4

I would only expect to need to set up the custom certs if you were using an internal cert authority. If you’re getting a cert from a third party that is well used, it should work. If you can connect to the OttoFMS console using https without a warning (and you didn’t have to trust that certificate authority on your computer), then it also should work.

Is the error only happening when you do webhooks? You may also want to try turning off the DAPI Callout using the env variable. If its only during webhooks then it might be an issue with the server calling back out to its own hostname, which you may not need anyways. Try using that env variable to toggle it off and see if it fixes your issue.

-Kyle