Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Help wanted]: Getting error : unable to verify the first certificate #130

Open
paritporeddiwar opened this issue Nov 9, 2021 · 3 comments

Comments

@paritporeddiwar
Copy link

Hi Guys,

We are using Axios library and code is in Node JS. When we hit this endpoint,
https://ta-reporting.bt.siemens.com/api/v1/HORIZON/launch/import
we are getting following error
(node:50) UnhandledPromiseRejectionWarning: Error: unable to verify the first certificate

UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
(node:50) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Till yesterday it was working fine.

@paritporeddiwar paritporeddiwar changed the title [Help Required]: Getting error : unable to verify the first certificate [Help wanted]: Getting error : unable to verify the first certificate Nov 9, 2021
@AmsterGet
Copy link
Member

Hello @paritporeddiwar !
Does this problem still exist?
Seems that the problem associated with self-signed certificates. You can find the details and possible solutions in this issue.

@AmsterGet AmsterGet transferred this issue from reportportal/agent-js-cypress Feb 21, 2022
@AmsterGet
Copy link
Member

Hello @paritporeddiwar !
Is this issue still actual for you?

@AmsterGet
Copy link
Member

Hello @paritporeddiwar !
Is this issue still actual?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants