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)?

  • dosse91@lemmy.trippy.pizza
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    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.

  • oldfart@lemm.ee
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    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.

  • minnix@lemux.minnix.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    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.

  • kristoff@infosec.pubOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

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

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    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 11 acronyms.

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

  • redcalcium@lemmy.institute
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    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.

  • Cam@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

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