Closed Henry-Hiles closed 1 year ago
Have just seen that AWS is having issues and I believe that is where api.astroicon.dev/v1 is hosted so given time, should hopefully resolve as I've just had the same error message (https://digital.com/who-is-hosting-this/#search=api.astroicon.dev)
Oh, thanks.
That page won't load for me but downdetector also suggests that AWS is down. Just gotta wait i suppose, thanks :smile:
I have the same problem and was on the point of a crisis.
same issue very thanks
After a few meetings, I ran an Astro build and am no longer receiving errors. That doesn't mean it's back up for good but it's an improvement.
As stated above, the error is due to the upstream AWS outage. I will keep this open for visibility until the issue is resolved.
In the future v1 release, everything should be local for builds so this won't happen again.
Down again?
TypeError: fetch failed
at Object.fetch (node:internal/deps/undici/undici:11522:11)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at runNextTicks (node:internal/process/task_queues:64:3)
at listOnTimeout (node:internal/timers:540:9)
at process.processTimers (node:internal/timers:514:7)
at async request (/xyz/node_modules/astro-icon/lib/resolver.ts:15:17) {
cause: Error [ERR_SOCKET_CONNECTION_TIMEOUT]: Socket connection timeout
at new NodeError (node:internal/errors:399:5)
at internalConnectMultiple (node:net:1099:20)
at Timeout.internalConnectMultipleTimeout (node:net:1638:3)
at listOnTimeout (node:internal/timers:575:11)
at process.processTimers (node:internal/timers:514:7) {
code: 'ERR_SOCKET_CONNECTION_TIMEOUT'
}
}
I currently cannot build because of this error:
After looking through the source code, I believe this is because https://api.astroicon.dev/v1 is down, as I get a 500 server error when I try to load it. I would appreciate if this could be fixed, as I can't build my website currently. Thanks.