Request to https://[prismicAPIURL]?[access_token] failed, reason: connect ETIMEDOUT [IP]

Developing with Prismic
1

There are some ETIMEDOUT errors for a few requests of PrismicAPI.
Could you provide some suggestions or knowledge on this issue?
FYI, I'm facing this only for few requests of PrismicAPI.

Thanks & Regards

3

Hi Srini,

Thank you for contributing to Prismic community, I will try to debug this issue with you.

Can you please share with us the full error you are getting including the exact timestamp in UTC in order to look it up in our systems?

Also, is a persistent problem or you get some random timeouts during the day (some request pass others timeout)?

Looking forward to reply,
Fares

4

Hi, Fares
Thank you for your quick response

These are random timeouts during the day. In my case more or less 100 errors a day.

Please find the complete error,
FetchError: request to https://[API URL]?access_token=[accessTokean] failed, reason: connect ETIMEDOUT [IP]
at ClientRequest. (/var/app/current/node_modules/isomorphic-fetch/node_modules/node-fetch/index.js:133:11)
at ClientRequest.emit (events.js:310:20)
at ClientRequest.wrapped (/var/app/current/node_modules/newrelic/lib/transaction/tracer/index.js:188:22)
at ClientRequest.wrappedRequestEmit (/var/app/current/node_modules/newrelic/lib/instrumentation/core/http-outbound.js:153:26)
at TLSSocket.socketErrorListener (_http_client.js:426:9)
at TLSSocket.emit (events.js:310:20)
at Shim.applySegment (/var/app/current/node_modules/newrelic/lib/shim/shim.js:1387:20)
at TLSSocket.wrapper [as emit] (/var/app/current/node_modules/newrelic/lib/shim/shim.js:2022:17)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)

Thanks & Regards

5

Hi Srini,

Thanks for the extra info, can you also send me the name of your repository in a direct message in order to look for those errors in our internal logs and debug the issue?

6

I couldn’t find any logs related to this issue, so I will create an issue in our issue tracker and we will reach back to you as soon as possible

10

Hi Srini,

Are you still having this issue?

11

This issue has been closed due to inactivity.