ruvnet/ruflo · error

[IPFS] Fetch failed for ${cid} on all gateways

Error message

[IPFS] Fetch failed for ${cid} on all gateways

What it means

Log warning in fetchFromIPFS: the CID could not be fetched from any configured gateway (each attempt timed out, was rate-limited, or errored); the function gives up and signals failure to the caller.

Source

Thrown at v3/@claude-flow/cli/src/transfer/ipfs/client.ts:177

        const latency = Date.now() - startTime;
        console.log(`[IPFS] Fetched ${cid} from ${gateway} (${latency}ms)`);
        return data;
      }

      // Handle specific error codes
      if (response.status === 504) {
        console.warn(`[IPFS] Gateway timeout on ${gateway}, trying next...`);
      } else if (response.status === 429) {
        console.warn(`[IPFS] Rate limited on ${gateway}, trying next...`);
      }
    } catch (error) {
      const errorMsg = error instanceof Error ? error.message : String(error);
      console.warn(`[IPFS] Gateway ${gateway} failed: ${errorMsg}`);
      continue;
    }
  }

  console.warn(`[IPFS] Fetch failed for ${cid} on all gateways`);
  return null;
}

/**
 * Fetch with full result metadata
 */
export async function fetchFromIPFSWithMetadata<T>(
  cid: string,
  preferredGateway?: string
): Promise<FetchResult<T> | null> {
  if (!isValidCID(cid)) return null;
  const gateways = preferredGateway
    ? [preferredGateway, ...IPFS_GATEWAYS.filter(g => g !== preferredGateway)]
    : IPFS_GATEWAYS;

  for (const gateway of gateways) {
    try {
      const startTime = Date.now();

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Verify the CID exists and is reachable on the IPFS network; pin it on a reliable node or add more gateways.

When it happens

Trigger: Thrown at v3/@claude-flow/cli/src/transfer/ipfs/client.ts:177 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18). Data as JSON: /api/errors/d1a532c8baaeff1f. Report an issue: GitHub.