Here’s the important bit:
It suggests that the certificate for api.monday.com is invalid.
Go to the URL in a browser and check that you see a valid certificate. I do.
To momentarily get around this problem, try this:
npm config set strict-ssl false
and test again to see if you get the expected result.
After testing, always revert back to
npm config set strict-ssl true
I’m guessing that your setup somehow proxies api.monday.com and does something weird.
Hi David,
Thank you for the reply.
What “URL” you referring to ? when I open “api.monday.com” it just redirect me to my monday homepage of my account
By the way, I am using ngrok as the tunnel. Is that related to the issue ?
Thanks
@Roy i just went to https://api.monday.com/v2 without logging into Monday. Then checked the certificate.
I’ve the same problem too. Didn’t modify anything on the code
I’m behind proxy, so i could ask to the it service department if they’ve upgraded something
Uncaught FetchError FetchError
at processPromiseRejections (internal/process/promises:265:13)
at processTicksAndRejections (internal/process/task_queues:97:32)
promises:265
Debugger attached.
C:\\Repo\\monday\\node_modules\\node-fetch\\lib\\index.js:1501
reject(new FetchError(request to ${request.url} failed, reason: ${err.message}
, ‘system’, err));
^
Waiting for the debugger to disconnect…
FetchError: request to https://api.monday.com/v2 failed, reason: unable to verify the first certificate
at ClientRequest. (C:\\Repo\\monday\\node_modules\\node-fetch\\lib\\index.js:1501:11)
at ClientRequest.emit (node:events:520:28)
at TLSSocket.socketErrorListener (node:_http_client:442:9)
at TLSSocket.emit (node:events:520:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
type: ‘system’,
errno: ‘UNABLE_TO_VERIFY_LEAF_SIGNATURE’,
code: ‘UNABLE_TO_VERIFY_LEAF_SIGNATURE’
}
Process exited with code 1
that’s my error.