Troubleshooting

The machine does not show up

The install command waits for the agent to reach the server and says so if it does not. Look at the agent's log (paths in Linux, macOS and Windows):

• The command expired. It works once, for ten minutes: make a new one in Add machine.
• No outbound HTTPS. The agent connects out to tilder.run on port 443; nothing needs to come in.
• A container or a system without a user session. The agent runs in the background instead of as a service, and does not come back after a reboot.

The terminal stays on "connecting"

Your browser and the machine could not find a path to each other. Usually a relay takes over within seconds. If it never connects:

• Check the machine is online in Machines.
• On a strict network (a company or hotel Wi-Fi), UDP may be blocked. tilder then relays over TCP; a network that blocks that too blocks tilder.

Windows: Defender or Smart App Control

The Windows agent is not code-signed yet.

• Smart App Control (Windows 11, Settings → Windows Security → App & browser control) blocks unsigned programs, with no per-app exception. Use a PC where it is off, or wait for signed releases.
• Microsoft Defender may flag tools that open a connection out and let you work on the machine remotely. First check the file is ours:

Get-FileHash "$env:LOCALAPPDATA\Programs\tilder\tilder.exe"

Compare it with https://tilder.run/dist/<version>/checksums.txt. If it matches, report the detection as incorrect at microsoft.com/wdsi/filesubmission and tell us on GitHub with the detection's name.

Still stuck

Open an issue at github.com/nghyane/tilder/issues or write to support@tilder.dev. Include your system and the last lines of the agent's log; never a recovery code.