Yeah that's exactly what I'd done but it was insisting on trying to redirect me to the site on port 4443 for some reason.
Fixed it in the end by reverting the NPM config to default (no advanced settings) and instead using Pihole's VIRTUAL_HOST=pihole.mydomain.internal environment variable in the Docker compose file.
Synology has Container Manager, which is their GUI frontend for Docker, so if it'll run in Docker it'll run on a Syno NAS. I'm running Pihole on mine just fine.
As for the M.2 drives, you can use non-Synology ones as storage. Don't quote me on it but I've a feeling it "just works" in the EU where they're not allowed to force you to use specific brands, but if it doesn't then there's a script that removes the restriction: https://github.com/007revad/Synology_enable_M2_volume
You should check their repo as they have other useful scripts. I'm using the one that enables dedupe on non-SSD volumes myself.
I'm using plenty of containers, accelerated and otherwise, but I also want a full-blown desktop that I can access from wherever. Even on a wired LAN, streaming that desktop is slow and laggy when it's hosted on my NAS, which I think is due to the lack of hardware acceleration on that system. I want to move the VM to a host that has that feature (currently running Ubuntu Server) but I need a hypervisor that doesn't require its own desktop system to be installed in order to manage it.
Well indeed, that's why I want to move the VM off the NAS and onto something with some hardware acceleration. Are there any remote frontend options for KVM?
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.
Yeah that's exactly what I'd done but it was insisting on trying to redirect me to the site on port 4443 for some reason.
Fixed it in the end by reverting the NPM config to default (no advanced settings) and instead using Pihole's
VIRTUAL_HOST=pihole.mydomain.internalenvironment variable in the Docker compose file.Cheers for your help anyway!