• 11 Posts
  • 299 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle



  • The audacity of this company to increase prices when:

    A) downloads are locked behind the paywall but havent worked in years (probably close to a decade at this point)

    B) they focus all the development time on bringing bullshit to the platform (live tv, rentals, other streaming app searches, etc)

    Requiring a subscription for remote access is actually fucking insane, they don’t have any bandwidth costs associated with that other than authentication so ???

    This will drive people to Jellyfin, and watch how fast Plex drops into irrelevance when all the selfhosters move away. Plex is (now was) the #1 thing to that both myself and others in this community would recommend to someone looking to get into selfhosting. ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯ not anymore, wonder how much the revenue will drop?


  • $1k for the base isn’t horrible IMO, especially if you compare it to something like the mac mini starting at $600 and ballooning over $1k to increase to 32GB of “unified memory” and 1tb of storage.

    I get why people are mad about the non-upgradable memory but tbh I think this is the direction the industry is going to go as a whole. They can’t get the memory to be stable and performant while also being removable. It’s a downside of this specific processor and if people want that they should just build a PC



  • Hey, can you elaborate a little bit more? Based on my Google search, casa-os is a front end for selfhosting? So, I would assume that you are not connecting to the right ports.

    So, my assumption is: casa-os is using your port 80 and 443, so when you set up the DNS A Record, and navigate to it in your browser, it takes you to the homepage for casa-os. If this is indeed the case, then you have a couple options. You could:

    1. Change the ports that casa-os is using and then rebind NGINX to 80 and 443
    2. set up a second device just for NGINX (which is what I do, I use a Raspberry Pi just for network entry for stability reasons)
    3. (I’ve never done this, so YMMV) you might be able to use Tailscale Serve
      • You would have it serve the port for NGINX under your Tailscale DNS name
      • Once you’re there, I imagine that you could use a CNAME DNS record or something on your custom domain in order to continue using the domains that you want, sub domains, SSL, etc.

    Let me know what ends up working for you. I hope that either option 1 or 3 work, if those fail then you can definitely get it working via option 2 :)













  • Ahhh i gotcha, so basically it forwards traffic through the pi so that you can send traffic through tailscale on devices that don’t support it? Sounds like a cool idea tbh

    Good on ya for the tailscale/syncthing though, off-site backups are super important! If Jellyfin supported federation you could merge your library and your parents library and have it all accessible through each of your local instances. Maybe one day they’ll add it, i think it would be a killer feature.

    Glad the write-up helped though, it should at least help you move towards single instances (at least for immich) since you can just backup on tailscale via the dns entry!


  • Glad to help, yes that is a perfect example of how you could use this to your benefit. Much easier to just tell people to enable VPN (tailscale) and navigate to an easy to remember URL.

    I’m somewhere in the middle, I do cybersecurity professionally so i work a lot with technical stuff but my hobbies are much deeper in it so theres a lot of stuff i don’t know. But, thanks to these communities i was able to learn how to do a lot of things and have now levelled up into doing the research on my own and trying to give back :)

    In your dream scenario, is that each family member would be hosting immich/jellyfin on their pi zero? Or is the pi zero somehow routing traffic for them back to your server for jellyfin and immich?