A node stores verified file replicas and serves downloads directly. Meshzu coordinates placement, health checks and delivery routes.
Use a dedicated Linux host with Docker Engine and the Compose plugin, Python 3.12 or newer, and at least 2 GiB of RAM. Keep enough free disk space for the capacity you offer, plus operating overhead.
The installer requires root access. TCP port 443 must be free on the host. Install Docker ↗
If the node has its own public IP, choose public port 443 and allow inbound TCP 443 in its firewall.
Behind a router, choose a public port and forward it to your node’s LAN IP on TCP 443. The public and internal ports can differ:
A download would connect to https://n-example.node.meshzu.com:8443. Use a reserved DHCP lease or static LAN address so the forwarding rule continues to work.
Meshzu assigns the hostname and manages its DNS and certificate. The console shows the public IP observed from the node’s connection. Networks with carrier-grade NAT or different inbound and outbound addresses may need additional network configuration.
Your firewall must also allow outbound HTTPS and DNS. The script does not change your router, firewall or DNS resolver settings.
For a node that has never checked in, open its Actions ⌄ menu and choose Install node to generate a fresh token. Previously issued installation tokens are replaced. If credentials were already created but the node never checked in, the replacement command includes --reenroll. Run it on the same node: it refreshes node credentials and keeps local storage.
It checks prerequisites, writes node configuration under /opt/meshzu-provider, creates node credentials, and builds and starts three Docker services: object storage, the node agent and HTTPS. Data lives in persistent Docker volumes. It obtains the node’s certificate and configures a systemd timer to check renewal twice a day.
It does not install Docker, format disks, configure port forwarding or change firewall rules. Installation can resume using the existing configuration. A new node does not receive customer data until Meshzu verifies its location, approves it and confirms connectivity.
| Status | Meaning |
|---|---|
| Awaiting installation | The node has not checked in. Use Actions → Install node. |
| Offline | Meshzu cannot currently reach the node. |
| Delivery blocked | The agent is connected, but public file delivery is not passing checks. Open Connection details and check DNS, forwarding and firewall rules. |
| Awaiting approval | Connectivity is working. An operator must verify the site and approve storage. |
| Online | The node has passed delivery checks. |
HTTPS response measures the response from Meshzu’s control service, not the customer’s latency or an ICMP ping. Stored and the replica count reflect verified copies; available capacity also accounts for placement reservations.
Meshzu assigns the physical site used for resilience. Servers sharing power or network infrastructure count as one location. Providers cannot declare their own independent locations.
Open Actions ⌄ → Delete node. Confirming removal revokes the node’s credentials and installation tokens. Deletion is available only when the backend confirms the node is unapproved and has no stored replicas or active uploads.
A node holding data must be safely emptied before deletion. Removing a node from the console does not uninstall its software or erase disks on the server.