Website Opens but Local Agent Stuck Connecting to Relay or Times Out - What to Do?
Distinguish between webpage access and persistent command connections; check the target computer's network and proxy paths.
Successful Webpage Does Not Guarantee Command Channel Success
The Local Agent first authenticates, then connects to the command relay; if the client is stuck at this stage or reports a connection timeout, it is not yet ready to receive tasks. Opening a webpage in a browser only proves part of the network path is available. Proxies, VPNs, or network policies may affect the webpage and persistent connections differently, so diagnosis must be done on the target machine running the client, not based solely on successful access from another device.
Check Current Network Before Restoring Connection
Confirm the client terminal is still running and retains the last sanitized error. Check if the network was recently changed, proxies enabled or disabled, or if it entered a restricted network environment; restore connection under normal network conditions you are authorized to use, then retrieve the current commands from settings. The client prioritizes WebSocket but falls back to HTTP streaming, which does not guarantee passing through all proxies or restrictions, so do not disable all security controls just for troubleshooting.
Wait Until Ready Before Continuing Tasks
After seeing 'Local sandbox is ready!', verify the connection list and currently selected machine. If repeated failures occur, record the time, system, connection method, and whether a proxy is involved; do not provide actual tokens or full commands. Only consider credential handling if authentication failure is confirmed; if only output updates disconnect, first check the original task status to avoid repeatedly submitting the same execution operation to test the network.