Comment on as a noob, should I connect jellyfin with tailscale using OIDC?

• hendrik@palaver.p3x.de ⁨3⁩ ⁨weeks⁩ ago

  Sure, sorry, you’re in the selfhosted community, so I sent some self hosted options 😆 If you own one of the internet/wifi routers with Wireguard built in (FritzBox, MikroTik, etc…) that might be an option as well. Other than that, I never tried any of the more commercial options, so I don’t know much about it.

  original

  • Sirius006@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

    I’ve been wanting to learn basic self hosting for a while but I don’t really have the time to dig into it now (I have two young kids, a job that takes a lot of brandwitch, and brand new medical problems). I’m only in this situation because Jellyfin was waaaay to easy to setup locally so now I want more. It’s all their fault.

    In a few years I’ll dig more, for myself and to be able to teach some basic tech literacy to my daughters when they grow up.

    original

    • hendrik@palaver.p3x.de ⁨3⁩ ⁨weeks⁩ ago

      Take care. Yeah, some things are really easy. But then at some point it always gets nasty, there’s a million details to learn and you can keep digging down pretty much forever 😆 If you’re at some time in the position to do it as a hobby, there’s ways to make it a bit less time consuming. We have some turnkey solutions. I sometimes recommend https://yunohost.org for people who just want to set up a server without dealing with all the low level stuff… But still, it’s an entire hobby.

      original

      • Sirius006@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

        Uh, I never heard of Yunohost before but it actually seems awesome ! I bookmarked it. It might lead me to start with getting serious with selfhosting sooner than expected. The downside is that it will lead me to ask even more stupid questions to this community…

        original
• habitualTartare@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  wireguard is self hosted and you do have to “expose” one UDP port. From the outside it’s difficult to detect that this “opening” exists because wireguard just listens and ignores everything unless you send the encrypted credentials. Compared to hosting a webpage or jellyfin directly this is much more secure. As long as you keep wireguard relatively up to date you don’t really have to worry much about it.

  I personally use wg-easy. It’s designed to be deployed into docker (using docker compose is by far the easiest).

  Then you can either use your IP address, or ideally a dynamic DNS provider so you’d connect to myexample.com:51820. Duckdns is free, otherwise options are available like cloudflare. If you can get jellyfin working, this should be relatively straightforward.

  original
• prenatal_confusion@feddit.org ⁨3⁩ ⁨weeks⁩ ago

  I was very skeptical because I didn’t want to punch holes into that nice safe lan. Pangolin got me in the end after I left tail scale with its easy docker for a cheap vps (1GB ram) and its approach in general.

  For example I am running my services locally in a docker via compose. I add a newt endpoint (pangolin talk) that is a docker container with some with info for my pangolin instance ton said compose and I have only the content of said docker compose connected via wireguard.

  Next step is exposing a public resource where you choose a specific service and port to map to a public URL.

  It is all so compartmentalized its fantastic and makes me feel good about that public service.

  Securing that service itself is possible with an additional auth layer.

  original