Roomler blog
Why Roomler exists and how it is built: remote desktop from a browser tab, a private mesh network and team collaboration on one open-source agent.
How a SOCKS5 proxy works, and how to run one into your own LAN
What a SOCKS5 proxy does at connect time, why remote-side DNS matters, and how to run one from your laptop into a network only one of your machines can see.
How to securely access a home server with no open ports
Reach a home server from anywhere with no port forwarding: outbound-only agents, services by name or one tunnel, access rules rolled out in Warn mode first.
Reach a NAS and printer from anywhere with a subnet router
Set up a subnet router so your laptop reaches a NAS, printer and hypervisor from anywhere, and avoid the overlapping 192.168.1.0/24 trap and ACL denials.
How unattended remote access works on Windows, Linux and macOS
Skip the approval prompt per device, then pick the install that reaches a machine nobody is logged into on Windows, Linux and macOS, and where each OS stops.
What NAT traversal is, and how two machines pick a path through NAT
What NAT traversal means, the ladder from LAN to hole punching to a TLS 443 floor, why NAT-type guesses fail, and how to see which path a pair is on.
Remote desktop black screen: which permission or session is missing
Black screen, wallpaper only, or frozen at the lock screen: a session that connects but shows nothing is a capture problem. Match the symptom to the fix.
Self-hosted remote desktop with one Docker Compose file
Run a self-hosted remote desktop server from one compose file: real secrets, pull before up, TLS in your own proxy, and sessions your server cannot read.
Why remote desktop is slow, and the one check to run first
A sluggish remote desktop is almost always a relayed pair. One command tells you if the session is on LAN, Direct or Relay, then the causes in field order.
NetBird alternatives for self-hosters, compared by use case
What NetBird does better, then alternatives sorted by job: a hosted mesh, Tailscale clients on your own server, or mesh and remote screen from one agent.
Allow remote desktop through a firewall without inbound rules
Remote desktop through a firewall with no inbound rule: allow outbound TCP 443 to one hostname and outbound UDP for direct paths, then verify with netcheck.