InnerScientist

It was all just bloat anyways, who needs anything besides a kernel?

Check DNS, MTU and do a full wireshark capture from the Client using both curl and the browser.

You must be at Least this high to work here.

Great! Now I can play frogger from both perspectives at once.

I have a failsafe service for one of my servers, it pings the router and if it hasn't reached it once for an entire hour then it will reboot the server.

This won't save me from all mistakes but it will prevent firewall, link state, routing and a few other issues when I'm not present.

I didn't consider it as valid, one on (phone and internal nvme1), the second one on nvme2 and the third one in the cloud.

Though I have only two copies of normal data myself, I consider live and cloud to be enough for most data. Everything very important has more backups in other ways (bitwarden has an exportable local version on every logged in device, images are stored in immich on my server making it 3 devices)

• Maintain three (3) copies of your data: This includes the original data and at least two copies.
• Use two (2) different types of media for storage: Store your data on two distinct forms of media to enhance redundancy.
• Keep at least one (1) copy off-site: To ensure data safety, have one backup copy stored in an off-site location, separate from your primary data and on-site backups.

You have 3 copies, one on your phone and nvme, one on the backup nvme and one in the cloud. You have 2 media, internal SSD and cloud (your phone would count as a third if it wasn't auto synced) You have 1 off-site in the cloud

Or use the ublocklist extension, this puts a button besides all search results to perma ban that domain and allows URL lists like this for automatic garbage removal.

Find a new service you like, add it using rootless podman. That way you can test it without affecting your running system.

The buff/cache will free automatically when an application needs ram, until then it's useful for speeding up the system.

Try sysctl -w net.ipv4.conf.all.rp_filter=2 on the PC (not vps) or =0 if that doesn't work

Do a ping of 8.8.8.8 from your user, then open a new console and run tcpdump -i with first your uplink, then wg0. The packets should be seen on wg0 if they're routed correctly and the problem then is on the vps side. Otherwise it's a problem on your local config.