<@U084APK40NS> 5-02-14 09:47:33,759 - ERROR call-h...
# ask-ai
a
@millions-hair-24956 2025-02-14 094733,759 - ERROR call-handler - [2025-02-14T144733.759320] correlation_id=2f2a6b17-ae32-442d-89cd-7e5855e0b969 room_name=f8777931-b6e4-4521-8e46-5f60014006b4 call_id=f0114493-6bea-4fcf-92d1-692f0f1937fd call_type=OUTBOUND tenant_id=671feeb463a1ce1afa16b3ce Configuration error: Cannot connect to host ontune-weztvqmg.omumbai1a.livekit.cloud:443 ssl:True [SSLCertVerificationError: (1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'ontune-weztvqmg.omumbai1a.livekit.cloud'. (_ssl.c:992)")] {"pid": 85207, "job_id": "AJ_qYNCXjULMB3W"}
g
The error you're encountering indicates an SSL certificate verification failure due to a hostname mismatch. This means the SSL certificate presented by the server does not match the expected hostname
ontune-weztvqmg.omumbai1a.livekit.cloud
. This could be due to an incorrect server configuration or an issue with the SSL certificate itself. To resolve this, ensure that the SSL certificate is correctly configured for the domain
ontune-weztvqmg.omumbai1a.livekit.cloud
. You may need to check the server's SSL configuration and verify that the certificate includes the correct domain name. Additionally, ensure that your client is connecting to the correct server address. Would you like more detailed steps on how to verify and resolve SSL certificate issues? Sources: - https://livekit-users.slack.com/archives/C07FVFL1H3P/p1732602824.811679 - https://livekit-users.slack.com/archives/C07FY8WHGPM/p1732232726.198099 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
a
@dry-elephant-14928 I am using the URL which you provided.
@refined-appointment-81829
r
Check your OS and certificates
Did you follow something like I mentioned here yet? https://livekit-users.slack.com/archives/C048FRL1N2C/p1732399568426869
a
Let me try once. One more it is working with wss://ontune-weztvqmg.livekit.cloud url. Not sure why it is not working with mumbai url
r
yes, check that thread I sent. Everytime I've seen someone with a message like the one you shared it is because the keystore was not setup.
I think that is in our docs but I will check and make sure. I've seen that enought that is is worth calling out if it is not already in there
a
Ok