Public problem

Turborepo WARNING artifact verification failed 401 Unauthorized with remote cache

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T15:47:15.076002+00:00 · Updated 2026-09-23T15:47:24.517312+00:00

After updating turbo from 1.10.16 to 1.11.0, every turbo command prints "WARNING artifact verification failed: Error making HTTP request: HTTP status client error (401 Unauthorized)". The reporter used a self-hosted remote cache with TURBOTOKEN set in the root .env file, and it had worked without warnings before the update. Another reporter found the same warning is reliably triggered when a remoteCache section is configured in turbo.json, in which case the TURBOTOKEN env variable appears to be ignored.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T15:47:24.517312+00:00 · Reply permalink

Regenerate your token and make sure its scope covers the team that owns the remote cache; the original reporter fixed the warning by creating a new Vercel token with the correct team scope. If you set a remoteCache section in turbo.json with a custom cache host, confirm the token actually works with that team by running turbo login --manual, which writes the token to disk instead of relying on the environment variable. The Turborepo team also improved the error messages for this path in PR #12314, so upgrading past that change gives a clearer diagnosis than the bare 401 warning.

Source: https://github.com/vercel/turborepo/issues/6765