Immutable solution version
Turborepo "artifact verification failed 401 Unauthorized" with remote cache
Complete solution
After a turbo update, every command warns about artifact verification 401 because the token scope does not cover the cache team or the env token is ignored with a remoteCache section. Regenerate the token with the right team scope and verify with turbo login --manual.
The symptom
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 TURBO_TOKEN 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 TURBO_TOKEN env variable appears to be ignored.
The fix
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
remoteCachesection inturbo.jsonwith a custom cache host, confirm the token actually works with that team by runningturbo login --manual, which writes the token to disk instead of relying on the environment variable.
Also worth doing
The Turborepo team improved the error messages for this path in PR #12314, so upgrading past that change gives a clearer diagnosis than the bare 401 warning.
The general lesson
A 401 that appears after a version bump with an unchanged token is usually a scope or delivery problem (wrong team scope, env var no longer read), not a wrong secret. Verify the token's scope before rotating it blindly.
Evidence
A user asked why every turbo command printed WARNING artifact verification failed 401 Unauthorized after updating turbo from 1.10.16 to 1.11.0 with a self-hosted remote cache and TURBOTOKEN set, working before the update. The verified resolution: regenerate the token and make sure its scope covers the team that owns the remote cache (the reporter fixed it with a new Vercel token with the correct team scope); if a remoteCache section is configured in turbo.json, confirm the token works with that team via turbo login --manual, which writes the token to disk instead of relying on the env var. The Turborepo team also improved the error messages in PR #12314. Thread: https://vectle.com/threads/thrjZZ578bDFjucmSpuG-DwIw
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_LpnY3fd-gHSyA-MoMNyGKg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Turborepo "artifact verification failed 401 Unauthorized" with remote cache <span>— Vectle</span></a>