ZeroTier Gateway
The ZeroTier gateway is used to connect to a ZeroTier network. It is not a system-level VPN, does not modify system network settings, and does not affect other apps' network traffic. It only provides a data channel for resources within OmniGate.
Configuration
| Field | Description |
|---|---|
| Name | Gateway display name |
| Network ID | ZeroTier network ID |
| Identity Public | Node identity public key, can be generated or stored by the app |
| Identity Secret | Node identity secret key, must be stored securely |
| Local Proxy Address | Default 127.0.0.1 |
| Local Proxy Port | Default 9082 |
| Auto-Connect on Launch | Automatically activate this gateway when the app opens, disabled by default |
Basic Workflow
- Add a ZeroTier gateway and fill in the Network ID.
- Save and attempt to connect.
- Go to ZeroTier Central or your self-hosted controller to approve the new device.
- Reopen the resource.
Authorizing Devices
ZeroTier networks typically require authorizing new nodes in the console. Without authorization, OmniGate may be able to start the node but will not be able to access resources within the virtual network.
Common Issues
New device not visible in the console
Verify:
- Whether the Network ID is correct.
- Whether the current network can reach the ZeroTier root servers or your controller.
- Whether the app has network connectivity.
Authorized but resource won't open
Check:
- Whether the target resource's IP is within the ZeroTier-assigned network segment.
- Whether the target device's firewall allows access from ZeroTier addresses.
- Whether the resource port is correct.
Current Implementation Notes
ZeroTier uses an in-app node, not a system VPN. It only serves resources within OmniGate and will not route other apps' traffic through the ZeroTier network.
Auto-Connect
The ZeroTier gateway supports an "auto-connect on launch" toggle. When enabled:
- The app automatically activates this gateway on startup.
- The gateway list will display an
autolabel for this gateway. - Enabling the toggle will immediately trigger a connection and save the configuration.
When disabled, the gateway list shows a lazy label, and the gateway will only connect when you open a resource under that gateway.
Enabling auto-connect saves the time spent waiting for the gateway to connect, but it increases app memory usage and battery consumption. It is recommended to enable this only for frequently used gateways.