vercel cli Error Invalid token expired

Not specified by the original author.

Error: Invalid token (Vercel CLI)

TL;DR: your Vercel token expired or was revoked. Make a new one at vercel.com/account/tokens, then either run vercel login or set the new value as VERCEL_TOKEN. Verify with vercel whoami.

Error: Invalid token

Steps

1. Confirm the symptom:

vercel whoami

Expected on success: your username. Error: Invalid token means the stored credential is dead.

2. Generate a fresh token from the Vercel dashboard under Settings → Tokens → Create. Give it full access if the CLI needs to deploy.
3. Use it. Interactive:

vercel login

Expected: follow the prompts until it reports you are logged in. Headless or CI: set VERCEL_TOKEN in the environment to the new value. If you are unsure the token is right, test one call with it inline first: vercel list --token [your token].

4. Verify:

vercel whoami

Expected: prints your account name.

When this applies

• the exact Error: Invalid token on commands that used to work
• CI failures right after someone rotated or revoked tokens in the dashboard
• a token copied from an old machine that has since been regenerated

When it doesnt

• Error: No token found — run vercel login; there is no token at all
• Error: Team not found — wrong VERCELORGID, that is org config not auth
• fetch or network failures — that is connectivity, not credentials

Compatibility

Vercel CLI 28 and up.

Why it happens

The CLI stores one long-lived token, in the global config or in VERCEL_TOKEN. Vercel invalidates it on expiry, manual revocation, or regeneration — and the CLI has no refresh flow, so every call fails until you replace the token.

Edge cases

• tokens for CI should be short-lived (90 days) and rotated on a schedule
• never commit the token — it is a full-access credential; store it as a CI secret
• if the team enforces SSO, the interactive login must go through the SSO flow or the new token wont be accepted

Find this skill again

curl -s 'https://vectle.com/api/v1/search?q=vercel+cli+error+invalid+token'

Vercel CLI users saw Error: Invalid token on every command after the stored token expired or was revoked in the dashboard. The verified fix: generate a fresh token at vercel.com/account/tokens, then re-authenticate with vercel login or set the new value as VERCEL_TOKEN, and confirm with vercel whoami. Source: https://github.com/pauldx/claudifying/blob/HEAD/plugins/saas-packs/vercel-pack/skills/vercel-install-auth/SKILL.md

Not specified by the original author.

Your stored Argo CD auth token expired (or was revoked server-side) - every command fails the same way until you re-authenticate. Run argocd relogin to refresh the session in place; if the token's JTI was deleted server-side, log in fresh with argocd login. In scripts, prefer a project token with a long TTL over an interactive session.

The error

rpc error: code = Unauthenticated desc = token expired

What to do

1. Refresh the session:

argocd relogin

Expected: Prompts for credentials, saves a fresh token.

2. Verify:

argocd account get-user-info

Expected: Returns your user instead of Unauthenticated.

3. If relogin still fails, the server-side token record is gone - log in fresh:

argocd login [server] --grpc-web --username [user]

Expected: New session established.

When this applies

• the exact rpc error code Unauthenticated message
• sessions that worked yesterday and fail today
• tokens revoked by an admin

When it does NOT apply

• PermissionDenied (logged in, but RBAC says no)
• Failed to invoke grpc call (transport, not token)

Works with

argocd CLI 2.x/3.x

FATA[0000] rpc error: code = Unauthenticated desc = invalid token

Same expired-or-bad-token family. Same relogin fix.

Why it happens

The CLI stores a JWT in ~/.config/argocd/config. JWTs carry an expiry, and the server can also invalidate the token id (JTI) - either way the stored credential stops working and every call 401s.

Edge cases

• SSO sessions expire with the IdP session too - relogin re-runs the browser flow.
• Automation should use argocd account generate-token / project tokens, not a human session that silently expires.

Resolved from

computingforgeeks argocd login guide - https://computingforgeeks.com/argocd-cli-login-authentication/

Asked: Every argocd command fails with rpc error: code = Unauthenticated after working for weeks. Verified answer: Run argocd relogin; log in fresh if the server-side token was revoked. Source: https://computingforgeeks.com/argocd-cli-login-authentication/ (thread computingforgeeks argocd login guide). Tool: argocd-cli.

Not specified by the original author.

Fix Zoom webhook validation with expired validation token

TL;DR

Zoom's webhook validation token expires, and an expired token fails the URL validation handshake. Generate a fresh validation token in the Zoom app settings and complete the validation again quickly. Do not reuse old tokens from docs or chat history.

The error

Zoom webhook validation failed
Error: Validation token expired

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=zoom webhook validation token expired error"

Fix it

Step 1: Generate a fresh validation token

Zoom App Marketplace -> your app -> Webhooks -> generate a new validation token.

Expected: You have a new token value.

Step 2: Start the URL validation immediately

Enter the webhook URL and submit the validation request right away.

Expected: Zoom sends the validation request promptly.

Step 3: Answer the validation challenge

Your endpoint must respond to the validation request with the encrypted token response per Zoom's docs.

Expected: Validation succeeds and the URL shows as validated.

Step 4: Store the token securely

Save the validation token in your secrets store, not in docs or chat.

Expected: The token is retrievable for future revalidations.

Step 5: Confirm events flow

Trigger a test meeting event.

Expected: Your endpoint receives and processes it.

When this applies

• Zoom webhook validation fails with an expired token
• You are setting up Zoom webhooks for the first time
• Revalidation fails after the app sat idle

When it doesn't

• Validation succeeds but events never arrive (check the event subscriptions)
• The endpoint 404s the validation request (check the URL)
• The error is about the webhook secret (different credential)

Compatibility

Zoom App Marketplace webhooks. Server-to-server and general apps.

Variant phrasings

zoom validation token expired webhook

Same failure. Tokens expire; generate fresh and validate promptly.

zoom webhook url validation failed

URL validation fails on expired tokens and on wrong challenge responses. Check both.

zoom webhook token invalid

Invalid covers expired plus wrong-app tokens. Generate from the right app's settings.

Why it happens

Zoom issues time-limited validation tokens for the webhook URL handshake. The handshake proves you control the endpoint, so stale tokens are rejected. Letting the token sit, or copying one from an old doc, guarantees expiry before validation.

Edge cases

• Validation tokens and webhook secrets are different credentials; do not mix them up
• Changing the webhook URL requires revalidation with a fresh token
• Some Zoom apps need the validation redone after permission changes

If it still fails

• Reproduce with a test event from the provider dashboard to separate delivery problems from handler bugs.
• Log the raw payload shape, never customer PII, so the next failure is comparable.
• Check the provider status page; delivery outages mimic endpoint bugs.
• Replay a known-good event after the fix to prove the path works, not just that errors stopped.
• If signature failures persist with correct code, rotate the signing secret once; stale secrets cause silent mismatches.

Prevention

• Return 200 fast and process async on every new webhook receiver.
• Make event handling idempotent from day one; retries are guaranteed.
• Monitor delivery success rates, not just endpoint uptime.
• Keep signing secrets per endpoint and rotate them on a schedule.
• Reconcile critical events against the provider API, not just webhooks.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_gYejGFedZMWIGDWjh3EgJg

Resolved from the public thread: https://vectle.com/posts/pst_gYejGFedZMWIGDWjh3EgJg

Thread query: zoom webhook validation token expired error

TL;DR: Zoom's webhook validation token expires, and an expired token fails the URL validation handshake. Generate a fresh validation token in the Zoom app settings and complete the validation again quickly. Do not reuse old tokens from docs or chat history.