Copying them over here --- I was able to fix the cors policy issue with my own token server, but there's nothing I can do about the LiveKit cloud server. I really don't want to build my own server for this. I get a cors error for this URL:

http://<PROJECT-ID>.livekit.cloud/settings/regions

and the web socket fails (but probably because it doesn't get the region. [3:44 AM] websocket connection failure from my Unity WebGL build:

[3:45 AM] WebSocket connection to 'ws://<PROJECT-ID>.livekit.cloud/rtc?access_token=<TOKEN>&auto_subscribe=1&sdk=js&version=1.13.2&protocol=9' failed:

websocket connection failure from my Unity WebGL build:

[3:45 AM] WebSocket connection to 'ws://<PROJECT-ID>.livekit.cloud/rtc?access_token=<TOKEN>&auto_subscribe=1&sdk=js&version=1.13.2&protocol=9' failed:

This url also fails with cors error:

http://<PROJECT-ID>.livekit.cloud/rtc/validate?access_token=eyJhbGciOiJIUzI1NiIsInR5c[…]0&auto_subscribe=1&sdk=js&version=1.13.2&protocol=9

For CORS, our server is configured to allow all CORS requests. For the websocket connection failures, do you have the detailed error messages?

Check out Dolby.IO’s Unity Plugin. That’s how it should work!

And remember, behind every large enterprise client spending thousands of dollars every month, is a lone developer like me researching solutions.

Good luck to you guys