Relay is a route to an existing Yuri host, not another place where your projects run. Desktop and SSH-managed hosts can provide this route; ordinary Web / CLI hosting does not enable a Relay host.
Establish availability at the source
Create a Relay-capable pairing on the host and inspect the Relay state in Remote Instances. The host and receiving device must both reach the Relay endpoint. A sleeping or stopped host cannot serve requests through it.
When a saved connection includes both direct and Relay routes, a reachable direct route can be preferred. A Relay-only link has no direct route to fall back to.
Know what the route authorizes
The Relay forwards end-to-end encrypted traffic; the paired device still needs authorization from your host. Encryption does not turn an unused pairing secret into something safe to share publicly. Revoke an unwanted client at the host, or disable Relay access when you no longer want that route.
Direct network connections and public HTTPS hosting have separate reachability and authentication requirements. Use the connection checklist to identify which route is failing.