You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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--
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--
and Attempting to fetch the block with retries
it worked once a while on restart then the same
filter-addrs
andfilter-protocols
err persists.possible root: helia-delegated-routing-v1-http-api/packages/client/src/client.ts
line-362
The text was updated successfully, but these errors were encountered: