This message was deleted.

setup egress to debug mode and set ws url to wss:<domain>, keep the insecure to default

@faint-army-19363 I'm not using TLS. Why would I write wss?

ok then pass as ws://domain. Egress service should be able to access into your livekit servers via outside (public internet), which will send a request from https://egress-composite.livekit.io (default layout site). You should the egress service exactly error in egress service server logs

"url": "<https://egress-composite.livekit.io?layout=speaker-dark&token=><token>&url=wss%3A%2F%2F<domain>"}

My livekit servers are accessible from outside. My app using my livekit servers right now.

There is a config flag for

insecure

that needs to be set to true. Otherwise, chrome cannot connect to an insecure websocket

it is already set. insecure: true . it's not working.

if your livekit-server is accessible from outside, it is using TLS. Have you tried using

wss://

?

I will try but this is my livekit helm yaml. I don't think I am using TLS.

The helm chart is meant to be used with TLS (see pre-requisites): https://docs.livekit.io/oss/deployment/kubernetes/#pre-requisites I’m not sure how you have

mydomain

mapped to a livekit instance otherwise, or whether there are firewall issues with connecting the two deployments

I set up a livekit server with the helm yaml file above and I can broadcast with the address ws://mydomain:7880. I'm not using kubernetes on AWS, GCloud, or DO. How can I configure TLS?

use nginx ingress to expose service.