this post was submitted on 08 Sep 2025
97 points (98.0% liked)

Selfhosted

51273 readers
935 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 2 years ago
MODERATORS
 

Some years ago, I hosted my own matrix server for a few months. I'm an experienced self-hoster, but I remeber that Matrix was paticularly hard to host, requiring weird proxy rules, DNS adjustments, federation never worked reliably and push notifications never worked at all. I ditched the project soon because I also had no real use for it. However, I recently had some ideas where a Matrix server would be useful again. Has anyone attempted to install it recently and can tell me whether the situation has improved? Also, which server do you recommend? There still is synapse but I found it paticularly complicated to host. Dendrite is now archived and the current fork seems to be tuwunel which doesn't seem to be under very active development.

(page 2) 9 comments
sorted by: hot top controversial new old
[–] SrMono@feddit.org 7 points 1 day ago

I installed synapse some weeks ago. Pretty easy, straightforward. Even managed to install some bridges.

After the last matrix.org incident and some info about the failing message retention, I just killed the server again. I'm not comfy with the service being so greedy/resource hungry and also the usability sucks at certain points.

[–] helix@feddit.org 4 points 22 hours ago

I recently shut down my server because it's a high traffic, high risk software. You should have an eye on it, I'd say at least half an hour every week...

[–] ohshit604@sh.itjust.works 3 points 21 hours ago* (last edited 21 hours ago)

As the end use my biggest gripe with Matrix is with voice communications, it’s almost as if you sneeze wrong you’ll lose connection to the voice group, screen sharing is horrible, no audio and the window is not adjustable, cant even make it full screen.

Now they’re reducing people’s usage by putting in a subscription and locking certain features, at least on the home server.

While I am disappointed they did at least take my advice and prevent Windows Recall from capturing people’s messages.

[–] tvcvt@lemmy.ml 4 points 23 hours ago* (last edited 23 hours ago)

I have synapse server running in docker on a VPS and it's been pretty reliable. At my office I use it as sort of a self-hosted Slack replacement. For our use case, I don't have federation enabled, so no experience on that front. It's a small office and everyone here uses either Element or FuzzyChat on desktop and mobile. It runs behind an nginx reverse proxy and I've got SSO set up with Authentik and that's worked very well. Happy to share some configs if that would be useful.

[–] oopsallnaps@piefed.ca 3 points 21 hours ago

I use https://github.com/spantaleev/matrix-docker-ansible-deploy which makes it pretty painless to self host on a vpc with Synapse as the server.

I don't have federation setup, since I just use it with friends. So besides running the update command once a week, I don't even think about maintaince.

[–] blurry@feddit.org 3 points 1 day ago

I host synapse as docker container behind traefik and it works pretty well. I have two users on my instance, have setup the mautrix-whatsapp bridge and federate with the instance of a friend.

The setup was straight forward: Pointing the sub-domain via traefik to the service and in the homeserver.yml enable well-known which announce port https with port 443 instead of 8448.

load more comments
view more: ‹ prev next ›