Skip to main content
Most setup problems fall into a handful of buckets. Find your symptom below; if you’re still stuck, open an issue with the terminal output from both machines.

Common symptoms

Enable both Accessibility and Input Monitoring for ShareClick (or your Terminal, if running from the terminal) in System Settings → Privacy & Security. Then quit and reopen ShareClick — permissions only take effect on relaunch.
The psk isn’t identical on both machines. Passphrases are case-sensitive and must match exactly. Re-check both config.toml files.
Check all of:
  • Both machines on the same Wi-Fi / network?
  • Windows firewall allowed ShareClick (Private networks)?
  • Correct server_host IP on the client?
Try shareclick discover to see if the server is visible over mDNS.
The name field must match one of the [[machines]] entries in the same config file. Fix the spelling so they line up.
Check the layout edges (right / left / top / bottom) in [[machines]] and confirm auto_edge_switch = true. As a reliable escape, hold both Shift keys to toggle control from the keyboard, or press F12 on the server.
New icons hide under the ”^” (show hidden icons) arrow by the clock — drag ShareClick onto the taskbar. For a first test you can skip the tray entirely and run shareclick.exe connect from PowerShell.
This is the unsigned-app quarantine flag. Remove it:
Full details in Installation.

Quick reference

Still stuck?

Open an issue on GitHub

Include the terminal output from both machines so we can help fast.