5 ms·

I was getting login pages last week when attempting to start meetings. Ironically, this led me to self-hosting Jitsi with the Jitsi Helm chart and putting it b

I was getting login pages last week when attempting to start meetings. Ironically, this led me to self-hosting Jitsi with the Jitsi Helm chart and putting it behind oauth2-proxy so my friends and I can use it. Deploying Jitsi with the Helm chart is remarkably simple and does not consume that much memory. If anyone is interested in self-hosting: 2 GB is my RAM usage on idle when running videobridge, web-ui, prosody, and oauth2-proxy atop k3s in its default configuration. You do have to open a stupidly large range of ports to UDP traffic for videobridge, though. With that said, it's been a reliable solution and does not need me or my friends to create $BIGTECH account.

unmole 3y ago
> does not need me or my friends to create $BIGTECH account. So, who is the OAuth provider?
- koito17 3y ago
  Our own private, self-hosted Forgejo instance that we use often enough that using it as an identity provider is not a big hassle :) If you have no cookies or expired ones, oauth2-proxy will take you a page with a simple "Log in with OpenID Connect" button, which then takes you to the login page of the Forgejo instance. If you're not logged in, then you provide your credentials. Otherwise, you get redirected back to Jitsi with cookies that are good for a week.
  - ofrzeta 3y ago
    I didn't remember, so I had to Google: Forgejo is the recent Gitea fork that itself is a Gogs fork. To save some people some clicks. https://news.ycombinator.com/item?id=34011581 https://news.ycombinator.com/item?id=34011581
    - zx8080 3y ago
      Forgeto
- ahoka 3y ago
  You can run your own, there are a lot of open source IDPs.
ezst 3y ago
2GB RAM for idling isn't what I would call "not that much memory" :)
- bombcar 3y ago
  640MiB ought to be enough for anyone ;)
  - antaviana 3y ago
    It was 640KB...
  - ezst 3y ago
    I mean, I get the reference, but this amount of upscaling has a measurable cost in the real world, in this day and age (a small simulation from EC2's price calculator brings it from $40 to $80 a month if you go e.g. from t2.medium to t2.large). I don't want to sound mean or unappreciative of jitsi developers' efforts, just highlighting that this kind of resource needs might put it out of reach of many potential users.
- dijit 3y ago
  2G is what Teams uses idle on my client PC which is much more constrained on memory than my server(s) that have in the order of 64-512G. If you're hosting things for internal consumption it's a generally good rule to put the memory burden on the server if you can.
  - ezst 3y ago
    I don't think anyone in their sane mind considers Teams (or anything electron-based, really) a model of adequate resource usage :) And I'm thrilled that you can afford $100-$600 a month of server costs to run jisti, but I'm willing to bet that you are not a majority.
    - dijit 3y ago
      > I don't think anyone in their sane mind considers Teams (or anything electron-based, really) a model of adequate resource usage :) That's fair > And I'm thrilled that you can afford $100-$600 a month of server costs to run jisti, but I'm willing to bet that you are not a majority. Stop hosting everything on Amazon, it's a total rip-off for raw compute. 64GiB of ram shouldn't be costing you more than $50/m (for some kind of colo like Hetzner) 2GiB of ram should probably be closer to $10 for a single VM instance with someone like Tilaa or Vultr (after tax) Meaning one you start hitting 8GiB of total consumption for all your services it's cheaper to make the leap to 64GiB of ram and go with a colo.
deleted 3y ago
[deleted]
kiririn 3y ago
Glad to hear it’s gotten easier to run, back in peak covid times it was absolute nightmare fuel to self-host when it came time to update it. Even self hosting email is easier than Jitsi was at that time
WhyNotHugo 3y ago
2GB of RAM would basically make it the largest VPS I rent. It's a pretty beefy server, IMHO. This gets worse if you only have a few calls per month. The cost and management overhead doesn't scale at all.
- koito17 3y ago
  I should have clarified what I meant with the 2GB figure. I am counting the memory consumption of everything: running Linux (specifically Fedora Server 38), running k3s (which means CoreDNS, Klipper, Traefik, ...), running the oauth2-proxy, then running the whole suite of Jitsi (sans Jibri, since I do not need the functionality it provides). I simply ran "free -h" in my server and saw 2GB of memory usage. The "actual" amount of memory that goes into running jvb and jicofo seems to be roughly 600 MB, which is still a lot to some, I guess. But I was able to run a meeting with three people and share my screen with peak memory usage at 2.2 GB -- again, for the whole system. k3s-server makes up nearly half of the 2 GB idle figure, sitting at about 700 MB of usage (according to the top(1) command I ran for this post). If 2 GB idle memory usage is too much, then I would say ditch k3s entirely and handle everything with docker-compose, using Nginx as your reverse proxy. That should at least bring the figure down to about 800 MB (jvb, jicofo, prosody, containerd, oauth2-proxy, nginx).

unmole 3y ago

> does not need me or my friends to create $BIGTECH account. So, who is the OAuth provider?

koito17 3y ago
Our own private, self-hosted Forgejo instance that we use often enough that using it as an identity provider is not a big hassle :) If you have no cookies or expired ones, oauth2-proxy will take you a page with a simple "Log in with OpenID Connect" button, which then takes you to the login page of the Forgejo instance. If you're not logged in, then you provide your credentials. Otherwise, you get redirected back to Jitsi with cookies that are good for a week.
- ofrzeta 3y ago
  I didn't remember, so I had to Google: Forgejo is the recent Gitea fork that itself is a Gogs fork. To save some people some clicks. https://news.ycombinator.com/item?id=34011581 https://news.ycombinator.com/item?id=34011581
  - zx8080 3y ago
    Forgeto
ahoka 3y ago
You can run your own, there are a lot of open source IDPs.

ezst 3y ago

2GB RAM for idling isn't what I would call "not that much memory" :)

bombcar 3y ago
640MiB ought to be enough for anyone ;)
- antaviana 3y ago
  It was 640KB...
- ezst 3y ago
  I mean, I get the reference, but this amount of upscaling has a measurable cost in the real world, in this day and age (a small simulation from EC2's price calculator brings it from $40 to $80 a month if you go e.g. from t2.medium to t2.large). I don't want to sound mean or unappreciative of jitsi developers' efforts, just highlighting that this kind of resource needs might put it out of reach of many potential users.
dijit 3y ago
2G is what Teams uses idle on my client PC which is much more constrained on memory than my server(s) that have in the order of 64-512G. If you're hosting things for internal consumption it's a generally good rule to put the memory burden on the server if you can.
- ezst 3y ago
  I don't think anyone in their sane mind considers Teams (or anything electron-based, really) a model of adequate resource usage :) And I'm thrilled that you can afford $100-$600 a month of server costs to run jisti, but I'm willing to bet that you are not a majority.
  - dijit 3y ago
    > I don't think anyone in their sane mind considers Teams (or anything electron-based, really) a model of adequate resource usage :) That's fair > And I'm thrilled that you can afford $100-$600 a month of server costs to run jisti, but I'm willing to bet that you are not a majority. Stop hosting everything on Amazon, it's a total rip-off for raw compute. 64GiB of ram shouldn't be costing you more than $50/m (for some kind of colo like Hetzner) 2GiB of ram should probably be closer to $10 for a single VM instance with someone like Tilaa or Vultr (after tax) Meaning one you start hitting 8GiB of total consumption for all your services it's cheaper to make the leap to 64GiB of ram and go with a colo.

deleted 3y ago

[deleted]

kiririn 3y ago

Glad to hear it’s gotten easier to run, back in peak covid times it was absolute nightmare fuel to self-host when it came time to update it. Even self hosting email is easier than Jitsi was at that time

WhyNotHugo 3y ago

2GB of RAM would basically make it the largest VPS I rent. It's a pretty beefy server, IMHO. This gets worse if you only have a few calls per month. The cost and management overhead doesn't scale at all.

koito17 3y ago
I should have clarified what I meant with the 2GB figure. I am counting the memory consumption of everything: running Linux (specifically Fedora Server 38), running k3s (which means CoreDNS, Klipper, Traefik, ...), running the oauth2-proxy, then running the whole suite of Jitsi (sans Jibri, since I do not need the functionality it provides). I simply ran "free -h" in my server and saw 2GB of memory usage. The "actual" amount of memory that goes into running jvb and jicofo seems to be roughly 600 MB, which is still a lot to some, I guess. But I was able to run a meeting with three people and share my screen with peak memory usage at 2.2 GB -- again, for the whole system. k3s-server makes up nearly half of the 2 GB idle figure, sitting at about 700 MB of usage (according to the top(1) command I ran for this post). If 2 GB idle memory usage is too much, then I would say ditch k3s entirely and handle everything with docker-compose, using Nginx as your reverse proxy. That should at least bring the figure down to about 800 MB (jvb, jicofo, prosody, containerd, oauth2-proxy, nginx).