friendly neighborhood kbin.run admin, possibly a sentient lifeform… likes pizza and beer.

professional pixie wrangler and rf magician

Mbin contributor and maintainer, aka nobodyatroot on GitHub.

support kbin.run, visit the FAQ page for ways how! ❤️

  • 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle





  • kbin.run admin here, i’m curious if this cert problem is still happening as i recently loosened up some of my super strict bot killing mechanisms… give it a shot again and DM me if it still doesn’t work so i can try to figure out what’s going on.

    as for the name… yea, i should have named it something different. at the time, kbin was the only horse in town and the intent was to help alleviate some traffic from .social before the foundation took over to run it on their cluster… then things fell apart. unfortunately, i can’t rehome it to a new domain because it will break federation of all existing content, accounts, etc.




  • debounced@kbin.runtoSelfhosted@lemmy.worldRemote desktop
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    9 months ago

    i use Tailscale on everything these days (or use Headscale if you want to self host the control plane). with the free plan you get up to 100 devices on a “tailnet”, just set the right ACLs to only allow the remote connection ports of choice, pair it with self hosted RustDesk, and you should be good to go. the NAT traversal of Tailscale is pretty good from what i’ve observed, but sometimes you might get stuck on a relay (called a DERP) if it can’t get across the firewall(s).