Unable to connect to a resource with a self signed certificate

💬 Queries and Resources
1

I have added the CA to the docker.env file according to the docs

image
image1270×807 50.4 KB

But it still errors out.
image
image1222×162 7.92 KB

I bashed into the api container and see that the volume is mounted and the cert is there. There is no db-connector section on the yaml file ( not sure if this was deprecated or something ). If I curl from that bash prompt, it is giving me this message:
image
image762×113 2.42 KB

How do I get the Retool to use my self-signed CA?
Adding that CA to the resource settings doesn't work either.

2

I also tried using the --cacert option with curl to specify the root cert, but get the same error. I have added this same certificate to my windows machine and can access https just fine.

3

I also face this erroe. Anyone help me.

4

Hey @DavidBusch! Thanks for reaching out.

It seems odd that directly specifying the certificate in a curl request doesn't work. :thinking: That doesn't sound like a Retool issue. You've tried the same thing from your host machine without any issues?

Setting aside the above for a moment, the first thing I notice is that the error you shared seems to have been thrown from within a workflow. This is important because all such requests are handled by the workflows-backend container, which needs to be configured separately.

image
image916×292 25 KB

image
image968×294 27.9 KB

Note that the DB_CONNECTOR service has been rolled into both the api and workflows-backend containers, instead of running separately.

Before adding your cert to the workflows-backend container, you can try making a request to your resource from within an app just to see if there are any issues with that configuration.

Hopefully this back-and-forth will be helpful to you, as well, @hulazphila!