FetchError: request failed, reason: connect ETIMEDOUT 99.86.230.68:443

[VasiliiD (Vasilii Dementev)]

Hi! Nuxt static generate. Every time we've got some errors during page generation process. Any ideas how to solve it?

|12:45:04.651|FetchError: request to https://secret.cdn.prismic.io/api/v2?access_token=MC5ZSVFDZFJFQUFDVUFMZ21F.I--_ve-_ve-_vS7vv70877-9I--_vUzvv70A77-977-9LALvv70va--_vSEOIO-_vXbvv70X77-977-9MBk failed, reason: connect ETIMEDOUT 99.86.230.68:443|
|---|---|
|12:45:04.652|    at ClientRequest.<anonymous> (/opt/buildhome/repo/node_modules/node-fetch/lib/index.js:1461:11)|
|12:45:04.652|    at ClientRequest.emit (events.js:376:20)|
|12:45:04.652|    at TLSSocket.socketErrorListener (_http_client.js:475:9)|
|12:45:04.652|    at TLSSocket.emit (events.js:376:20)|
|12:45:04.652|    at emitErrorNT (internal/streams/destroy.js:106:8)|
|12:45:04.652|    at emitErrorCloseNT (internal/streams/destroy.js:74:3)|
|12:45:04.653|    at processTicksAndRejections (internal/process/task_queues.js:82:21)|

[Fares]

Hi Vasilii,

May I know if the build fails every time? And do you get those timeouts only when building locally?
We already have an issue reported in our tracker that is similar to this.

In order to update this issue with your details, may I know this repository that you are using? Is it "secret.cdn.prismic.io"? otherwise, you can send me a direct message with your repository name.

For your reference, those threads can be related to this:

https://community.prismic.io/search?q=FetchError:%20request%20failed,%20reason:%20connect%20ETIMEDOUT

Looking forward to your response,
Fares