PCLink - Documentation
Loading...

PCLink: Remote Telemetry Documentation

The Definitive Guide to Secure PC Remote Control and Execution

Overview

Welcome to PCLink. This guide will walk you through configuring and utilizing PCLink to securely control and monitor your PC from a browser or your mobile phone.

PCLink is a web-first server that turns your desktop into a remotely accessible machine with features like file browsing, terminal access, and peripheral control. It utilizes a zero-trust security model, meaning every new device must be manually cryptographically approved by you before execution sequences are allowed.

Video Tutorial

The fastest and most robust way to master PCLink’s core capabilities—including establishing secure zero-trust connections, remote execution, and monitoring live telemetry—is through our official interactive tutorial.

1. Prerequisites

  • The Host PC: The computer you want to control remotely (Windows, Linux, or Arch).
  • A Controlling Device: Any device with a modern browser (desktop, laptop) OR the PCLink Mobile App (Android).
  • Network: Both devices must exist on the same network sequence, or you must configure port forwarding (advanced) for remote access over the broader internet.

WARNING

Important Antivirus Notice PCLink performs deep system actions (native API screen capture, remote input). Security software like Windows Defender may aggressively flag it as a false positive (e.g., Wacatac.B!ml). The project is 100% open source. If this occurs, you must add an exclusion matrix in your localized antivirus software.

2. Host PC Installation

Choose your operating system architecture. The server is the core headless component that runs on the machine you want to control.

Windows Architecture

  1. Navigate to the GitHub Releases page.
  2. Download the compiled .exe installer (e.g., PCLink-Setup-x.x.x.exe).
  3. Execute the installer and follow the standard prompt pipeline.

Linux (Debian/Ubuntu)

Automated Script (Recommended) : Open a terminal and run the curl script:

bash <(curl -fsSL https://raw.githubusercontent.com/BYTEDz/PCLink/main/install.sh)

Manual Execution: Download the .deb or .rpm package block from the Releases page and install it using your package manager (e.g., sudo dpkg -i pclink*.deb).

Arch Linux

Install from the AUR using your preferred helper daemon:

yay -S pclink

3. Initial Configuration & Launch

After installation, the PCLink daemon must be initialized to create your first local connection pool.

  1. Start the Server:

    • Windows: Launch “PCLink” from the Start Menu wrapper.
    • Linux/Arch: Execute the command pclink in your terminal.

  2. Access the Web UI: On the same host PC, open your browser and navigate to: https://localhost:38080/ui/

    • Note: You will see an SSL warning because the encryption certificate is self-signed natively. This is standard protocol. Proceed to the site (click “Advanced” -> “Proceed to localhost”).

  3. Administrator Password : The initial connection event will prompt you to inject an administrator password for the Web UI. Save this sequence.

  4. Host QR Matrix: Once authenticated, the main dashboard will render a unique QR code. This code represents your host PC tunnel. Leave this page open.

NOTE

Troubleshooting Protocol If you cannot access https://localhost:38080/ui/, ensure no background service is occupying port 38080. Verify your internal firewall parameters allow PCLink traffic.

4. Device Pairing Sequence

PCLink requires explicit zero-trust approval for every new macro device.

  1. Install the PCLink Mobile App onto your Android device from the official repository or Play Store.
  2. Launch the mobile app.
  3. Tap “Scan QR Code” and point the camera block at the QR code rendered on your Host PC’s Web UI.
  4. On the Host PC Web UI, a new connection manifest will arrive. Click “Approve”.
  5. Your mobile device is now securely keyed and can control the PC.

Phase B: Remote Browser Pairing

  1. On your remote laptop/desktop, open a browser and navigate to https://<YOUR_HOST_PC_IP_ADDRESS>:38080/ui/.
    • Extract your host PC’s static local IP address (e.g., 192.168.1.100) from your router’s network settings.
  2. Authenticate using the admin password injected earlier.
  3. You will see a “New Device Detected” prompt on the host PC’s primary Web UI (at localhost). Approve it.
  4. The remote browser session has acquired host control.

CAUTION

Internet Remote Access To control your PC from outside your native network, you must establish port forwarding on your router for port 38080 (TCP) targeting your host PC’s local IP address. This carries extreme security vectors; we mandate utilizing a zero-trust VPN (like WireGuard) for external network bridges instead of raw port exposure.

5. Core Operational Features

Once cryptographic pairing is concluded, your controlling device will yield an active command dashboard.

Feature ClassificationExecution CapabilityInterface Access
Peripheral SyncNative control of remote mouse, keyboard, volume, and media playback APIs.Main control panel / Mobile app touch matrix.
Remote ExplorerRaw disk manipulation: upload, download, delete, and structure files on the host PC.”Files” module in the Web UI or Mobile app.
Integrated ShellEstablish direct TTY pipelines for terminal/CMD commands on the host daemon.”Terminal” module in the Web UI.
System MonitorIntercept live CPU, RAM, physical disk, and process telemetry usage metrics.”System” dashboard panel.
Extension EcosystemInject third-party capabilities (e.g., WoL logic, custom compiled scripts).”Extensions” navigation tab.

6. Security Posture & Best Practices

  • Zero-Trust Manual Approval: No hardware can establish a connection without explicit user approval of the pairing request payload. If an unexpected request arrives, strictly deny it.
  • Cryptographic Passwords: Your Web UI admin password encrypts the configuration layer. Utilize high-entropy strings.
  • Update Protocols: PCLink is constantly evolving. Aggressively pull updates to ingest security patches and API modifications.
  • Public Network Risks: Engaging PCLink over hijacked public Wi-Fi is dangerous. Always rely on the enforced HTTPS wrapper and utilize a VPN tunnel where possible.

7. Diagnostics & Troubleshooting

ExceptionResolution Protocol
Cannot hit localhost:38080/ui/- Verify the PCLink daemon is running.
- Check firewall ingress rules for port 38080.
- Attempt raw http:// (HTTPS will force redirect).
Camera cannot parse QR code- Ensure both devices share the exact same Wi-Fi subnet.
- Hard-refresh the QR code generation via the Web UI.
- Utilize manual IP and pairing text blocks instead.
Input telemetry is lagging- Expected behavior over WAN networks. LAN should maintain ~10ms latency.
- Compress the screen capture render rate in the host settings.
Antivirus kills PCLink.exe- Mutate your antivirus exclusion lists to ignore the entire PCLink installation volume. This is an unavoidable false-positive due to aggressive screen capture hooking.
Lost Admin Keystore- You must physically wipe the configuration payload. On Linux: rm -rf ~/.config/pclink/. On Windows: Delete %APPDATA%\pclink\.

Support & Open Source Configuration

PCLink is actively maintained by Azhar Zouhir as an open source initiative.

View Source on GitHub