Skip to content

Network

Network shows the name the node answers to, how it is connected to your network, which proxies it trusts and what its firewall lets in.

The Network page

The Host card shows the name the node answers to: its hostname, cluster and domain name, for example spica.virgo.univrs.cloud. Select Edit to change them.

Editing the host

If another node on the network already belongs to a cluster, the cluster and domain are locked to that cluster.

The Interface card shows the node’s network connection: its address, virtual IP, default gateway, DNS servers, MTU and MAC address.

The badge next to the virtual IP says which node carries it:

  • Holding: this node answers on the virtual IP.
  • Standby: this node shares the virtual IP, but another node holds it at the moment.
  • On followed by a node name: another node on the network has a virtual IP, and this node is not part of it.

Select Edit to change the IP address, netmask, virtual IP, default gateway or DNS servers. Use Add DNS for up to three DNS servers.

Editing the interface

The virtual IP is the address the node’s name, its apps and your router’s port forwarding point to, so it is shared by all the nodes in a cluster. It can only be changed on the node that holds it, or while no node on the network has one yet.

A node on standby

On a node on standby, the virtual IP is locked. The ? next to it explains which node holds it; to move it to this node, use Take over virtual IP on the Dashboard.

The virtual IP locked on a node on standby

If another node on the network has a virtual IP and this node is not part of its cluster, the field is locked too. Adopt this node from the Dashboard of the node holding the virtual IP, to share it instead of configuring a second one.

If you put another reverse proxy in front of the node, add its IP address here. The node then reads each visitor’s real address from the headers that proxy adds, such as X-Forwarded-For. That address decides, for example, whether a visitor counts as being on your local network. The node’s own proxy is already trusted.

Select Add and enter the proxy’s IP address.

Adding a trusted proxy

Open a proxy’s menu to Edit or Delete it.

A trusted proxy’s menu

The Firewall card shows what the node accepts from the network. Incoming connections are blocked unless a rule allows them, and Allowed lists those rules: what each one is for, its port and its protocol.

The Firewall card

The rules cover the node itself. An app that publishes its own port is not listed here.

After repeated failed logins from the same address, the node blocks that address for a while. Blocked addresses lists the addresses blocked at the moment, with the service they were trying to log in to in brackets: sshd is the remote shell (SSH). The line under it counts every address blocked since the node last started and the failed attempts it is still watching.

Hover over the i next to an address to see when it was blocked and when the block expires. A block is lifted by itself when it expires.

When an address was blocked and when the block expires

To lift a block sooner, for example after locking yourself out with a wrong password, select the × next to the address and confirm.

The card is read again every hour. Select Refresh to read it now.