What kind of machine is this, laptop? Desktop? If desktop, check the cables. Otherwise I’d switch out the drive.

The request from the other machines go through the firewall and are being redirected, the requests from the NAS are basically trying to connect to localhost, so no redirection here as the requests aren’t leaving the machine.

Docker Gitea to Docker Forgejo was basically using a different image and pointing it to the existing database. Not sure if and when both will be different enough for that to no longer work. But I also only use it as a docker compose storage repository. No idea about automation etc.

What do you mean, “proprietary”? Don’t they connect via Bluetooth?

Wait, you update productions systems without running a staging environment? Or even checking the update notes and your installed apps? Also no backups? What kind of business are you running over there?

If setting up TLS is too much work, better stay with a service. Signal is nice.

It really depends on if you need transcoding or not. If no, it doesn’t matter. If yes, check for integrated GPUs on both models and check that it will work as a transcoder for jellyfin.

Kavita works well for me.

The idea is that the router plugs in to your home internet and the server into the router. Between the two they get the server able to handle incoming requests so that you can host services on the box and address them from the broader Internet.

Why would I need a separate router for that? I’d need to configure the main router anyway.

And you think this behavior magically goes away just because it’s a different language?

a motivated group of talented Rust OS developers could build a Linux-compatible kernel, from scratch, very quickly, with no need to engage in LKML politics

Riiight… Because those developers would always be of the same opinion… Good luck with that.

Which display size? How much storage?

Budget?

Sure, if you’d rather like to believe that.

The other bad news: there are so many vulnerabilities on all systems which can be used to gain root-level access, it’s just a matter of time. Also, even future vulnerabilities will be an issue, as the underlying Sinkclose attacks will still work.

Docker image is already updated.

Ah. Personally I’d do the mounting via fstab to get a consistent path.

How do you mount your volume?

I am unsure about sustainability

In what regard?

Apart from the world of trouble you might get yourself into when doing such things on secured systems, why are you going at it in such a complicated way?

Why not simply use a self hosted file/document storage and sharing solution like Nextcloud or Pydio Cells or something like that? Reachable through standard HTTP(S), which is a lot easier to reach than most other protocols.