This message was deleted.
# helpdesk
s
This message was deleted.
a
With room composite egress, I believe you would need to host your own template and use the custom base url parameter
s
I only need track egress to a file/S3 bucket
I believe the certificate mentioned on the logs is the on used on the livekit server signalling
a
Is egress running within the same vpc?
s
yes it is
browsers, egress and livekit server all in the same network
a
I'm not sure whether it's possible with self signed certificates https://docs.livekit.io/oss/deployment/#domain,-ssl-certificates,-and-load-balancer
d
Egress uses livekit's Go SDK to connect to the room. It'll by default validate certs. You can disable this behavior by modifying the dialing behavior here to something like: https://github.com/livekit/server-sdk-go/blob/main/signalclient.go#L84
Copy code
dialer := *websocket.DefaultDialer
	dialer.TLSClientConfig = &tls.Config{InsecureSkipVerify: true}
then you'd have to recompile egress to get it to work. alternatively, you could use ws:// URLs without the self-signed SSL.
s
Fixed it 🙂! For future reference here it is: Egress uses the “debian way” of handling the root certificated. So, simply add the self sign root cert to
/usr/share/ca-certificates/
and run
sudo dpkg-reconfigure ca-certificates
and when the Egress connects to the livekit it should validate the certificate.
🙌 1
Thanks allot @dry-elephant-14928, I was already looking into the code but was lost in the signalclient.go when I finally got it to work with the method above.
d
ah ha! that's great to know. Thanks for sharing @steep-painter-64729!