Skip to content
This repository has been archived by the owner on Feb 3, 2024. It is now read-only.

Unhandled Rejection at: Promise Frequent crashes with errors like this #71

Open
xperisa opened this issue Sep 18, 2022 · 2 comments
Open

Comments

@xperisa
Copy link

xperisa commented Sep 18, 2022

Unhandled Rejection at: Promise {
FetchError: request to https://gql.twitch.tv/integrity failed, reason: connect ETIMEDOUT 199.232.18.167:443
at ClientRequest. (/usr/src/app/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:481:9)
at TLSSocket.emit (node:events:513: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) {
message: 'request to https://gql.twitch.tv/integrity failed, reason: connect ETIMEDOUT 199.232.18.167:443',
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
[stack]: 'FetchError: request to https://gql.twitch.tv/integrity failed, reason: connect ETIMEDOUT 199.232.18.167:443\n' +
' at ClientRequest. (/usr/src/app/node_modules/node-fetch/lib/index.js:1491:11)\n' +
' at ClientRequest.emit (node:events:513:28)\n' +
' at TLSSocket.socketErrorListener (node:_http_client:481:9)\n' +
' at TLSSocket.emit (node:events:513:28)\n' +
' at emitErrorNT (node:internal/streams/destroy:157:8)\n' +
' at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n' +
' at processTicksAndRejections (node:internal/process/task_queues:83:21)',
name: 'FetchError'
}
}
Unhandled Rejection Reason: FetchError: request to https://gql.twitch.tv/integrity failed, reason: connect ETIMEDOUT 199.232.18.167:443

@dawinaj
Copy link

dawinaj commented Sep 18, 2022

I am getting the same, so now Im almost certain its not a fault on my side.
image
image

@xperisa
Copy link
Author

xperisa commented Sep 18, 2022

I am getting the same, so now Im almost certain its not a fault on my side. image image

Many people have encountered this problem

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants