ruvnet/ruflo · error

[IPFS] Gateway ${gateway} failed: ${errorMsg}

Error message

[IPFS] Gateway ${gateway} failed: ${errorMsg}

What it means

Log warning in resolveIPNS: a single public IPNS gateway attempt failed (network or HTTP error); the loop continues to the next gateway in the list before giving up on the name.

Source

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

        if (response.ok) {
          // Extract CID from the final URL after redirects
          const finalUrl = response.url;
          const cidMatch = finalUrl.match(/\/ipfs\/([a-zA-Z0-9]+)/);
          if (cidMatch) {
            cid = cidMatch[1];
          }
        }
      }

      if (cid) {
        const latency = Date.now() - startTime;
        console.log(`[IPFS] Resolved ${ipnsName} -> ${cid} via ${gateway} (${latency}ms)`);
        return cid;
      }
    } catch (error) {
      const errorMsg = error instanceof Error ? error.message : String(error);
      console.warn(`[IPFS] Gateway ${gateway} failed: ${errorMsg}`);
      continue;
    }
  }

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

/**
 * Fetch content from IPFS by CID with fallback across multiple gateways
 *
 * @param cid - Content Identifier
 * @param preferredGateway - Optional preferred gateway to try first
 * @returns Parsed JSON content or null if fetch fails
 */
export async function fetchFromIPFS<T>(
  cid: string,
  preferredGateway?: string

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Check the gateway error in the log; the client tries the next configured gateway automatically, so persistent failures mean all gateways should be checked or replaced.

When it happens

Trigger: Thrown at v3/@claude-flow/cli/src/transfer/ipfs/client.ts:117 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/595e6cded9dacfc9. Report an issue: GitHub.