Published April 14, 2026 on matbanik.infoNo Docker. No Pro license. Just two binaries and NSSM.
What You're Building
Two binaries — hbbs (ID/Rendezvous) and hbbr (Relay) — managed by NSSM as auto-start Windows services. Clients on your LAN connect through your server instead of RustDesk's public infrastructure.
Your server generates an Ed25519 keypair on first run. Every client needs the public key to trust your server. Lose the private key, regenerate everything.
---
Prerequisites
| Requirement | Notes |
|-------------|-------|
| Windows 10/11 or Server 2019+ | Tested on Windows 11 24H2 |
| Static LAN IP on the server | DHCP reservation works too |
| Admin access | Service installation requires elevation |
| RustDesk client installed | On both server and remote machines |
---
Step 1: Download Binaries
Create a dedicated directory. This guide uses C:\RustDeskServer\ — pick any path, but don't move it after service installation.
Why the dkxce fork? The original NSSM hasn't been updated since 2014. The official RustDesk documentation links to this maintained fork. Version 2.25 fixes critical service management issues on modern Windows.
---
Step 2: Generate Keys
Run
hbbs once manually to generate the keypair. Open an elevated PowerShell:
`powershell
cd C:\RustDeskServer
Start hbbr first (hbbs expects it)
Start-Process .\hbbr.exe -WindowStyle Hidden
Start-Sleep -Seconds 3
Start hbbs — replace YOUR_SERVER_IP with your static LAN IP
update_pk entries for each client that connects. If a client's ID shows as "does not exist" when you try to connect, that client hasn't registered with your server yet.
Both sides of every connection must use the same server. This is the #1 support issue.
AppNoConsole 1. This is a known NSSM issue on Windows 10/11 where console allocation fails in the service context. Without this flag, the service enters a start/stop loop with no useful error.
Keys/database appear in System32.
Set
AppDirectory to your server folder. NSSM defaults to the system directory as the working directory for services. hbbs writes its files relative to the working directory.
Service fails on boot, works fine when manually started.
Add
SERVICE_DELAYED_AUTO_START and DependOnService NlaSvc. The network adapter isn't ready when early-start services begin. Delayed start with a network dependency solves this.
"ID does not exist" when connecting.
Both the source and target machines must be configured to use your server. A client pointing at the public RustDesk servers has an ID that only exists there — your server has no record of it.
Don't run the RustDesk Server GUI wrapper alongside NSSM.
The
RustDeskServer.Setup.exe GUI installer and NSSM both try to manage the same binaries. Pick one. This guide uses NSSM because it survives reboots without requiring a user login.
The -k _` flag is not needed. Key-based authentication has been the default since server v1.1.11. Including it is harmless but unnecessary.
Relay server in client config is optional. When the relay server runs on the same machine as hbbs (the common case), clients auto-detect it. Only set this if your relay is on a different host.
Published December 15, 2024 on matbanik.info There's something about the rhythm of pedaling that quiets the noise in my head. The world shrinks to the road ahead, the burn in my legs, and the sound of my breath. The Appeal of Cycling Unlike running or gym workouts, cycling lets you cover real distance. You start somewhere, and you end up somewhere else. There's a journey, not just motion. Road vs Gravel I've ridden both, and each has its appeal: Road cycling is about speed, efficiency, and that feeling of gliding Gravel riding adds adventure—you never quite know what's around the next bend Building the Habit The key for me was making it easy. Bike ready to go, kit laid out the night before. Remove all friction between waking up and getting on the road. More rides to come as I explore new routes and push my limits. Originally published on matbanik.info . Cross-posted with ❤️ to Blogger.
Published February 22, 2026 on matbanik.info When I first heard "cloud commitment insurance," I nodded politely and had absolutely no idea what anyone was talking about. Insurance? For cloud commitments? What gets insured — the server? The discount? The contract? And who's the insurance company here? I had several sessions with the Archera team trying to wrap my head around it. Here's the thing that made it so confusing: their product is genuinely simple. So simple that the simplicity itself became the barrier. There was no complex architecture to diagram, no 47-step integration to plan. It just… worked. And my brain kept looking for the catch. This post is the guide I wish someone had handed me. It explains Archera through a single extended analogy that maps every concept to something you already understand. Then it walks through onboarding, monthly review habits, and — for the engineers who want to go deeper — how to connect your agentic IDE directly to ...
Published January 28, 2026 on matbanik.info Let me tell you about the worst part of my workday. It's not the hard problems. Hard problems are actually kind of fun — they're puzzles, and puzzles have solutions. No, the worst part is something much more mundane. It's Tuesday afternoon. I've got 30 tabs open. Three different documents all titled "final." A dozen notes scattered across apps. And somewhere in that mess — I know this for certain — is the one sentence that would unlock everything. The insight I had yesterday. The decision I already made. But I can't find it. So I start over. I re-explain the context. I re-derive the conclusion. I waste an hour getting back to where I already was. Sound familiar? Your AI Hero Assistant --- The Day Everything Changed Here's what I eventually figured out: my bottleneck was never ideas. It was never intelligence, or speed, or even time. It was state . I could see a complex system quickly — ...
Comments
Post a Comment