If it’s a time-based issue, it’s heat or memory.

If you can boot back to Windows and have no problems at all, that would be interesting.

Heat or memory issue.

Are your fans running?

We’ll need to see configs and IP assignments to be able to help.

They aren’t comparable being at completely different scales. Check https://diskprices.com/

Don’t mix your public and private DNS records. Use your public records for public things, and a local DNS forwarder for your local network.

A records only reference IPs and not ports.

SRV can be used to specify where to find ports, but the client needs to support those lookups to properly use it. You can use a reverse proxy or HTTP redirects to point things to different ports.

It stretches the player models out and makes them easier to hit I guess? Seems pretty stupid, but people do it.

If it fails it’s healthcheck, then it reports unhealthy. Check and see what it’s healthcheck is configure to be.

Doesn’t look like anything integrates with it yet except for something called Mastopod.

April Fool’s sure is super lame this year.

That’s not the issue, it’s the changing kernel extensions and passthrough methods of hardware. Causes hiccups from time to time.

You’ll definitely be struggling with that GPU, so maybe that’s a no-go.

At the moment, just VirtualBox for simplicity, but have run flat KVM for similar things in the past. It is FAR from ideal, but better than fucking with dual booting for myself. Also breaks a lot with Nvidia hardware.

Yes. Dual boot, or even simpler, try running your games in Windows VM in Linux. Performance hit should be minimal.

It’s kinda fun for what it is. The extra modes are great.

Great game, but I don’t know if playing on Deck is super ideal.

Well let me pull my case stud…no

Kubernetes doesn’t work with a GUI, and uses a stalwart config format for a reason. Relying on an “easier” way to do it will have unintentional consequences.

Try getting a job with “Well I know Kubernetes but only if I can use this particular GUI uhhhhhhh.”

No

Well an abstract from the real work might catch you in a weird spot, especially with the k8s world.

It’s certainly a GUI for a thing. What’s your question though?

Just kinda flipped through his guide. It’s a bit dated on knowledge and techniques, even for beginners.

You don’t need a computer for a router. Get a router that ships with OpenWRT and start there. GL.iNet makes good and affordable stuff. Use that for your ad blocking, VPN, and so on to get started.

I’d just skip OpenVPN altogether and get started with Wireguard or Headscale/Tailscale.

If you want to run other heavier services, start out with a low-power minipc until you’re settled on what your needs or limitations are. You can get a very capable AMD minipc for $250-300, or an n100 low-power for a bit cheaper. Check out Minisforum units for this. Reliable, good price, and solid warranty.

If you deal in heavy storage, maybe consider adding a NAS to the mix, but maybe that’s a further steps. OpenWRT is a good starting point just to get your basic network services and remote access up, then just move on from there.

A good and fun starting point for some people is setting up Home Assistant on a minipc or Raspberry Pi (honestly, the costs of Pi boards now is insane. Might be good just to get the minipc).