Kubo's content is unfetchable, despite node being reachable #9986
Labels
kind/bug
A bug in existing code (including security flaws)
need/author-input
Needs input from the original author
need/triage
Needs initial labeling and prioritization
Checklist
Installation method
third-party binary
Version
Config
Description
Closest relation (though not quite since that's about dials, which seem to succeed in this case): #5800
I've been noticing with Kubo V0.20 that step 4 of the diagnosis tool at https://pl-diagnose.on.fleek.co/#/diagnose/access-content is always failing (Error:
The request failed context deadline exceeded
), and that https://cid.contact is always unable to find my CIDs despite usingautoclient
routing. Besides that, the other 3 steps succeed completely fine, which makes the diagnosis tool and all IPFS gateways I've tried failing to fetch anything from me pretty strange.I've tried various configs involving Accelerated DHT, Optimised providing, adjusting grace period and water level, removing QUIC (both v1 and not) from
Swarm
, but nothing's resolved it. As an extra detail, I'm behind a router, so CircuitV2 is involved (though working multiaddresses are discovered within 30 seconds ofipfs daemon
, so it shouldn't be causing issues).Possible relation to probe-lab/network-measurements#49 (?).
The text was updated successfully, but these errors were encountered: