PC Remote

Secure remote PC control, QR-based device pairing, and Wake-on-LAN.

WPF
Android
TLS 1.2/1.3
Device keys
Trusted devices
WoL

Project overview

PC Remote separates the desktop UI, the Windows service, and the mobile client. New phones can only be added during a short pairing window, and every paired phone receives its own device key.

OKYou can revoke access from the app: remove one device from the trusted list or reset all pairings and rotate the keys.

How it works now

Show QR→ Short pairing window→ Trusted phone→ Protected commands

The QR code is only used to start a pairing session. After pairing, commands travel over TLS with certificate pinning, and the server accepts them only from devices that are already trusted.

Safer pairing

Only while the QR window is open

A new phone can be registered only while the QR window is open on the PC. Once the window is closed, new devices can no longer pair.

No permanent shared control key

The QR code no longer exposes a long-term control secret. After pairing, the phone receives its own device key instead of sharing one permanent key with every device.

Access management

Trusted devices list

The Windows app shows the phone name, first pairing date, and last access time. You can remove one device without manually editing files.

Reset all pairings

If a phone is lost, a QR code was exposed, or you want a full access reset, use the reset option. It removes every trusted device and generates new keys.

What this means for a regular user

Phone→ TLS + certificate pinning→ Windows service→ Command
ProtectionLocal secrets are protected on both Windows and Android, and pairing is now separate from normal control: you explicitly allow a new device first, then it works as a trusted one.

Setup guide

1

Prepare the PC

  • Enable Wake-on-LAN in BIOS or UEFI. Typical names are Wake on LAN, Power On by PCI-E, and disabling ErP if needed.
  • In Windows, open your network adapter settings and allow wake only by magic packet.
  • If you want a stable local address, reserve a fixed LAN IP for the PC through DHCP Reservation.
2

Pair the phone

  • Make sure the phone and the PC are on the same network.
  • On the PC, open the Security section, choose Show QR, and scan it right away from the phone app.
  • Pairing works only while the QR window is open. Once it is closed, new devices cannot be added.
3

Verify access

  • Enable local network mode on the phone if you want the app to use the LAN address.
  • Check that the phone appears in the trusted devices list and that last access updates over time.
  • If the device is no longer needed, remove it from the list. If you want a full access reset, use Reset pairings.
1

Prepare external access

  • Make sure your ISP gives you a public external IP. Compare the address from 2ip.ru with the WAN IP in your router settings.
  • If the ISP uses CGNAT, direct external access will not work unless you use a VPN or another tunnel.
  • Wake-on-LAN on the PC must be enabled the same way as in local mode.
2

Configure the router

  • Reserve a fixed local IP for the PC so the router rules keep pointing to the right machine.
  • Inside the local network, the app sends Wake-on-LAN to the standard UDP ports 7 and 9.
  • The Windows PC Remote service listens on internal TCP port 5055.
  • For PC Remote commands, you can forward external TCP port 5055 to the same local address, internal port 5055.
  • If you have two PCs in the same local network, use different external TCP ports. Example: external 60000 -> internal 5055 for one PC, and another external port -> internal 5055 for the second.
3

Make external access safer

  • The safest option is a VPN such as WireGuard or Tailscale, so you do not expose the control port directly to the internet.
  • If you use direct port forwarding, set up DDNS for a stable address and never share the QR code or screenshots of it.
  • For external Wake-on-LAN, use external UDP port 40000 in the usual case. On the router, you can forward it to internal UDP port 7 or 9 for that PC.
  • In the Android app PC settings, enter the actual external PC Remote port if it differs from 5055. For example, with a 60000 -> 5055 rule the phone must use port 60000.
  • If your public IP changes, update the address in the app or use DDNS instead of a raw IP.
4

Pairing and recovery

  • Open the QR code only when you are actually adding a new phone.
  • After pairing, review the trusted devices list and last access in the Security section.
  • If a phone is lost or you suspect a leak, remove that device or reset all pairings.
⚠️ If something does not work
  • A new phone will not pair if the QR window is already closed.
  • The PC will not wake if WoL is disabled in BIOS or in the network adapter settings.
  • External access will fail if UDP or TCP forwarding is missing, if the phone uses the wrong external port, or if the ISP gives you a private carrier-grade IP.
  • If the phone was reset or removed from trusted devices, pair it again with a fresh QR code.
💡 Recommendations
  • Use Ethernet when possible. Wake-on-LAN over Wi-Fi is often unreliable.
  • Do not keep the QR window open longer than needed for pairing.
  • If you are unsure whether access is still safe, use Reset pairings and pair your own devices again.