this post was submitted on 24 Jul 2023
39 points (100.0% liked)

Selfhosted

40439 readers
733 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
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
39
[advice] Hosting Matrix Server & Bridges (lemmy.perthchat.org)
submitted 1 year ago by [email protected] to c/selfhosted
24 comments fedilink hide all child comments
 

Hi all,

I want to host my own matrix server, so that i can run bridges to all the other (stupid) messaging apps.

I am looking for any advice or experience in choosing which server to run, and if you know of any good tutorials, run throughs, etc. i typically would like a lighter instance, as i expect about 3 users, with 2 of us needing bridging.

  • dendrite
  • synapse
  • conduit
  • construct

and then the addition of bridges, (Signal, WA, Messenger and hopefully SMS).

I am fairly self sufficient when it comes to self hosting, and i run everything on linux, in docker, proxied by Nginx proxy manager. but typically prefer stuff that works more or less out of the box.

Thanks all!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

I have the container up, but now some issues with ports. I can connect with element in the browser, but the app is having issues.

What did you do with proxying? I was told I need to port forward 8448, but that doesn't seem right.

I'm using nginx proxy manager, default settings, and LE certs.

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

You can use whatever port if you’re proxying it to 8448 (assuming the container host is listening on that port which it would be by default).

If you use matrix.example.com and proxy port 443 to 8448 then it should work as your user would be @user:matrix.example.com.

You would need to portforward from outside your network if you want to access it and have it talk to other servers as they all need to communicate with your server.

Personally I wanted matrix to show my user as @user:example.com at my actual domain not as a matrix subdomain, so I had to setup the .well-known/server type http path to tell it my server is actually at matrix.example.com.

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

yep, i have my sub-domain proxying to the host :8448, and i can use it locally. however the android element app is not able to connect, but the browser element can.

it is a dilly of a pickle, and i am not sure what is missing.

the docs at https://gitlab.com/famedly/conduit/-/blob/next/DEPLOY.md tell me to curl directly to port 8448.... oh, dumbass! just typing this out i saw that it was an if not an and port 8448.... never mind! i iwll post this to indicate my stupidity and hopefully figure out what i am doing wrong!

$ curl https://your.server.name/_matrix/client/versions

# If using port 8448
$ curl https://your.server.name:8448/_matrix/client/versions