This message was deleted.

It seems likely that the error you're encountering is related to the worker registration process with the LiveKit server. The error message "invalid worker id" suggests that the worker is not being properly identified or registered with the server. This could be due to incorrect configuration settings or missing environment variables required for the worker to connect to the server. My understanding is that you should ensure that the worker is configured with the correct WebSocket URL, API key, and API secret. These are essential for establishing a connection with the LiveKit server. According to the LiveKit documentation, the

WorkerOptions

should include these parameters, and they can also be set via environment variables:

LIVEKIT_URL

,

LIVEKIT_API_KEY

, and

LIVEKIT_API_SECRET

. Would you like more detailed guidance on configuring these settings or troubleshooting the connection further? Sources: - LiveKit documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@millions-hair-24956 Do we need to specify a separate API SECRET and API KEY in the server config?

Yes, you need to specify an API key and API secret in the server configuration. These credentials are crucial for authenticating and authorizing requests between the LiveKit server and the workers or clients. According to the LiveKit documentation, the API key and secret can be set in the server's configuration file or as environment variables (

LIVEKIT_API_KEY

and

LIVEKIT_API_SECRET

). This ensures that only authorized entities can interact with your LiveKit server. Would you like more detailed instructions on how to configure these settings in your server setup? Sources: - LiveKit documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.