This repository was archived by the owner on Mar 19, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
Error: SELF_SIGNED_CERT_IN_CHAIN undefined: Getting metadata from plugin failed with error: request to https://www.googleapis.com/oauth2/v4/token failed #393
Description
Looks like issues that started at 12:30 CT about a self signed cert in chain when interacting with cloud datastore. This was a cron job that runs every minute and has been running for months.
If the support paths suggested above still do not result in a resolution, please provide the following details.
Environment details
- OS: ubuntu 16
- Node.js version: 12.15.0
- npm version: 6.13.4
google-gaxversion: 1.15.1
Steps to reproduce
{ Error: SELF_SIGNED_CERT_IN_CHAIN undefined: Getting metadata from plugin failed with error: request to https://www.googleapis.com/oauth2/v4/token failed, reason: self signed certificate in certificate chain
at Object.callErrorFromStatus (/snow-ticket-worker-4602/workspace/snow-ticket-worker-ci/master/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/call.js:30:26)
at Http2CallStream.call.on (/snow-ticket-worker-4602/workspace/snow-ticket-worker-ci/master/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/client.js:96:33)
at Http2CallStream.emit (events.js:203:15)
at process.nextTick (/snow-ticket-worker-4602/workspace/snow-ticket-worker-ci/master/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/call-stream.js:100:22)
at process._tickCallback (internal/process/next_tick.js:61:11)
code: 'SELF_SIGNED_CERT_IN_CHAIN',
details:
'Getting metadata from plugin failed with error: request to https://www.googleapis.com/oauth2/v4/token failed, reason: self signed certificate in certificate chain',
metadata: Metadata { internalRepr: Map {}, options: {} },
note:
'Exception occurred in retry method that was not classified as transient' }
`11
Metadata
Metadata
Assignees
Labels
No labels
Activity
shaunwarman commentedon Aug 19, 2020
No idea still, but assuming some bad CI job or hidden proxy
chore(deps): update dependency sinon to v13 (#393)