ProbablePenguinB

Probably an SFF PC off ebay for $60 or so + a 10G NIC. Could run Opnsense, or OpenWRT if you wanted to.

That will not solve OPs problem.

IMO Nextcloud AIO is a mess that doesn’t work properly for anyone used to docker and docker networking. It makes lots of bad assumptions about how things are configured.

Managed to gain access to the container by using the docker virtual ip of the apache container, but i see this as no solution because the virtual ip can change whenever an update is applied.

The reverse proxy docs have something in the section “Running the Reverse Proxy in a Docker container on the same server”

It sounds like they want you to use network mode host on the NGP container which is dumb, but should work in theory. Then you can use localhost in NGP.

Proxmox itself uses about 1GB, so other than that you have the rest left over for everything else.

I’m a little confused why this would be needed, I only need the port during initial setup of a stack when I’m writing it and configuring the reverse proxy, once it’s running everything goes through the proxy and I never need the port again.

Are you seeing high IOWait? How did you determine that it’s an IO issue?

I can download/write + stream to multiple users off a HDD that’s MUCH slower than your SSD without any issues, so I suspect something else is going on.

Will a HDD work for my purposes?

HDDs are much slower than an SSD, like more than 30,000x slower on IOPS.

Ah, portainer gives me an error if one is, so I just mash the numpad and choose another.

Don’t forget that the modern approaches also make it much quicker and easier for someone to make something.

It’s just the ease of use, Tailscale sets everything up for you, keeps track of IPs so you don’t need to manually define endpoints, and handles NAT negotiation.

It’s the right choice, nextcloud is buggy af, the issue from years ago where it randomly corrupts files is still open too, I got hit by that one and had to completely restore from a backup.