If you own a domain, which you do, you can get wildcard certs from Let’s Encrypt using a DNS challenge. Most (all?) popular reverse proxies can do this either natively or via an addon/module, you just need to use a supported DNS provider.

Wolf’s “tea” got me properly lolling. Nice one.

Libraries were simple enough, sure, but have you delved into the full settings? Trying to figure out the correct settings for QuickSync hardware acceleration was a mission in and of itself and there’s very little guidance on what any of the options mean or do. I don’t have the container running right now or I’d provide examples, but In Plex it’s a single checkbox.

I’m sure Jellyfin will get there and it’s a cool project, but it’s fairly obvious that it’s written by hobbyists, for hobbyists. Meanwhile Plex excels at just working straight out of the box.

Judging by the rest of the thread I’m going to get downvoted for this, but what the hell:

I’m sure I’ll switch to Jellyfin eventually but I tried it out a few weeks ago to see what all the hype was about and it just… wasn’t great. It was difficult to setup, with way too many overly-complicated settings, and then it refused to play one of the two test files I tried. Like it or not there’s a reason that Plex is the dominant player in the game, and a large part of that reason is that it verges on plug-and-play for simplicity of both setup and use.

Yes, it sucks that they’re removing remote streaming for free users, but I imagine there’s a significant chunk of users who don’t know or care how to properly open their server up to the world and are relying on the Plex proxies for their streams (which happens entirely in the background), and those aren’t going to be cheap to run. Maybe putting them behind a paywall will provide the resources to make them faster.

I did buy a lifetime pass last time they announced a price hike; it’s honestly paid for itself many times over, and I’ve been encouraging other users I know to do the same before this next one, because yes, it is a significant hike this time around. That said, while I wouldn’t pay monthly for it, I do still feel like the lifetime pass is tremendous value for such a polished product. It’s a shame they’ve had to do it at all, but I don’t begrudge them for it.

Good shout. I’ve just recently moved from Pihole to Adguard Home myself, complete with Hagezi lists. I consider myself very tech savvy and I work in the field but AGH suits my needs much better.

One example is wildcard DNS to route all of my hosted services via reverse proxy. In Pihole I had to make weird blocking rules to make this work, but AGH has specific settings for it. It also supports DoH out of the box, whereas Pihole needs non-standard faffery to get it working.

Very pleased with AGH in general.

HACS installs community integrations whereas addons are like external programs that hook in HA. You can do the same thing with HA in Docker by installing the addon containers separately and then hooking them in manually but HA OS makes it much simpler.

For example I’m running the Mosquitto broker, Z2M, a Visual Studio Code server, diyhue, and Music Assistant as addons.

Docco page about it is here: https://www.home-assistant.io/addons/

If you want to give Home Assistant a try like others are suggesting, save yourself some time and hassle and install Home Assistant OS in a virtual machine. While you absolutely can run it in Docker you lose out on some neat quality of life improvements like add ons (which, funnily enough, are Docker containers pre-configured to hook in HA).

Exactly this. Also it annoys me that Namecheap tries to automatically “top up funds” over a month before renewals are due. I think they’ve always done it but it wound me up enough this year to move to Cloudflare.

Yeah, everything that’s already been said, except that I specifically chose an off-the-shelf Synology NAS with Docker support to run my core setup for this exact reason. It needs a reboot maybe once or twice a year for critical updates but is otherwise rock solid.

I have since added a small N100 box for things that need a little extra grunt (Plex mainly) but I run Ubuntu Server LTS with Docker on that and do maintenance on it about as often as I reboot the NAS.

Were you talking about MacOS? It’s been a long time since I last had to use it but I assumed it was case sensitive because it’s Unix based. Uh maybe ignore me then!

NTFS absolutely supports case sensitivity but, presumably for consistency with FAT and FAT32 (Windows is all about backwards compatibility), and for the sake of Average-Joe-User who’s only interaction with the filesystem is opening Word and Excel docs, it doesn’t by default.

All that said, it can be set on a per-directory basis: https://learn.microsoft.com/en-us/windows/wsl/case-sensitivity

Just to add to the info so far: while you’re spending the effort doing a migration it’s worth going the extra few steps and moving to their Docker image. It’ll make any future server moves a doddle, not to mention updates etc.

Isn’t that exactly why so many of these company and app names have missing vowels? Because they can’t trademark a word but they can trademark a collection of letters that sounds like a word when spoken aloud. It’s really dumb.

Also the first thing that popped into my head. I know EVA was just a voice but teenaged me had the hots for her.

2. Sure but there’s no reason to openly advertise that yours has open services behind it.
3. Absolutely. There are countries that I’m never going to travel there so why would I need to allow access to my stuff from there? If you think it’s nonsense then don’t use it, but you do you and I’ll do me.
4. See point 3.

We all need to decide for ourselves what we’re comfortable with and what we’re not and then implement appropriate measures to suit. I’m not sure why you’re arguing with me over how I setup my own services for my own use.

Admittedly I’m paranoid, but I’d be looking to:

1. Isolate your personal data from any web facing servers as much as possible. I break my own rule here with Immich, but I also…
2. Use a Cloudflare tunnel instead of opening ports on your router directly. This gets your IP address out of public record.
3. Use Cloudflare’s WAF features to limit ingress to trusted countries at a minimum.
4. If you can get your head around it, lock things down more with features like Cloudflare device authentication.
5. Especially if you don’t do step 4: Integrate Crowdsec into your Nginx setup to block probes, known bot IPs, and common attack vectors.

All of the above is free, but past step 2 can be difficult to setup. The peace of mind once it is, however, is worth it to me.

Make an offer of $0.01. Assuming the responses aren’t automated, every time they reject it, raise the offer by 1c. Keep doing it till you hit the $15 mark and then just stop. It could waste literal years of their time.

A VPS makes sense insofar as keeping things thoroughly isolated from my own systems, but the overhead of maintaining a box that’s directly connected to the Internet like that isn’t something I’m keen on and I’m not convinced I’d have the expertise to do it right from the outset.