I'm getting this error when tried running dev - File "/Users/ajay/Documents/laxmi/projects/.venv/lib/python3.12/site-packages/aiohttp/connector.py", line 1285, in _wrap_create_connection raise ClientConnectorCertificateError(req.connection_key, exc) from exc aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host jarvis-yr3qg92a.livekit.cloud:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')] 2025-08-12 025027,812 - ERROR livekit.agents - Error in _connection_task

Thanks for reaching out, laxmi. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

it is running locally and i'm not using any kind of ssl

It looks like the error is happening because SSL certificate verification is failing, even though you're running things locally without SSL. No worries though—here are a few steps that can help you fix this: 1. Run LiveKit in development mode: Try starting the server with this command to turn off SSL requirements for local development:

livekit-server --dev

2. Disable SSL verification in your client code: If the error comes from your client app, you can turn off SSL verification there. For example, in Python:

import ssl
ssl_context = ssl.create_default_context()
ssl_context.check_hostname = False
ssl_context.verify_mode = ssl.CERT_NONE

3. Use HTTP instead of HTTPS: Make sure your client is connecting to the right local endpoint without SSL, like using

BASE_API_URL

with your local server’s address. If you want, I’m here to help you walk through any of these steps—just let me know!

i don't have livkit server on my local maachine

Since the LiveKit server isn’t running locally, the SSL certificate verification error probably happens because the client can’t verify the server’s certificate. No worries though — here are some steps that can help you fix this: 1. Check the server's SSL certificate: Make sure the LiveKit server you’re connecting to has a valid SSL certificate from a trusted Certificate Authority (CA). 2. Adjust client TLS settings: If the server uses a self-signed or private CA certificate, you’ll want to configure the client to trust it by specifying the CA certificate file. For example:

tls:
  enabled: true
  ca_cert_file: /path/to/ca.crt

3. Use insecure mode (for development only): You can temporarily skip SSL verification by setting the client to insecure mode: `tls: enabled: true insecure: true`_Just a heads up: this isn’t recommended for production environments._ 4. Verify the server name: Double-check that the domain name in the client matches the server’s SSL certificate. For example:

tls:
  enabled: true
  server_name: <http://your-livekit-server-domain.com|your-livekit-server-domain.com>

If you want, I’m here to help you walk through any of these steps — just let me know! Sources: Running LiveKit on AWS | Deploy to a VM | LiveKit Docs | solutions/doorbell_local/main/certs/servercert.pem

ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)

Looks like your system is having trouble verifying the SSL certificate because it can’t find the local issuer certificate. No worries! Here are some easy steps to help you fix this: 1. Update Your System's CA Certificates: Make sure your system’s certificate store is up-to-date. If you’re on macOS, you can run:

sudo /Applications/Python\ 3.x/Install\ Certificates.command

2. Install Missing Certificates: If you’re working in a custom Python environment, double-check that it has the necessary CA certificates. You can easily install or update them with:

pip install certifi

3. Disable SSL Verification (Temporary): Just for testing, you can bypass SSL verification in your code like this:

import ssl
ssl_context = ssl.create_default_context()
ssl_context.check_hostname = False
ssl_context.verify_mode = ssl.CERT_NONE

If you run into any issues or want me to walk you through these steps, just let me know—I’m here to help!