I edited, since it was ambiguous. I think you only need zfs if you want replication, cold migrations should be fine without it.
Removing nodes from clusters is fine. It’s not really encouraged, but if a node fails you have to be able to remove it, so it’s possible.
The upstream refused the connection. You have it there as 127.0.0.1, but for inter-container communication usually you’d use the name. 127.0.0.1 would refer to the same container.
Docker (and other container platform) networking is a bit tricky and I’ll admit I don’t fully understand how it works, because it doesn’t work like regular networking. But a simple scenario like yours shouldn’t be difficult.
You could even just create a cluster and do a migration. I don’t think you need zfs for that, you only need zfs for replication.
What’s in the logs?
Fun fact, a malicious server can detect the difference between you loading the script for inspection in your browser, and you doing curl | sh, and could serve an entirely different script.
No, package installers support configuration. Plenty of packages (e.g. postfix) prompt for configuration at install time.
I’m not installing OP’s CA cert just to view his blog.
There is plenty of backup management software. You want one that will not only keep a copy of your data, but also save you in the event you accidentally delete one or more files.
I’d upgrade the NAS to full server status and run everything from there. For most people, there’s not much point in separate devices. It just adds a point of failure.
Not many flags. Nothing in the behavioral analysis makes me suspicious. Just looks like an installer.
It doesn’t fit everyone’s use case.
I think you have two goals at odds with each other.
I had a longer reply typed out, but I guess the network ate it. The gist was to consider a second low power device for the always on services that don’t need the big noisy storage.
First of all, a NAS VM is generally considered a bad idea that has been discussed before so I won’t repeat it here.
Anything using those drives is going to keep them awake. Usually, NAS software runs background tasks, as does proxmox. You’ll have to identify and schedule them to shut down during sleep hours.
But that’s going to be a huge pain, because eventually you’ll find it’s gone to sleep when you haven’t, and you want access. I’d see if you could configure proxmox to suspend the VMs and put the whole thing to sleep when you push the power button.
Looks fine to me (Firefox 142.0.1 on GrapheneOS 2025081400 on a Pixel 8).
I’ve seen worse. That shouldn’t have overheating problems.
€530,000 still seems high, but it’s good that it’s only a fine. There’s no good reason to imprison someone that does not pose a danger to the public.
You haven’t given much detail to go on. I’m pretty sure proxmox has a support dump button (I’m out of the house right now so I can’t check), but you could at least do lshw, lspci, etc., and the VM config file.
You might get better answers from the proxmox support forum. It’s more active than Lemmy.
If your request is showing up in nginx’s log, it means you can reach nginx. The upstream is where nginx is going to get the content you want. In your case, that should be the other containers.