Did anyone installed jitsi meet lately

tarkhil

tarkhil

Hello

I'm trying to install matrix+jitsi meet, and I'm in total darkness. Jitsi meet components fights instead of cooperate, and all FreeBSD docs on subject are years old.

Can anyone with fresh positive experience help?
 
cracauer@ , I believe tarkhil is referring to self-hosting a Jitsi Meet server.

But yes, the client runs inside the browser.

I'm afraid I can't help you with the FreeBSD solution tarkhil. I tried it a couple of times over the years, but as you've discovered, it's rather undocumented. For now, I've reverted to officially supported Linux distros for that particular server, which can be spun up fairly quickly.

Don't receive that as discouragement though. For my purposes, I just couldn't justify the time to figure it out.
 
My current server do not run modern Linux in bhyve ((( I'll try to think the damned thing out.
 
Anyway I think the problem is not in configs, but in built software. 15 second timeout fires immediately, what is the most likely cause?
 
unfortunately, I have never figured out how to get it to run properly. The various sources did not help, in the end I installed Linux in a VM and used a container, that was all done in 30 minutes.
 
tarkhil said:
Hello

I'm trying to install matrix+jitsi meet, and I'm in total darkness. Jitsi meet components fights instead of cooperate, and all FreeBSD docs on subject are years old.

Can anyone with fresh positive experience help?
Click to expand...
Why not Matrix + Livekit (Element-Call), which runs perfectly in FreeBSD.
 
tarkhil said:
Hello

I'm trying to install matrix+jitsi meet, and I'm in total darkness. Jitsi meet components fights instead of cooperate, and all FreeBSD docs on subject are years old.

Can anyone with fresh positive experience help?
Click to expand...
Matrix has recently changed to their inhouse-built "Element Call" feature, so Jitsi isn't required anymore. It is/was a PITA to set it up anyways.

Setting up element call is another challenge in and of itself, and pkg synapse itself is way outdated, the package maintainer isn't making much of an effort to keep it up-to-date. Last time we were enough people to force an update with complaining, the freebsd version was 10(!) versions behind the official one. Now we're just ~5 versions behind afaik, so far.

Exactly because of this, over time, I'm planning to wander off the PKG route and set up matrix and element call with scripting within a freshly installed jail so I can always have the latest version. I'll report on the progress if anyone's interested. I need to get a more up-to-date synapse+element call+whatever else needed running, since matrix is my main communication platform.
 
karolyi said:
Matrix has recently changed to their inhouse-built "Element Call" feature, so Jitsi isn't required anymore. It is/was a PITA to set it up anyways.

Setting up element call is another challenge in and of itself, and pkg synapse itself is way outdated, the package maintainer isn't making much of an effort to keep it up-to-date. Last time we were enough people to force an update with complaining, the freebsd version was 10(!) versions behind the official one. Now we're just ~5 versions behind afaik, so far.

Exactly because of this, over time, I'm planning to wander off the PKG route and set up matrix and element call with scripting within a freshly installed jail so I can always have the latest version. I'll report on the progress if anyone's interested. I need to get a more up-to-date synapse+element call+whatever else needed running, since matrix is my main communication platform.
Click to expand...
I build from source by cloning github repo for every component of Matrix/Element (server side only). So far I had one incident where the Synapse failed to start due to an issue on their side, but was sorted quickly.

I highly recommend this path as the development pace is too fast for the packages to get updated frequently.

element-hq generally releases a new version every one or two weeks.
 
freebuser said:
I build from source by cloning github repo for every component of Matrix/Element (server side only). So far I had one incident where the Synapse failed to start due to an issue on their side, but was sorted quickly.

I highly recommend this path as the development pace is too fast for the packages to get updated frequently.

element-hq generally releases a new version every one or two weeks.
Click to expand...
Yes, I already do that with element-web and synapse-admin, just need to set up the same with synapse, and element-call. Also, most probably a turn/stun server will be necessary too (for webrtc), but that I already have with coturn set up.
Good to know what to expect with synapse-latest.
 
You must log in or register to reply here.
Back
Top