Helia/remote-pinning-service: Aggregate Err
Repo: https://github.com/ipfs-examples/helia-remote-pinning where: helia-remote-pinning/resolver
Description: After running bootstrapper, pinning-service, publisher, and resolver as sequentially--somehow the resolver is unable to fetch the content associated with the given CID
Possible Causes:
-
Network Connectivity Issues: The resolver cannot connect to the pinning service or publisher nodes.
-
CID Unavailability: The CID provided might not be pinned or accessible.
-
Transport Filters: Misconfigured transport protocols (e.g., lack of WebSocket or WebRTC transports) prevent peer discovery and data transfer.
4.Bootstrapper Issues: Bootstrapper might not have properly registered nodes or is inaccessible.
Fixes: Hence, After Configuring other transports at each node--
transports: [
tcp(),
webSockets(),
webTransport(),
circuitRelayTransport()
],
and Attempting to fetch the block with retries
try {
DOM.output().innerText = ''
const cid = CID.parse(DOM.resolveInput().value ?? '')
DOM.output().innerText += `Resolving ${cid}\n`
for (let attempt = 0; attempt < 3; attempt++) {
try {
const data = await helia.blockstore.get(cid, {
signal: AbortSignal.timeout(5000)
})
DOM.output().innerText += `✅Resolved: ${new TextDecoder().decode(data)}\n `
return
} catch (err) {
DOM.output().innerText += `⚠ Attempt ${attempt + 1} failed: ${err}\n`
}
}
throw new Error('❌Failed to resolve CID after 3 attempts. Refresh & Try again!')
it worked once a while on restart then the same filter-addrs and filter-protocols err persists.
possible root: helia-delegated-routing-v1-http-api/packages/client/src/client.ts line-362
Triage: will investigate