As for alternatives, I’ve heard lots of good things about Tailscale (or headscale if you want to self host).
If them connecting to you is an option, WireGuard is also stupidly easy to set up and very reliable. If you need to also forward layer 2 traffic (old LAN games and weird local protocols), you can use OpenVPN for that. A bit hard to set up but also quite capable.
Unfortunately that trace isn’t very useful due to the lack of debug symbols. One would have to decompile and analyze the binary to really gather some information as to how that happened, and it’s probably against their TOS.
hamachi will occasionally disconnect *and then ask for my password to restart the service. *
The GUI is probably trying to restart the daemon for you which causes this, because that’s not standard behaviour. You can probably fix that but just allowing your user to do that passwordless, although it’s dumb:
# /etc/polkit-1/rules.d/50-hamachi.rules
polkit.addRule(function (action, subject) {
if (
subject.user === "YOURUSERNAMEHERE"
&& action.id === "org.freedesktop.systemd1.manage-units"
&& action.lookup("unit") === "logmein-hamachi.service"
) {
return polkit.Result.YES;
}
})
You’ll want to change your username in there and also adjust the service name if it’s different.
When you subscribe to a community, you only start receiving data from that point on. It doesn’t go and download the history, that’d be very resource intensive on the remote instance. Thus it fetches a handful of posts, and no comments as a preview of the community, and after a couple days of activity is looks mostly normal.
I would probably just skip the Lemmy Easy Deploy and just do a regular deployment so it doesn’t mess with your existing. Getting it running with just Docker is not that much harder and you just need to point your NGINX to it. Easy Deploy kind of assumes it’s got the whole machine for itself so it’ll try to bind on the same ports as your existing NGINX, so does the official Ansible as well.
You really just need a postgres instance, the backend, pictrs, the frontend and some NGINX glue to make it work. I recommend stealing the files from the official Ansible, as there’s a few gotchas in the NGINX config as the frontend and backend share the same host and one is just layered on top.
And I’m too hungry to make that decision let alone take on the cold to obtain the food in question.
Technically a lot of the newer chips used in datacenters support encrypted VMs which encrypts the RAM too, although you still have to trust that the hosting provider uses that feature.