Client doesn't work with intermediate SSL certs

[gingerwizard]

This is caused by https://github.com/request/request/issues/3106.

[JasonStoltz]

@gingerwizard Any suggestions on how to resolve this?

[jason-gan]

a workaround I did was to fork the repo, and add "rejectUnauthorized: false" to the request wrapper

[sitaram-dev]

@jason-gan how can I do this please describe the steps.

[JasonStoltz]

I'm not recommending this as a production solution, but if you're struggling with self signed certificates in local or development environments, you can set the following environment variable:

NODE_TLS_REJECT_UNAUTHORIZED="0"

[sitaram-dev]

Ya I did reject unauthorised to false for the time untill I move to cloud services. You r genius 💯

On Mon, 18 Oct, 2021, 7:11 pm Jason Stoltzfus, @.***> wrote:

I'm not recommending this as a production solution, but if you're struggling with self signed certificates in local or development environments, you can set the following environment variable:

NODE_TLS_REJECT_UNAUTHORIZED="0"

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/elastic/app-search-node/issues/25#issuecomment-945780519, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJAFRECDVL4LX55LLAWPLVDUHQP2FANCNFSM4OO6BCQQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.