blue-policeman-87141
08/17/2025, 5:35 PMtall-airline-16756
08/17/2025, 5:35 PMtall-airline-16756
08/17/2025, 5:35 PM.env
file: Just create a .env
file in your project’s root folder and pop in these lines, swapping out the placeholders with your real info:
LIVEKIT_API_KEY=your_api_key_here
LIVEKIT_API_SECRET=your_api_secret_here
LIVEKIT_URL=<wss://your_livekit_server_url>
2. Using a .env.local
file: Same idea—create a .env.local
file in the root and add those variables.
3. Exporting environment variables: Or if you prefer, you can export them directly in your shell like this:
export LIVEKIT_API_KEY=your_api_key_here
export LIVEKIT_API_SECRET=your_api_secret_here
export LIVEKIT_URL=<wss://your_livekit_server_url>
Just make sure to replace your_api_key_here
, your_api_secret_here
, and <wss://your_livekit_server_url>
with your actual details.
If you want, I’m here to help! Just let me know if you have your LiveKit API credentials handy and how you’re currently setting those environment variables.
Sources: Transcription Applications | livekit/livekit_composite | DeepWiki | livekit-plugins/livekit-plugins-deepgram/livekit/plugins/deepgram/stt.py | client/web/.env.example | Next.js 13+ quickstart | LiveKit Docsblue-policeman-87141
08/17/2025, 5:37 PMtall-airline-16756
08/17/2025, 5:37 PM.env
file, let’s zoom in on the connection issue together. Could you share a bit more about the error you’re encountering? Specifically:
• What exact error message are you seeing?
• Is your LIVEKIT_URL
set to a valid WebSocket URL (like <wss://your_project.livekit.cloud>
)?
• Have you had a chance to check if any network or firewall settings might be blocking the connection?
With these details, we’ll be able to get to the bottom of this and find a fix for you.
Sources: client/web/.env.example | examples/nextjs/.env.example | client/web/.env.example