Unable to use gRPC resource with SSL/TLS

Hi Retool Community!

I have an issue in using a gRPC resource.
More specifically, I want to create a gRPC resource to connect my retool app to Camunda 8 SaaS (https://camunda.com/).

On the gRPC resource setup screen, I need to enable SSL/TLS as the connection with Camunda can't be established without SSL/TLS.
I have managed to correctly connect and use the gRPC API on Camunda using Postman (https://www.postman.com/).

So, my question is, how can I set up SSL/TLS on Retool gRPC resource? What files I need to upload to the relevant fields (as shown in the attached screenshot) and how can I create these files? Right now I get the error: "Error: 14 UNAVAILABLE: No connection established"

Thank you in advance,
Spiros Chronas

Hey @spirosc thanks for reporting this. We have filed a bug report as that error is thrown for any issue with certs/configuration on either the client or server side. Have you tried the Verify CA Certificate option? If not, can you try and let me know if you receive the same error?

I'll also update this post as I get any additional information on the internal bug report that we have tracking this.

Hi @joeBumbaca , thank you for your response.
I just tried the Verify CA Certificate option and I still get the same error.
Regarding the OAuth setup, I am sure it is correct as I use the same values on postman and there is no problem there.

I am looking forward to the results of the bug report.
Thanks again.

Hi @joeBumbaca , I was wondering if you got any updates on the bug report.

@spirosc Unfortunately not, the eng team responsible has it in their queue and we'll update this thread as soon as we have any new information to share.

Thanks a lot @joeBumbaca, I am looking for the eng team response.

Hi @joeBumbaca , any news here?
My team considers moving on a paid plan, however my manager is negative because of the bad support experience.

I like Retool platform and the power and flexibility it provides, and I do not want to abandon this project.
Could you please push further to resolve my issue?

Best regards,

@spirosc I bumped the internal ticket for this issue. We'll let you know here as soon as there is any update, thanks.