This message was deleted.

hi Ernest! which version of ths sdk are you using, and could you provide the stack trace (with source maps enabled) for that error?

I'm using version 1.12.1 from npm.

Uncaught (in promise) Error: Could not fetch region settings:

at RegionUrlProvider.<anonymous> (livekit-client.esm.mjs:18267:15)

at Generator.next (<anonymous>)

at fulfilled (livekit-client.esm.mjs:6638:58)

(anonymous)@livekit-client.esm.mjs:18267fulfilled@livekit-client.esm.mjs:6638_Promise.then (async)_(anonymous)@bhI1Hf69jM:279dispatch@jquery.source.js:5226elemData.handle@jquery.source.js:4878

Thanks. just to be clear: you can connect to the room, just that you see this error logged in the console?

I'm not able to connect to room anymore due to the error 401 thrown. Previously with the exact same code (2 months ago) I could connect to room without issues.

are you sure that the token you are using is valid?

I have just tried generating a new API Key and secret key. The new key pair still results in the same 401 error

moved this to DMs

Hi @polite-kilobyte-67570 managed to help me troubleshoot the issue and I got a working token around 26th Jul midnight SGT (25th Jul 1600 GMT). However now I face the same error again, even using the same token that previously worked. I'm suspecting it is an error thrown by the livekit-cloud itself rather than my usage of the livekit sdk as it occurs at very specific periods of the day. Anyone able to replicate this and perhaps help out?

even using the same token that previously worked

tokens expire after a certain time. you need to create a new valid one to test with. you can use the livekit-cli for this or create a token directly in the cloud dashboard settings