TedZanzibar

joined 1 year ago
[–] [email protected] 0 points 2 weeks ago (4 children)

Problem solved! If we ignore the world's ~300 million colorblind people.

[–] [email protected] 1 points 1 month ago

To be fair the Synology lineup is confusing, but if you get the right model - one with a Ryzen processor and support for 32GB memory (officially; they can take more) - then you've got yourself a proper little workhorse with low power consumption, a stable, reliable OS, and super easy expansion thanks to the hot-swap drive bays and their Hybrid RAID option. My 8 bay model is running a couple of full-blown VMs and what must be two dozen or so docker containers while barely breaking a sweat. The DS723+ is the equivalent 2 bay model.

For things that need some acceleration like Plex and Immich I've added a little N100 box (a Beelink S12 Pro) with Ubuntu Server and another Docker instance, and mounted the NAS storage via SMB. This also sips power even when transcoding 4x Plex streams at once.

All of which is to say you don't need to do a complex, potentially power hungry and difficult to expand self build to do what you want.

[–] [email protected] 2 points 1 month ago

Neither does the BBC's couch to 5k app, for who knows what reason.

[–] [email protected] 1 points 1 month ago

You are a legend, thank you!

[–] [email protected] 1 points 1 month ago (2 children)

Any chance of a link to the clip?

[–] [email protected] 4 points 3 months ago (1 children)

Unless you're hosting VHDs and need maximum throughput (in which case use NFS), SMB is going to be the easiest to setup and maintain across those 4 platforms.

The Linux SMB implementation is decent and supports the latest version of the protocol (or close to, at least) whereas NFS in Windows ain't so great and is a bit of a pig to get working in my experience.

[–] [email protected] 1 points 3 months ago

Thanks, I'll muse over this when I next get the chance!

[–] [email protected] 0 points 3 months ago (2 children)

Yes please, I might revisit it with a fresh pair of eyes.

[–] [email protected] 1 points 3 months ago (4 children)

Thanks for the suggestion. I spent a good hour or two trying to make Wireguard work for me last night but failed. If I set it to only apply to Immich, nothing else would have Internet access at all. Likewise if I set the peer IP range to just my LAN subnet.

After pulling my hair out for a while I gave up and uninstalled.

[–] [email protected] 1 points 4 months ago

Hmm I must be doing something wrong then because it doesn't work for me.

[–] [email protected] 2 points 4 months ago (6 children)

If it was just me, or if Tailscale wasn't such an insatiable battery leech then I'd absolutely do that but the wife (and kids) acceptance factor plays a big role, and they're never going to accept having to toggle a separate service on and off to get to their photos.

Maybe I'm being overly paranoid but I work in IT and see the daily, near constant barrage of port scans and login attempts to our VPN service and it has an effect!

[–] [email protected] 1 points 4 months ago

Very useful insights, thanks.

I do currently have external stuff running via a Cloudflare tunnel (which is why I need DNS based LE certs for the internal proxy) but I don't know if it's setup correctly (beyond doing basic reverse proxying) and the admin backend for it feels like massive overkill for a home setup. Plus with Immich I run into the issue of a) dire warnings about it being in active dev and potentially insecure and b) filesize limits making away-from-home backups difficult.

I could well be over thinking the whole thing.

 

Specifically from the standpoint of protecting against common and not-so-common exploits.

I understand the concept of a reverse proxy and how works on the surface level, but do any of the common recommendations (npm, caddy, traefik) actually do anything worthwhile to protect against exploit probes and/or active attacks?

Npm has a "block common exploits" option but I can't find anything about what that actually does, caddy has a module to add crowdsec support which looks like it could be promising but I haven't wrapped my head around it yet, and traefik looks like a massive pain to get going in the first place!

Meanwhile Bunkerweb actually looks like it's been built with robust protections out of the box, but seems like it's just as complicated as traefik to setup, and DNS based Let's Encrypt requires a pro subscription so that's a no-go for me anyway.

Would love to hear people's thoughts on the matter and what you're doing to adequately secure your setup.

Edit: Thanks for all of your informative replies, everyone. I read them all and replied to as many as I could! In the end I've managed to get npm working with crowdsec, and once I get cloudflare to include the source IP with the requests I think I'll be happy enough with that solution.

 

I work in tech and am constantly finding solutions to problems, often on other people's tech blogs, that I think "I should write that down somewhere" and, well, I want to actually start doing that, but I don't want to pay someone else to host it.

I have a Synology NAS, a sweet domain name, and familiarity with both Docker and Cloudflare tunnels. Would I be opening myself up to a world of hurt if I hosted a publicly available website on my NAS using [insert simple blogging platform], in a Docker container and behind some sort of Cloudflare protection?

In theory that's enough levels of protection and isolation but I don't know enough about it to not be paranoid about everything getting popped and providing access to the wider NAS as a whole.

Update: Thanks for the replies, everyone, they've been really helpful and somewhat reassuring. I think I'm going to have a look at Github and Cloudflare's pages as my first port of call for my needs.

 

Hey there, my local instance has had two admin posts pinned for the last 6 months-ish and they show right at the top of my Subscribed, Local, and All views. I can't imagine they're going to get un-pinned any time soon, so it would be great to get a feature where we can hide them.

Thanks for the consideration!

view more: next ›