What your network needs to allow
IXEL Mesh needs no incoming ports. Each device makes outgoing connections only:
| To | Protocol | Why |
|---|---|---|
mesh-handshake.ixel.si and auth.ixel.si |
HTTPS (TCP 443) | Sign-in and finding your other devices |
mesh-handshake.ixel.si |
UDP 3478 | Learning this device’s public address |
| Your other devices | UDP | The encrypted connections themselves |
Direct connections work through most home routers, mobile networks and cloud firewalls, because both devices reach out to each other at the same moment.
When both devices are behind strict networks (some corporate and carrier networks), a direct path may not be possible. Relays that run on your own devices are coming for these cases. Until then, one device with a public address in your mesh (a cloud VM, or a router with a forwarded UDP port) connects to everything.
A device shows Connecting and never connects
- Check both devices are turned on in IXEL Mesh and show each other as online.
- Make sure outgoing UDP isn’t blocked on either network.
- Run
ixel-mesh statuson both to see the path each one is trying.
“This device was removed from your mesh, or its sign-in expired”
The device was removed in the Dashboard, signed out, or hasn’t signed in for 180 days. Sign in again in IXEL Mesh.
“You’ve reached the device limit for your plan”
Remove a device you no longer use in the Dashboard, then try again.
The proxy address is in use
Another copy of IXEL Mesh may be running, or another program uses port 1055. Choose another address in Settings → Network, such as 127.0.0.1:1056.
Logs
If something goes wrong, the background service’s log usually says why:
| System | Log |
|---|---|
| Mac | ~/Library/Logs/IXEL Mesh/meshd.log |
| Windows | %LocalAppData%\IXEL Mesh\meshd.log |
| Linux | ~/.local/state/ixel-mesh/meshd.log |