It's currently unclear how to get voice to work other that the single hint:
Voice regions and LiveKit reachability if you are enabling voice.
I only have a single community instance, so I wasn't sure whether I need to actually configure it - but by default voice/video did not seem to work.
I did manage to get it to run by create a voice region and use the url wss://<FLUXER_DOMAIN>/livekit. Add the coordinates etc, add the community ID and in the end it seems to have worked!
This needs either some refinement and/or for single community servers, maybe a way to get a default?
RexSystem1 voteoriginally by @sayagohren on GitHubCollapsed as off-topic by Rex: About connecting the desktop app to self-hosted instances, which has its own thread.
In the documentation there is no also information about the way of switching instances on desktop client. It seems to me that connection to official server is hard-coded and it is impossible to connect to self-host using windows and android app, using web version is shitty.
In the documentation there is no also information about the way of switching instances on desktop client. It seems to me that connection to official server is hard-coded and it is impossible to connect to self-host using windows and android app, using web version is shitty.
RexSystem1 voteoriginally by @schemen on GitHub OP
Alright, I also figured something out:
You can add the following line to the docker-compose.yml, next to the other livekit variables:
FLUXER_LIVEKIT_DEFAULT_REGION: '{"id":"default","name":"Default","emoji":"🌍","latitude":0,"longitude":0}'
The app can deal with a default region, this essentially just configures a default region and it'll work.
See my comment @ https://feedback.fluxer.com/p/641/c/1649 – big updates coming to self-hosting and voice & video (entirely rewritten custom stack, no more LiveKit, major stonks). Closing this issue out in preparation for that. Thanks!
7 comments
Off-topic comment by @sayagohren
Comment by @davefatkin
Comment by @schemen
Comment by @schemen
FLUXER_LIVEKIT_DEFAULT_REGION: '{"id":"default","name":"Default","emoji":"🌍","latitude":0,"longitude":0}'The app can deal with a default region, this essentially just configures a default region and it'll work.Comment by @mirkohubtv
Comment by @schemen
Comment by Hampus