this post was submitted on 19 Sep 2024
51 points (89.2% liked)

Selfhosted

40296 readers
213 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 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
51
Selfhosted chat service (feddit.nl)
submitted 2 months ago* (last edited 2 months ago) by VitabytesDev@feddit.nl to c/selfhosted@lemmy.world
35 comments fedilink hide all child comments
 

After the arrest of Pavel Durov, I wanted to move from Telegram to something end-to-end encrypted. I know Signal is pretty good, but I think it is better to have our messages in my own server.

I have already looked in XMPP, but it required SSL certs and I did not have the mood to configure them.

Do you know any other selfhosted messaging service for a group of 4-5 friends, or an easy way to configure an XMPP server? Or shall I use Signal after all (I don't really care that much about being selfhosted, I just thought it would be more privacy friendly)?

UPDATE: I managed to set up an XMPP server using prosody with the SSL certs. We have been testing it with my friend and it seems to go well.

you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 1 points 2 months ago (3 children)

I suppose, but then you're kind of screwed if you want to access Jellyfin outside of your network. I suppose you could use a VPN, but it's probably easier to just not use the Chromecast (or just accept that it's going to hit the WAN regardless).

[–] qjkxbmwvz@startrek.website 1 points 2 months ago (2 children)

Yeah I don't expose Jellyfin over the Internet, so it doesn't matter for me, and wouldn't work at all over WAN (unless VPN'd to home network).

Also, it's all reverse proxied, and there's nothing preventing having two Jellyfin hostnames, e.g., jf-local.mydomain.com and jf-public.mydomain.com.

[–] sugar_in_your_tea@sh.itjust.works 2 points 2 months ago (1 children)

Then you're all clear.

I personally want my Jellyfin to be on the WAN, and I have certain devices on my internal network VPN'd to my VPS, which exposes the services I want to access remotely. But if you don't need that, using the local addr in your DNS config totally works. Getting TLS certs will be complicated, but you don't need that anyway if everything is local or over a VPN.

[–] qjkxbmwvz@startrek.website 2 points 2 months ago

Getting TLS certs will be complicated

I just use Let's Encrypt with a wildcard domain

same certs for public and private facing domains. I'm sure this isn't best practice, but it's mostly just for me so I'm not too worried :)