Check the destination computer first: it must be awake, online and running Yuri. Use its actual local address or desktop window to establish whether the problem exists before the network connection.
Follow the route that was saved
- LAN: the client needs a reachable address and a host listening on that network. A loopback address on the phone points at the phone.
- Relay: check host Relay availability and connectivity. A Relay-only connection cannot rescue an offline host.
- SSH: read the reported stage—authentication, remote setup or forwarding—and inspect that stage rather than repeatedly replacing the pairing code.
Then check enrollment
A used or expired code cannot enroll another client. Generate a fresh one on the intended host. A revoked client must pair again; a locally deleted connection may simply need to be imported again with a new pairing.
If the connection succeeds but the expected work is absent, confirm the host identity and project directory. Do not reset the host's data just because another device is looking at a different workspace.