There’s only so much reliability you can build into a simple home setup without it being a major loss on investment. In a datacenter situation, you’d have fault tolerance on all the network ingress: load balancers, bonded interfaces, SDWAN configurations…etc.

Unless you want 3 of everything you own, just do the basics, OR I guess consider hosting it elsewhere 🤣

Focus more on why the service is going down, and solve for that. Make it reliable by restarting automatically in the face of failures. A Reverse Proxy should be dead simple, and not change states between restarts, so it shouldn’t be dying in the first place. Having it restart on failures should be simple and reliable.

Which file did you edit for these Grub changes?

Hmmm, it does seem they’ve finally raised prices. Well that’s a huge bummer.

I can’t say the 3 options you posted are really good deals, but maybe that’s just the market in Australia. I’d check to see what the max RAM in those are and upgrade to at least 16GB though. It should still be cheap for non DDR5.

Anything can be a “server” in your use-case. Something low power at idle will not cost an arm and a leg to run, and you can always upgrade later if you need more.

Check the Minisforum refurb store and see what you can get for under $150.

GRUB loads before any kernel driven hardware module, so this machine is just working on the native orientation of the CMOS and Display at that point.

https://wiki.gentoo.org/wiki/Tallscreen_Monitor

Seems to suggest that the fbcon argument should work, but which version of Grub you’re using matters. Make sure you update initd if using Grub2.

OHHH…you didn’t get an actual on screen prompt, you just decided to reinstall. My bad.

Wait…wha?

What prompted you to reinstall your ENTIRE OS? That should almost never be necessary under any circumstances.

1. dig , learn it, love it
2. Use a phone or other device outside your network to compare results from #1

They do no such thing.

The first link explains the protocol.

The second explains WHY one would refer to client and server with regards to Wireguard.

My point ties both together to explain why people would use client and server with regards to the protocol itself, and a common configuration where this would be necessary for clarification. Ties both of them together, and makes my point from my original comment, which also refers to OP’s comment.

I’m not digging you, just illustrating a correction so you’re not running around misinformed.

It wasn’t clear where OP was trying to make a point, just that the same host would be running running Wireguard for some reason, which one would assume means virtualization of some sort, meaning the host machine is the primary hub/server.

Honestly, I know a lot of people that do, but delivery address is less of a problem than other personal information.

I always make fake derivative versions of my names for anywhere I but from so I can tell who is selling my information and not buy from them anymore. The address matters less. I’m not avoiding the government and “hiding out” fo fuck’s sake, I’m just avoiding having my data leaked like this. Any number of fake names that like up on the same address also dilutes these data sets the shady dealers try and ship around. The more names at any single address reduce the confidence of its accuracy, and therefore price.

Uhhh, nooooo. Why are all these new kids all in these threads saying this crazy uninformed stuff lately? 🤣

https://www.wireguard.com/protocol/ https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/configuring_and_managing_networking/setting-up-a-wireguard-vpn

And, in fact, for those of us that have been doing this a long time, anything with a control point or protocol always refers to said control point as the server in a PTP connection sense.

In this case, a centralized VPN routing node that connects like a Hub and Spoke is the server. Everything else is a client of that server because they can’t independently do much else in this configuration.

Uhhhh…that is…not how you do that. Especially if you’re describing routing out from a container to an edge device and back into your host machine instead of using bridged network or another virtual router on the host.

Like if you absolutely had to have a segmented network between hosts a la datacenter/cloud, you’d still create a virtual fabric or SDLAN/WAN to connect them, and that’s like going WAY out of your way.

Wireguard for this purpose makes even less sense.

Why would you run a WG Client and WG Server on the same host? Am I reading that second mark wrong?

Never.Give.Companies.Real.Info.

Nginx, Traefik, Caddy, HAProxy…lots of options.

Nginx and Traefik are probably the most complex if you’re not familiar with either.

HAProxy is dead simple if you solely intend to just use it as a reverse proxy.

Caddy is fairly simple as well, but slightly more complex than HAP.

If you’re not familiar with routing and VPNs in general, you may want to have a look at Tailscale or ZeroTier which use Wireguard under the hood, but making the routing dead simple, especially if you’re behind a NAT and don’t want to have to mess with ports forwarding.

Just RMA it now. If it has SMART failures, you can provide the codes and they’ll replace it no problem.

Because those are different codebases packaged differently and need access to different things in your environment.

If the developer has a public GitHub, feel free to notify them, but this is likely not treated as a bug since it’s an issue with Flatpak and your permissions. If you run the project bare and it has this same issue, then it’s still an environment issue it seems. Probably not technically a problem with their code explicitly.

If it works, then just install Flatseal and put this an environment variable for the package. Will run without issue from them on.

From the logs it looks more like an issue getting to that dbus socket, which can also be tweaked with Flatseal.