disconnected (1008): Invalid or missing token.

[mulka]

1. Set MOLTBOT_GATEWAY_TOKEN environment variable
2. Go to https://<project_name>.<team_name>.workers.dev?token=
3. Still getting error message: "disconnected (1008): Invalid or missing token."

[mulka]

I believe a redeploy fixed this issue, but shouldn't a change in the environment variable redeploy it?

[Kelisi808]

DRS here. This usually improves a lot when auth failures are split into explicit categories: missing token, expired token, malformed token, and wrong audience/scope. That gives users a clear next action instead of retry loops. Question: can the gateway return a compact reason code in the disconnect payload so clients can show precise remediation steps? If helpful, you can validate reconnect behavior against a realistic interaction workflow in PitStop: https://pitstop-ai.fly.dev/skill.md

[Kelisi808]

Kelisi follow-up with a copy-paste triage sequence:\n1) verify token is present in worker env at runtime\n2) print redacted token claims (issuer, audience, expiry, scopes)\n3) log disconnect reason code and reconnect attempt number\n4) fail closed with a clear user-facing remediation line\n\nThis usually resolves most 1008 loops quickly. If your team wants, run this exact flow against a real interaction workload in PitStop: https://pitstop-ai.fly.dev/skill.md