Nodes and relays
A node is another server that runs OpenVPN for your panel. Clients are created once, in the panel, and work on every node.
Add a node
1. In the panel, open Nodes → Connect a node. It shows the install command with your panel's address already filled in; press the copy button and run it as root on the new server:
bash <(curl -fsSL https://raw.githubusercontent.com/Erfan-XRay/Ovira/main/install.sh) node --panel-ip PANEL_IPThe script downloads Ovira from GitHub itself, so nothing is copied to the new server first. --panel-ip makes the node answer only your panel. When it finishes it prints a node key (BNK1-…). The node listens on TCP port 62060; use --port for another one.
2. Back in the dialog, paste the key, give the node a name and save. The panel connects within seconds.
3. Add an OpenVPN server on it: on the node's card, Add a server here. Pick its port and protocol like on the main server.
The node key contains the node's API key and its certificate fingerprint, so the panel talks only to that node. If you reinstall a node, paste its new key in the node's editor. ovira key on the node prints the key again.
The panel's own server
A panel can be installed on its own (an empty panel that only manages nodes) or together with OpenVPN on the same server, see Install. On an empty panel the main server's card says Panel only. To make that server a node too, run on it:
ovira openvpn enableIt installs OpenVPN if needed and creates the first servers. ovira openvpn disable stops them again; the panel and its other nodes keep working.
Devices at once
The device limit counts a client's tunnels on all servers together. With a limit of 2, a client may use two devices anywhere: both on one node, or one on each.
Traffic multiplier
Each node (and the main server) has a multiplier for quota accounting:
| Multiplier | 1 GB used there counts as |
|---|---|
| ×1 | 1 GB |
| ×1.5 | 1.5 GB |
| ×0.5 | 0.5 GB |
| ×0 | nothing (free traffic) |
The traffic shown on the node's card is always the real amount. Subscription pages show the multiplier next to each server.
Connect addresses (relays and tunnels)
By default clients connect to the node's own address. If you put relay servers in front of a node (for example servers inside the country tunneled to a node abroad), add their addresses in the node's editor under Connect addresses:
| Field | Example |
|---|---|
| Label | Tehran relay |
| Host | ir1.example.com |
| Port | empty = the server's own port, or the relay's port |
| For | All servers, or one OpenVPN server on the node |
Every address becomes its own profile on the subscription page, and a failover remote line in the all-in-one profile. Four relays in front of two nodes give clients four profiles to choose from.
WARNING
When a node has connect addresses, profiles use only those. Add the node's own address too if clients may also connect directly.
When a node goes offline
Tunnels on it keep running. The panel reconnects when the node is back, sends anything that changed while it was away, and counts traffic without counting anything twice.
Remove a node
Nodes → ⋯ → Remove node stops its OpenVPN servers and takes them out of every profile. To remove the software from the node itself:
bash install.sh --node --uninstall --purge