Troubleshooting

1. Check the agent is running: silux-agent status (Linux: silux-connect-agent status). On Windows look for the Silux Connect Agent service; on Linux systemctl status silux-connect-agent.
2. Check it can reach your Silux Connect server over HTTPS and the relay WebSocket (firewall, captive portal, proxy).
3. Behind a proxy? silux-agent set-proxy http://user:password@proxy.example:3128, then restart the service.
4. Asleep or switched off? Try Wake up — see Wake-on-LAN.
5. Was it never enrolled? Enrolment errors: 401 auth.required (bad or expired enrolment key), 402 device_limit_reached (plan device limit), 403 tenant_mismatch (re-enrol cleanly).

macOS needs two permissions for silux-agent (and for the Silux Connect app if you use it):

• System Settings → Privacy & Security → Screen Recording (or Screen & System Audio Recording) — without it: no picture (“The remote screen can't be shown”).
• System Settings → Privacy & Security → Accessibility — without it: picture but mouse and keyboard do nothing.

After switching them on, end the session and connect again.

The agent needs xdotool, xclip and wl-clipboard. Installing the .deb with sudo apt install ./silux-connect-agent_….deb pulls them in; a plain dpkg -i may not. Run sudo apt -f install to fix it. Ubuntu 22.04+ / Debian 12+ are required.

• Blurry text on a slow link is normal at first on Ultra-Low — it sharpens within moments of the screen settling.
• Choose Eco for crisp text at low data, or Auto (adaptive) to let it decide.
• Hide the wallpaper, lower the remote resolution, or share one window — see Quality & bandwidth.
• Turn on Options… → Show connection quality to see kbps, delay and round-trip time.
• Press Refresh if part of the picture looks stale.

• “That access code or password is wrong.” — the code changes each time the agent restarts; ask for the current one.
• “Waiting for the person at the computer to accept…” never ends — they must answer the approval window. If nobody is signed in to that computer, connect-by-code can’t be approved; use an unattended password.
• “Too many wrong codes. Try again in 5 minutes.” — wait, then retry.
• Your workspace may restrict code connections (Who may connect by ID + code in Security Policy).

• Click into the browser tab — browsers only write to your clipboard while the tab is focused.
• Allow clipboard access when the browser asks (“The browser blocked clipboard access”).
• Check Clipboard mode in Security Policy and the Clipboard permission in your profile.
• For login screens, use Actions… → Type clipboard text.

• Check the File transfer permission and that USB control isn’t set to No file transfer or Block.
• A name can’t contain / or \.
• The local-folder pane works in Chrome and Edge; other browsers use Upload and save to Downloads.

Browsers only allow the camera and microphone on secure (HTTPS) sites, and ask for permission the first time. Check the site permissions in the address bar. Dictation also has to be switched on for your server; if not, the button says “Voice dictation isn't enabled”.

Closing the window hides it to the tray — the app keeps running. Click the tray / menu-bar icon (on Windows it may be under the ^ arrow) or use Open Silux Connect from its menu. To really exit, choose Quit.

• “That email or password is incorrect.” — use Forgot password?.
• “Account locked due to too many attempts. Try again later.” — wait and retry.
• In the app, check Workspace & server options: the right workspace slug and the right server (Silux Connect server or your own).
• No sign-in code? For email or Telegram codes press Send a new code (once every 30 seconds) and check spam. Lost your authenticator or phone? Use a backup code, or ask a workspace owner. See Sign-in codes.

When you contact support, include:

silux-agent status          # on the remote computer (Linux: silux-connect-agent status)
silux-agent get-id

the session’s page from Sessions (its events), and the time it happened. Your workspace admin can check the Audit log.