this post was submitted on 09 Feb 2026
193 points (99.0% liked)

Selfhosted

56208 readers
1075 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Pretty much what it says on the tin, but for more context. My friends and I use Discord to play D&D and other TTRPGs. We also use it to send memes and just have conversations. We mostly do the chat, text, images, gifs, etc. But we also use the voice and video chat pretty regularly too. Screen share sometimes as well. So I'd like to try to find something that has all those features if possible.

The new ID or facial recognition requirement they are implementing is a deal breaker for a few of us, and so if I can set up some kind of alternative to make it a non-issue, I'd like to.

I'm running Ubunutu 22.04 LETS, AMD 3700X, 64GBRAM, 10x 6TB HDD, and and 2 4TB NVmE. Have a 2gb up/down internet connection. So I don't think we should have any issues making it work smoothly for 7 people.

you are viewing a single comment's thread
view the rest of the comments
[–] ohshit604@sh.itjust.works 2 points 9 hours ago* (last edited 1 hour ago)

Setting up Element Call on my instance was difficult on its own, I understand why Synapse doesn’t come with it out of the box, essentially you spin up Matrix’s JWT service for authenticating clients and it if approved forwards the connection to the Livekit ports which must be opened on your firewall (ie port forwarded), otherwise people will not be able to connect to calls.

Big PITA and in my experience, on my home network, can conflict with games with VOIP chats so don’t follow the default 50000:55000 port range Livekit recommends or you’ll run into issues like I did, each person consumes 2 ports so adjust the range to your need.


Edit: I don’t suggest running Element Call standalone, it has issues of its own, once you get Livekit and JWT running and follow This guide you should have your element call support in Synapse now, pro-tip for those running synapse behind docker and get confused on the whole ./well-known part of the documentation you can edit your ./well-known in your homeserver.yaml file like such:

serve_server_wellknown: true

extra_well_known_client_content:
  optional: client
  "org.matrix.msc4143.rtc_foci": [
      {
          "type": "livekit",
          "livekit_service_url": "https://livekit-jwt.your.domain/"
      }
  ]