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.

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.

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.

Third Plex. It’s a bit baffling as to why it’s got such a bad rep recently because it performs its core function of serving media incredibly well, is super easy (barely an inconvenience) to setup, and there’s apps for every conceivable platform.

Yes there’s a few features locked behind a subscription (though they still sell lifetime passes, often at good discounts) and they’re trying to “legitimize” with their ad-backed streaming thing, but the core product of local media server is still very much there, and free, and isn’t going anywhere.

Yeah that’s cool and all but you’re strawmanning. Your original comment, that I hear parroted a lot, is that Telegram is (basically) unencrypted, and regardless of your feelings about the suitability of MTProto (not SSL) that’s patently untrue.

There’s no evidence that MTProto has ever been cracked, nor any evidence of them selling or allowing anyone access to their servers and recent headline news backs this up. Whether you choose to trust them with your data is up to the individual to decide. I’m just tired of seeing the “Telegram is unencrypted” claim in every instant messaging thread, made by people who don’t know or care to know the difference between encryption and E2E encryption.

Google, on the other hand, routinely allow “agencies” access to their servers, often without a warrant, and WhatsApp - who you cite as a good example of E2E encryption - stores chat backups on GDrive unencrypted by default. They added the option to encrypt last year but nobody was forced (or possibly even asked?) to turn it on, and to this day no encryption of backups is still the default. And while you might encrypt your backups, can you be sure the same is true for the people on the other end of your chats?

I’m not sure what point you’re trying to make? The people that claim “Telegram is unencrypted” seem to be of the belief that literal plaintext is flying over the air for anyone with a mediocum of knowledge to easily intercept, and that’s just not true.

Lacking end-to-end encryption does not mean it lacks any encryption at all, and that point seems to escape most people.

To take it to its logical conclusion you can argue that Signal is also “unencrypted” because it needs to be eventually in order for you to read a message. Ridiculous? Absolutely, but so is the oft-made opine that Telegram is unencrypted.

The difference is that Telegram stores a copy of your chats that they themselves can decrypt for operational reasons. It’s up to the user to decide whether the additional functionality that comes with this is worth the risk of a hostile agent successfully requisitioning those chats directly from Telegram themselves, rather than just busting through your door and threatening to break your legs if you don’t unlock your phone.

On the other hand, if you fill your Telegram hosted chats with a whole load of benign crap that nobody could possibly care about and actually use the “secret chat bullshit” for your spicier chats then you have plausible deniability baked right in.

Thank you! It winds me up so much when people parrot that claim.

Telegram is encrypted in transit and encrypted at rest on their servers. At no point is any data stored or transmitted without encryption. Whether you believe their claims of never giving out encryption keys is another matter.

My view is that if the feds wanted my chat logs that badly they wouldn’t go after Telegram, they’d go after me and my device directly, and at that point all bets are off.

Webtop. Lightweight Linux VMs but in Docker.

That’s… A lot of storage. I’d say your options are, in no particular order:

• buy a 12 bay NAS.
• expansion unit. Do it as a separate volume and shuffle cold data onto there.
• upgrade the drives.

Failing that you could just have a bit of a purge? If not straight deleting stuff, move things onto an external drive.

You could also try deduping. There’s a script that’ll add any drive to the internal “supported” list and also enable dedupe on mechanical drives. The savings were minimal on mine but you might have more luck. https://github.com/007revad/Synology_enable_Deduplication

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.

Yes and no? It’s not quite as black and white as that though. Yes, they can technically decrypt anything that’s been encrypted with a cert that they’ve issued. But they can’t see through any additional encryption layers applied to that traffic (eg. encrypted password vault blobs) or see any traffic on your LAN that’s not specifically passing through the tunnel to or from the outside.

Cloudflare is a massive CDN provider, trusted to do exactly this sort of thing with the private data of equally massive companies, and they’re compliant with GDPR and other such regulations. Ultimately, the likelihood that they give the slightest jot about what passes through your tunnel as an individual user is minute, but whether you’re comfortable with them handling your data is something only you can decide.

There’s a decent question and answer about the same thing here: https://community.cloudflare.com/t/what-data-does-cloudflare-actually-see/28660

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.

Better than using what? All I see is a bunch of stars.