Connect on difficult networks

If Auris cannot connect

1. Check the connection itself

   Confirm the phone has internet access. If possible, compare Wi-Fi with mobile data to find out whether the failure follows a particular network.

2. Allow recovery to try another route

   Auris can use alternate resolution, bundled endpoint information and adopted relays when its recovery policy calls for them.

3. Review an available relay invitation

   If a trusted contact shares a relay descriptor, review the adoption disclosure before accepting it. That route needs a reachable relay and backend to work.

What a connection relay does

A connection relay forwards traffic toward the Auris backend. The inner encrypted session protects application framing from a relay that terminates outer TLS. The relay can still observe your address, timing, traffic volume and its backend connection.

Relays are shared through contacts, with explicit adoption. Availability depends on the operator; there is no public Auris relay directory.

Connection relay or call relay?

Connection relay

An alternative path to the Auris service, useful when the ordinary route is unavailable.

TURN call relay

Carries encrypted call media. The Hide my IP on calls setting chooses a relayed media path to avoid exposing your direct address to the other caller.

These solve different routing problems. Neither is a multi-hop anonymity network. Choose an operator you trust for the network information the route exposes.

What to expect

Network filtering changes by provider and location. A route that worked yesterday can fail today, and encrypted DNS alone will not overcome an IP block. The client has relay support, but this review did not establish a live volunteer relay fleet or test every restricted network.

Transport layers and reachability evidence →