Yes, there’s no need to do all that. Point radarr at your existing library and use the library import page.

If it gets in the way of you being able to do things, it’s too much.

From your requirements, coreboot is probably the most limiting factor, so I would start there.

Assuming they use NAT. Almost certainly true for IPv4, very unlikely for IPv6. And you should have a firewall too.

That’s the neat part. I don’t!

I have automatic updates on everything, but if I actually spent time managing updates and vulnerabilities I’d have no time to do anything else in my life.

I know of Onlyoffice, but I haven’t used it personally: https://github.com/ONLYOFFICE/DocumentServer

It was there this morning, gone now. I guess they’re reading these comments.

I’ve had this site bookmarked for a while, but I’ve not actually evaluated them: https://lowendbox.com/

imagemagick is the swiss army knife: https://usage.imagemagick.org/crop/

Terminal user interface. Way back before we had GUIs, we had line drawing characters for text graphics.

Honestly you might. I bring my earplugs any time I go into the server room. And a jacket, because it’s nipple-crinkling cold in there. Or I stand in the hot aisle next to the SANs while I’m waiting for something.

Servers aren’t all that different from regular PCs. Plug in at least one PSU, boot install media, install your OS and off you go.

The neatest feature is the idrac. Hook that up to the network (and use the front panel to make sure it’s on DHCP) and you can do a lot of remote control, even get a virtual console, just like having a monitor, mouse, and keyboard.

Note that the R720 is rather old at this point. I’d install Windows first, and put the service tag in on Dell’s support site, and update all the firmware. There are other ways, but that one requires the least fiddling.

Also, once you have it up and running, you can see power consumption in the idrac.

And the fans will be pretty loud, so you’ll want to set up the idrac and use ipmitool to control them. I used to set mine to about 20%. You will need to do this on each cold boot (but not warm reboots). https://serverfault.com/questions/1025601/control-or-reduce-fan-speed-of-dell-r820

You’ll have to look by pid or command line.

And ports are per-protocol. Some DNS servers use TCP 53 and UDP 53, for example.

Misquotes are unlikely thanks to copy-paste. The post from Plex has been edited, so I think it was to correct that typo.

Or even the Lemmy search, because it’s been discussed here before.

The nginx host is the VPN client in this case, so it’d be connecting to itself. You need to point it to the host on the VPN server side network.

Right. How are you routing traffic from nginx?

You’ve confirmed I’ve understood it correctly. Someone on the Internet requests your site. They reach your VPS with nginx. So far so good. Now, how does nginx know how to reach the upstream service?

VPN setup on VPS with successful routing of containers. Confirmed by using a CLI IP check within the container which returned the VPS IP

If you want to route traffic from the VPS over the VPN, and the check returned the IP address of the VPS, this confirms it is not working. You need to configure your VPS to route traffic over the VPN. Personally, I’ve done this in the reverse direction (routing local qbittorrent to a public VPN) with gluetun.

I am happy to hold your hand through administering your server, but my support rates start at $120/hr.