Odyssey: Lift-Off II Resolvers - Querying live data - returning server error

Help
,
1

While querying the live data, I get the below error in my local host. Please help.
ERROR: ETIMEDOUT 54.208.186.182:443

And the same error while running the query from query explorer:
{
“errors”: [
{
“message”: “request to failed, reason: connect ETIMEDOUT 54.208.186.182:443”,
“locations”: [
{
“line”: 2,
“column”: 3
}
],
“path”: [
“tracksForHome”
],
“extensions”: {
“code”: “INTERNAL_SERVER_ERROR”,
“exception”: {
“message”: “request to https://odyssey-lift-off-rest-api.herokuapp.com/tracks failed, reason: connect ETIMEDOUT 54.208.186.182:443”,
“type”: “system”,
“errno”: “ETIMEDOUT”,
“code”: “ETIMEDOUT”,
“stacktrace”: [
“FetchError: request to https://odyssey-lift-off-rest-api.herokuapp.com/tracks failed, reason: connect ETIMEDOUT 54.208.186.182:443”,
" at ClientRequest. (C:\Users\apollo\odyssey-lift-off-part2\server\node_modules\apollo-datasource-rest\node_modules\node-fetch\lib\index.js:1491:11)“,
" at ClientRequest.emit (events.js:315:20)”,
" at TLSSocket.socketErrorListener (_http_client.js:469:9)“,
" at TLSSocket.emit (events.js:315:20)”,
" at emitErrorNT (internal/streams/destroy.js:106:8)“,
" at emitErrorCloseNT (internal/streams/destroy.js:74:3)”,
" at processTicksAndRejections (internal/process/task_queues.js:80:21)"
]
}
}
}
],
“data”: null
}

2

Hello @AmdapR,
It’s possible that the datasource (rest api) was unresponsive and timed-out at the time you executed the requests.
I took a look at the rest server we use for this demo and couldn’t see any downtime though, and working well at the moment. Could you retry and see if you get the same error? if that is the case then we’ll look at other potential sources of error.
Best,
Raph

3

You are right. I don’t think its an issue with the rest server. I retried and still get the same error.

4

got it thanks for retrying, could you share your repo to bring additional context?

5

I had this issue. It was because of the proxy settings done in my network. I disconnected from my network and tried the same using my mobile hotspot, it worked.

6

I am having the same error right now. The server was running fine last time I used it, did not change any setting, but all of sudden got this error.