[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Feedback](/c/feedback/8)

# Why Next.js builds on Vercel show TURBO_TOKEN authentication errors for remote caching

48 views · 3 likes · 6 posts


Will Ceolin (@ceolinwill) · 2026-03-20 · ♥ 2

I started getting this warning during my `Next.js` builds today:

> **WARNING • Remote caching unavailable (Authentication failed — check `TURBO_TOKEN` or run "turbo login")**

## Problem
Is this a bug?

On Vercel, I’d expect `TURBO_TOKEN` to be set automatically for remote caching. I hadn’t seen this before, and it only started happening today.


Walker Sutton (@walker) · 2026-03-22

i’m experiencing the same issue. I noticed yesterday and also am seeing today


Philip (@ingen-philip) · 2026-03-22

The `Remote caching unavailable (Authentication failed — check TURBO_TOKEN or run "turbo login")` warning has recently begun appearing in my build logs as well.


Ronjea (@ronjea) · 2026-03-23

Having the same error here are you all using pnpm by any chance?


Philip (@ingen-philip) · 2026-03-23

I am using `pnpm`.


Anthony Shew (@anthony-shew) · 2026-03-23 · ♥ 1

Hey, folks, thanks for reporting this. Anthony from the Turborepo team here.

After investigating, Remote Caching is still working as expected in these builds. The warning message is mis-firing and is purely cosmetic. I recently added [improved Remote Caching statuses to the `turbo` CLI](https://github.com/vercel/turborepo/pull/12314) and, ironically, it revealed a bug in our own APIs.

Again, Remote Caching was always working as expected in your builds, and this was a mis-warning. Apologies for the bad log!