Cluster Settings

Set up this node and how the cluster stores files and runs work

This node

Node name

Advertised URL (how other nodes reach this one)

Leave empty if this node has no public address. It will then keep a tunnel open to a reachable member, which also works through Cloudflare.

Tunnel through

Accept self-signed certificates from other nodes (LAN only)

Not part of a cluster

Create a new cluster

This node becomes the first member. Generate join tokens here afterwards to add more nodes.

Join an existing cluster

Paste a join token generated on a reachable member of the cluster.

Cluster

Add a node

Tokens can only be generated on a node with an advertised URL. Paste the token into the other node's Cluster Settings.

Identity (single sign-on)

The identity origin verifies every login in the cluster. Accounts are copied to the other nodes so they still work when the origin is unreachable. Groups are matched by name, so create the same permission groups on every node.

Storage

Contribute a folder from this node

Files written to cluster:/ are stored as ordinary files inside contributed folders. Files already in the folder are adopted into the namespace on the next rescan. The cluster:/ drive appears in File Manager once the cluster has at least one volume.

Make nearly full volumes read only automatically

Applies to every node. A volume under 5% free stops taking new files and takes them again above 7%. Turn this off to let volumes fill up; volumes it had locked become writable again within a minute.

Volume	Node	Free / total	Files

Replica policies

Copies per top-level folder

Folders without a policy keep one copy. Extra copies are created by the replication service.

Members

Maintenance takes a node out of scheduling. Draining also moves its copies to other nodes so it can be switched off safely.

Scheduling

Jobs, new files and extra copies go to the node with the highest score. Raise a weight to make that quality matter more. The resulting scores are shown on Cluster Info.