requests.exceptions.ConnectionError: HTTPSConnectionPool(host='secondbrainsportsclub-1nobc1nb.livekit.cloud', port=443): Max retries exceeded with url: /observability/logs/otlp/v0 (Caused by NameResolutionError("HTTPSConnection(host='secondbrainsportsclub-1nobc1nb.livekit.cloud', port=443): Failed to resolve 'secondbrainsportsclub-1nobc1nb.livekit.cloud' ([Errno -3] Temporary failure in name resolution)"))

Thanks — I’m looking at the DNS/connection error you posted. You’re seeing: requests.exceptions.ConnectionError: HTTPSConnectionPool(host='secondbrainsportsclub-1nobc1nb.livekit.cloud', port=443): Max retries exceeded with url: /observability/logs/otlp/v0 (Caused by NameResolutionError(...): Failed to resolve 'secondbrainsportsclub-1nobc1nb.livekit.cloud' ([Errno -3] Temporary failure in name resolution)) What this means • Your client tried to open an HTTPS connection to the LiveKit project subdomain

secondbrainsportsclub-1nobc1nb.livekit.cloud

, but DNS lookup for that hostname failed. No IP address was returned, so the request could not proceed. • The specific error text “[Errno -3] Temporary failure in name resolution” usually indicates a transient DNS resolution problem or a network-level block (proxy/firewall) preventing DNS lookups. Common causes and immediate checks • Transient DNS issue: Retry the request. Temporary DNS outages happen and can be resolved simply by retrying. • Local or network DNS misconfiguration: Check the machine’s DNS settings and test resolution: ◦ run

dig secondbrainsportsclub-1nobc1nb.livekit.cloud

or

nslookup secondbrainsportsclub-1nobc1nb.livekit.cloud

from the host reporting the error. • Corporate proxy / firewall (e.g., Zscaler) or deep packet inspection: These can interfere with connections to

*.livekit.cloud

and may break DNS or TLS. If you’re behind such a proxy, it frequently requires explicit bypass rules for LiveKit domains. • Incorrect project subdomain: Verify that

secondbrainsportsclub-1nobc1nb

is the correct and active LiveKit project subdomain you expect to use. Suggested troubleshooting steps 1. Retry the request to rule out a transient DNS glitch. 2. From the same host that raised the error, run: ◦

dig secondbrainsportsclub-1nobc1nb.livekit.cloud

◦

nslookup secondbrainsportsclub-1nobc1nb.livekit.cloud

Observe whether these return an IP address or an error. 1. If DNS lookups fail: ◦ Check the host’s configured DNS servers (e.g., /etc/resolv.conf on Linux). ◦ Try using a public DNS temporarily (e.g., 8.8.8.8) to see if resolution succeeds. 1. If DNS succeeds but the application still fails: ◦ Check for proxy / firewall rules or SSL inspection appliances that might block or rewrite traffic to

*.livekit.cloud

. ◦ If you use Zscaler or similar, add a bypass for LiveKit domains (example pattern:

*.livekit.cloud

and

turn.livekit.cloud

) so DNS and TLS pass through unchanged. 1. Verify your LiveKit project subdomain is correct in your configuration. If you can, please share: • The output of a

dig

or

nslookup

run from the affected host (copy/paste the results). • Whether the host is behind a corporate proxy or Zscaler. • Whether other hosts/networks can resolve that hostname successfully. I’ll use that info to recommend the next step (network config changes, proxy bypass rules, or further investigation). Sources: server-sdk-go | livekit/livekit_composite | DeepWiki | Configure ZScaler proxy for LiveKit connections | LiveKit