MyRemotingMyRemoting
Self-hosting quick start

Run your own MyRemoting server

It's your software — stand it up wherever you like. The control server is a single binary that handles coordination and the dashboard; the heavy traffic stays peer-to-peer over WireGuard and never touches it.

You'll need: a server (Windows or Linux) reachable on the internet, a domain name pointed at it (e.g. remote.yourcompany.com), and the ability to forward TCP 443. That's it — there's no inbound UDP to open for the control server.

1 · Install the control server

Windows / IIS
Linux
  1. Install the HttpPlatformHandler IIS module.
  2. Drop mr-control.exe and web.config into C:\myremoting\; set MR_BASE_URL to your https:// domain and MR_ENROLL_TOKENS to a secret.
  3. Create an IIS site on your domain and add HTTPS (win-acme gets you a free Let's Encrypt cert).
  4. Browse to /setup to create your first admin, then open Server → Readiness to confirm the outside world can reach you.
  1. Copy mr-control to the box and set MR_TLS_DOMAIN to your domain — it gets an automatic Let's Encrypt certificate.
  2. Install the provided systemd unit and start it; set MR_BASE_URL and MR_ENROLL_TOKENS.
  3. Browse to /setup for the first admin, then check Server → Readiness.

2 · Add a machine

From the dashboard's Add a machine panel, download the pre-configured installer, or create a shareable install link that drops machines into a group. Double-click it on the target PC and approve the Windows prompt — it installs the agent and screen service.

Download the agent installer

3 · Connect

Sign in from any browser or add the app to your iPad home screen, then control your machines — screen, files, console, registry, tasks, power, and more.

Not sure it's reachable? The control server's Readiness page asks our check service to connect back from the public internet and tells you exactly what's wrong — a closed port, a misconfigured domain, or a bad certificate — with a fix for each.

← Back to hosting options   Or have us run it for you