this post was submitted on 29 Aug 2023
45 points (97.9% liked)

Selfhosted

40219 readers
1001 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

With jitsi meet now requireing registration (something I do understand, .. but I just happen not to have a google, MS or meta account), I am looking at selfhosting a jitsi meet for personal use.

Has somebody already done this? What are your experience? What are the hardware requirements? Docker or native? Linux or other OS? (FreeBSD)?

top 14 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 1 year ago (1 children)

It's extremely easy to set up with docker, I've been using a self-hosted instance for about 2 years now. Contact me if you need help setting it up or if you just want to test it.

Hardware requirements depend on how many users will be using it, I use an old i3 NUC as a home server and it can easily handle a room with a dozen people, especially if it's just audio, it gets heavier on the CPU if a lot of them have their webcams on but generally speaking if you have a decent internet connection you'll be fine.

Follow these instructions: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/ You will need to set up HTTPS unless you're already using a reverse proxy.

[–] [email protected] 2 points 1 year ago

Hi, I have it running as of today. apache reverse-proxy native on the server and "stable-8922" in docker.

I have been wondering if it makes sense to move the jvb from docker to the server. I guess that is the part of the system that pulls most of the traffic. I don't know if this make any real difference for performance or not.

Anycase. All, thanks again for the help. Appriciate it. :-)

Kr.

[–] [email protected] 4 points 1 year ago

I have a native install on a Debian LXC - 16GB storage, 2GB RAM and 1 core, that I've been running for over 2 years behind nginx. Doesn't need much. If you want to record via Jibri, you need more juice. I will be redoing my install as they now offer an all in one Docker stack with recording capabilities. With the native install it is recommended to have a separate Ubuntu 18.04 server for Jibri just for recording, which is a hassle and outdated.

I haven't begun the Docker setup yet, but I imagine it has to be a more pleasant experience to admin.

[–] [email protected] 4 points 1 year ago

https://www.linuxbabe.com/ubuntu/install-jitsi-meet-ubuntu-22-04

I used this tutorial to run an instance for like 2 years on a $5/mo digital ocean droplet. I set it up super quick.

[–] [email protected] 4 points 1 year ago (1 children)

I ran it via Docker, it was easy enough, consumed close to no resources, upgrading was tricky a few times. Then I got rid of that server and did not continue hosting Jitsi, started freeloading on Freifunk Munchen public instance.

[–] [email protected] 1 points 1 year ago (1 children)

Any particular reason to use the ffmuc? Are there other instances worth considering?

[–] [email protected] 2 points 1 year ago

No real reason. It's stable so I keep using it. Look at the official list: https://jitsi.github.io/handbook/docs/community/community-instances/

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
HTTP Hypertext Transfer Protocol, the Web
HTTPS HTTP over SSL
LXC Linux Containers
NUC Next Unit of Computing brand of Intel small computers
SSL Secure Sockets Layer, for transparent encryption
VPS Virtual Private Server (opposed to shared hosting)
nginx Popular HTTP server

5 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.

[Thread #90 for this sub, first seen 29th Aug 2023, 21:05] [FAQ] [Full list] [Contact] [Source code]

[–] [email protected] 3 points 1 year ago

I install/configure/manage it using this ansible role that uses native debian packages. Experience up to 4-5 users is good on a low-end cheap VPS (2GB RAM, 2 vCPU)

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

If you already have a NextCloud instance, NextCloud Talk is easy to install in your instance. It uses webrtc so your instance won't do any video processing or routing at all, so server load is minimal. You'll need to setup a stun/turn server to make it work in double-nat situation though.

[–] [email protected] 1 points 1 year ago

Hi all. Thanks for the feedback. Very much appreciated 👍. ... I will set it up in docker.

[–] neutron 1 points 1 year ago (1 children)

What about Yunohost? Its made for newbies getting into selfhosting and has Jitsi support.

[–] [email protected] 2 points 1 year ago

Hi Neutrom, I don't know this one. I'll check it out. Thx! 👍

[–] [email protected] 0 points 1 year ago

There are other public Jitsi Meet instances out there anyone can use without an account.