abhigyanpatwari/GitNexus · error

Registry returned ${response.status}

Error message

Registry returned ${response.status}

What it means

fetchLatest throws `Registry returned ${status}` for any non-2xx, non-3xx response from the update registry (the body is cancelled first). The message interpolates the actual HTTP status code, so the rendered error tells you exactly what the registry answered — 404, 403, 500, etc.

Source

Thrown at gitnexus/src/core/update-check.ts:195

  let url = sanitizedHttpUrl(packageUrl);
  for (let redirects = 0; ; redirects += 1) {
    const response = await fetch(url.toString(), {
      method: 'GET',
      redirect: 'manual',
      headers: { accept: 'application/json' },
      signal: AbortSignal.timeout(FETCH_TIMEOUT_MS),
    });
    if (response.status >= 300 && response.status < 400) {
      if (redirects >= MAX_REDIRECTS) throw new Error('Too many registry redirects');
      const location = response.headers.get('location');
      await response.body?.cancel().catch(() => {});
      if (!location) throw new Error('Registry redirect missing location');
      url = sanitizedHttpUrl(location, url.toString());
      continue;
    }
    if (!response.ok) {
      await response.body?.cancel().catch(() => {});
      throw new Error(`Registry returned ${response.status}`);
    }
    const parsed = JSON.parse(await readResponseBody(response)) as {
      version?: unknown;
      'dist-tags'?: { latest?: unknown };
    };
    const latest =
      (typeof parsed.version === 'string' ? parsed.version : undefined) ??
      (typeof parsed['dist-tags']?.latest === 'string' ? parsed['dist-tags'].latest : undefined);
    if (typeof latest !== 'string' || !STRICT_UPDATE_VERSION.test(latest)) {
      throw new Error('Registry latest version is invalid');
    }
    return latest;
  }
}

async function publishMonotonically(
  entry: UpdateCacheEntry,
  attemptStartedAt: number,

View on GitHub (pinned to 0d1aed942f)

Solutions

1. Read the interpolated status in the message and act on it (404 → fix URL/path; 403/429 → auth or rate limit; 5xx → wait/retry or check registry status page)
2. Verify the URL with curl -i <registry-url> from the same network to reproduce outside GitNexus
3. Correct the registry configuration (host/path) or switch to the canonical registry

Example fix

// before (404 because package path missing)
// Registry returned 404
// after
buildUpdateRegistry('https://registry.npmjs.org'); // correct base, resolves the right package URL

const probe = await fetch(registryUrl); if (!probe.ok) console.warn(`Registry currently returns ${probe.status}; update check will fail`);

try { const latest = await fetchLatest(url, 0); } catch (e) { const m = /^Registry returned (\d+)$/.exec(e.message); if (m) { const status = Number(m[1]); if (status === 429 || status >= 500) scheduleRetryWithBackoff(); else logConfigProblem(status); } else throw e; }

When it happens

Trigger: The configured registry URL returns 404 (wrong path/package), 403 (blocked/rate-limited/UA-filtered), 429, or 5xx; a proxy answers 502/503 on the registry's behalf.

Common situations: Typo'd registry URL or package name path; corporate firewall returning 403 for unknown agents; registry outage or rate limiting; a custom mirror that only serves some paths.

Understand the failure class

Background: "API error: {status}" and "HTTP 401/403/404/429/5xx" errors: non-2xx HTTP responses explained — this error's family across 27 libraries.

Related errors

• Registry response too large
• Too many registry redirects
• Registry redirect missing location
• Embedding request failed (${safeUrl(url)}, batch ${batchInde
• Unsupported npm registry protocol

AI-assisted analysis of abhigyanpatwari/GitNexus@0d1aed942f (2026-09-08). Data as JSON: /api/errors/08530738feb3c194. Report an issue: GitHub.