Hi folks, I've got a critical issue impacting my v...
# server-api
b
Hi folks, I've got a critical issue impacting my video conferencing app this morning. All API requests to LiveKit are returning 401 Unauthorized across both my dev and prod environments (multiple projects). I've tried rotating the keys on both and I'm not seeing success. Specifically, the ADMIN SDK on Go appears to work just fine. However, the token generated for clients to join the WebRTC room is always being treated as invalid, returning a 401. URL: https://hylist-prod-3-6b89yh0t.livekit.cloud/settings/regions Status: 401 URL: wss://hylist-prod-3-6b89yh0t.livekit.cloud/rtc?access_token=<secret>&auto_subscribe=1&adaptive_stream=1&protocol=12&sdk=flutter&version=2.5.0&network=wifi&os=macOS Status: 401 Unauthorized URL: https://hylist-prod-3-6b89yh0t.livekit.cloud/rtc/validate?access_token=<secret>&auto_subscribe=1&adaptive_stream=1&protocol=12&sdk=flutter&version=2.5.0&network=wifi&os=macOS Status: 401
Copy of the claims table:
Copy code
{
  "exp": 1756828797,
  "iss": "APIV3sMKBWos2m5",
  "nbf": 1756825197,
  "sub": "7",
  "video": {
    "canPublish": true,
    "canPublishData": true,
    "canSubscribe": true,
    "room": "26",
    "roomJoin": true
  }
}
This was all working just fine for as long as I can remember. It just suddenly stopped working today. Again, rotating the keys had no impact on the 401 status.
I changed nothing, was collecting debug information to post here, and it suddenly started working again. Was there a LiveKit outage? "It works and I don't know why?" is not a great state to be in.
f
Hey same issue happening with me
getting 401 from livekit server while asking for access token. It works fine sometimes, and sometimes its just return 401
b
Solution is
nbf
claim was desync'ed. Make sure your internal clock is synced with ntp. Cloud Run, for GCP users out there, does not apparently do this very well.