Burn1ngBull3t

u/Burn1ngBull3t@lemmy.world
6 posts · 39 comments

Recent posts

Recent comments

I would agree, but as usual bollards are, in-fine, infrastructure for cars at the expense of cyclists and pedestrians.

IMO, they should remove the road all together 😄

For me, it was the biggest announcement from that and probably the reason i might invest in the Steam Frame.

That way I support Valve (or more like “i agree with that so here is my money) going the way of ARM support for Linux, the same way I bought the Steam Deck to “support” Proton translation layers.

on removed a homeplug · c/selfhosted · 3 pts · 341d

I did switch from homeplugs to mesh wifi. The difference night and day. Less latency, faster and overall more stable.

I arrived at that conclusion because my servers were using a NAs as storage for most services, all of them separated by homeplugs.

When I relocated the NAS with the servers, everything went smoothly so yeah. Removed all of that and used mesh wifi instead (because the line for internet isn’t in the same room as the servers)

Many issues this week:

  • Broke external-dns on my kube cluster because I updated my Pihole to v6
  • Thinking of a way to expose a game server externally (usually used CF tunnels for specific services, but couldn’t get it to work cause it’s TCP/UDP and not HTTP traffic)

But at least i got my Velero backups working on an private S3

Either tailscale or cloudflare tunnels are the most adapted solution as other comments said.

For tailscale, as you already set it up, just make sure you have an exit node where your services are. I had to do a bit of tinkering to make sure that the ips were resolved : its just an argument to the tailscale command.

But if you dont want to use tailscale because its to complicated to your partner, then cloudlfare tunnels is the other way to go.

How it works is by creating a tunnel between your services and cloudlare, kind of how a vpn would work. You usually use the cloudlfared CLI or directly throught Cloudflare's website to configure the tunnel. You should have a DNS imported to cloudflare by the way, because you have to do a binding such as : service.mydns.com -> myservice.local Cloudlfare can resolve your local service and expose it to a public url.

Just so you know, cloudlfare tunnels are free for some of that usage, however cloudlfare has the keys for your ssl traffic, so they in theory could have a look at your requests.

best of luck for the setup !