Content-Security-Policy when hosting livekit on a different domain than FLUXER_DOMAIN

(#586) Bug Fixed self-hosting voice

Thread

Comment by @SleazeStiKs
RexSystem 1 vote originally by @SleazeStiKs on GitHub OP
Fluxer itself is exposed on the root domain in my case chat.mydomain.com, Livekit is exposed under livekit-tcp.mydomain.com and livekit-udp.mydomain.com. In the admin panel I set the endpoint to wss://livekit-tcp.mydomain.com:7881. After some trial and error i ended up setting the endpoint to chat.mydomain.com as that resolves to the same IP as livekit-tcp.mydomain.com. This seems to fix this particular error.