Reference
Network and security
What chaar needs from your network, how your devices reach your machines, who can get in and what's encrypted.
Check what to allow through your firewall, see how your devices connect, and know who can reach your machines.
What chaar needs from your network
- Internet on every device and machine. chaar doesn't work on a local network alone.
- No inbound ports. You don't open or forward any port, and you don't need a VPN.
- chaar's servers. They sign you in, check which machines you can open, and pass a connection along when your device can't reach a machine directly. A machine needs to reach them for chaar to start.
What to allow through a firewall
Allow these outbound connections from every device and machine:
| To | What it's for |
|---|---|
| chaar's servers | Sign-in, access, and connections that can't go direct. |
dns.iroh.link over HTTPS, and DNS | Finding where a machine can be reached. |
| Outbound UDP | Direct connections. If UDP is blocked, connections go through chaar's servers. |
exp.host over HTTPS, from machines only | Notifications to your phone, through Expo's push service. |
How your devices reach your machines
- Your device first connects to the machine through chaar's servers, wherever the two of them are.
- They then try to connect straight to each other. If that works, chaar's servers drop out. If not, the connection stays on them.
A direct connection is faster. One through chaar's servers works on more networks, and is a little slower.
When your device and machine are on the same network, a direct connection stays inside it. Some systems ask your permission for this:
On macOS 15 and later, chaar's first launch walks you through it. Choose Allow network access, then Allow when macOS asks to find devices on local networks. Earlier macOS doesn't ask.
If you don't allow it, chaar still works through its servers, a little slower.
See whether you're connected directly
Only the phone app shows this.
Open a terminal tab
Open a session and go to a terminal tab.
Open the session info
Close the keyboard and tap ⓘ at the top right.
Tap More
The Connection rows open below.
| Row | What it shows |
|---|---|
| Path | Direct, or Relayed when it goes through chaar's servers. |
| Latency | The round trip to the machine. |
| Via | The machine's address, or the server's name. |
A new connection can show Relayed for a moment before it moves to Direct.
What's encrypted
Everything between your device and your machine is encrypted end to end. When a connection goes through chaar's servers, they pass it along but can't read it.
Who can reach your machine
Only people with access, from a device signed in to their account. Being on the same network, or knowing the machine's address, isn't enough. chaar's servers check access before a device connects, and the machine checks again before it answers.
Who has access:
- You, as the machine's owner.
- People you share it with, as Can view or Can run. See Share with others.
- Every member of its workspaces, the same as Can view.
With view access, someone sees the machine's sessions, tab names, what each tab runs, agent chat titles and every status mark with its message. They never see a terminal's screen or a chat's messages, and they can't type in either.
A change to someone's access can take up to about 5 minutes to reach their devices.
If something fails, look up the message in Troubleshooting.
Stuck? Ask in the Discord community.