-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Bootstrapper 0 and 1 repeatedly failing with 504s #1694
Comments
@haadcode are you able to confirm this has been resolved? |
@alanshaw - what I see now from https://vitriol.co is another long string of errors:
So no, it doesn't seems resolved (but the timeouts are gone) |
I retried and now all seems working. I will retry in a couple of hours to confirm. |
Nope, node 0 is still closing connections and node 1 is still 504 timing out.
... for ~100 lines |
@ipfs/infrastructure team, is anyone looking into this? |
I just loaded https://vitriol.co and watched IPFS startup. Closing this issue as it appears to be resolved but please reopen is the problem persists. |
Type:
Bug
Severity:
High
Description:
Repeated 504 Timeout errors from preload nodes 0 and 1:
index.min.js:1 GET https://node1.preload.ipfs.io/api/v0/refs?r=true&arg=QmSTYia3dXbtFTFZCEYnBFyNXpmED34xYtjkwxocTo1Q2d 504 (Gateway Time-out)
index.min.js:1 GET https://node0.preload.ipfs.io/api/v0/refs?r=true&arg=QmSTYia3dXbtFTFZCEYnBFyNXpmED34xYtjkwxocTo1Q2d 504 (Gateway Time-out)
Steps to reproduce the error:
The text was updated successfully, but these errors were encountered: