Link Node64 to IPv64.net: local and hybrid health checks

Node64 is the homelab container of IPv64.net. Linked to your account, it measures health checks directly in your home network – including targets that cannot be reached from outside – and combines them with the online measurements of IPv64.net. This page explains how to link a node, manage it in the portal and move checks between online and local.

What linking gives you

Node64 also runs without an account. Connected to IPv64.net, you get the outside view and the portal on top. The connection has two stages:

You create the API key under API (see Account: API keys). How to install Node64 and what it can do besides health checks is described on ipv64.net/node64.php and in the Node64 docs.

Set up the health checks sync

If an API key is stored in Node64, you link the health checks sync with one click directly in the node. Without an API key you use a code:

1. Request a code
   Open the Healthchecks sync with ipv64 page in Node64 and click Link with ipv64.net to request a code. It has 8 characters (e.g. ABCD-EFGH) and is valid for 10 minutes.
2. Enter the code
   Log in to IPv64.net and open ipv64.net/link.php (in the node overview the button Node mit Healthchecks verknüpfen). Enter the code – with or without the hyphen.
3. Location and remote management
   Optionally enter a free-text location (e.g. “Home”, “Office”) and choose the remote management, then click Verknüpfen (link).
4. Done
   The node fetches its own credentials and connects within about 10 seconds. It and its checks then appear in the portal.

The node gets its own credentials, which you can revoke individually – the sync does not need the API key. The node opens all connections outbound over HTTPS; no port forwarding is needed (details: Node64 docs: who connects where).

Remote management

Remote management defines which commands the portal may give the node:

You can change the setting later on the node's detail page. The node decides itself what it accepts; the setting is transferred with the next sync.

Node overview: manage nodes

Under Nodes in the health checks bar (ipv64.net/nodes.php) you see all your Node64 containers in one list – whether they report via API key, are linked with the health checks sync, report as a honeypot sensor or run a CDN64 tunnel. With an API key a node reports at startup and then every 15 minutes.

• Tiles: nodes total, online, with health checks sync and honeypot sensors.
• Per node: name with location and online dot, version and platform, last report, health checks sync (connected or offline, last sync, number of checks, conflicts), honeypot, CDN64 tunnel and enabled modules.
• “nicht verknüpft” (not linked) means the node reports, but the health checks sync is not set up. “verknüpft (anderer Account?)” means the sync is linked to a different account.

Remove, allow again, delete a node

Remove (Entfernen) takes a node out of your account:

• The health checks sync is disconnected; the checks continue online where possible (see Disconnect the sync). Docker and Proxmox checks are deleted together with the node.
• A honeypot sensor of the node is blocked.
• When the node reports again, it deletes its API key and the health checks link; its local data stays.
• CDN64 names keep running through the node's tunnel until you switch them off in Node64 or at ipv64.net/cdn64.

Removed nodes appear in a separate list. Allow again (Wieder zulassen) undoes the removal – afterwards you enter the API key in the node again and, if needed, link the sync with a new code. Delete (Löschen) removes the entry from the list for good; a honeypot sensor of the node stays blocked. If the node reports again later with a new API key, it reappears.

Detail page of a node

For nodes with health checks sync, the name and Details lead to the detail view:

• The node's checks with state, target, type and recent measurements. Each check has check now and move online; Check auf dieser Node anlegen (create check on this node) opens the form with this node as execution.
• Node: change name, location and remote management; plus status, version, time zone, modules, last sync, pending entries in the outbox, linked since and the ID.
• Trigger full sync (Vollabgleich anstoßen): the node syncs its complete state with IPv64.net again.
• Last commands: the last 10 commands to the node with their result.
• Conflicts: if the node made changes while offline that overlap with changes in the portal, the page shows the number of conflicts. You see both versions in the node on the Healthchecks sync with ipv64 page. You can also decide here: enter the conflict number (from the node) and keep the server version or take over the node version (see Node64 docs: conflicts).

Disconnect the health checks sync

Healthchecks-Sync trennen (Token widerrufen) ends the link; the node then keeps running standalone. For its checks:

• If other nodes measure a check, they keep measuring it.
• If only this node measures the check and “continue checks as online checks” is ticked (default), it continues online at IPv64.net – provided the target is public and your measuring point limit allows it. Docker and Proxmox checks never run online; they are deleted together with the node.
• All other checks of this node are deleted in the portal. Pure online checks always stay.

A disconnected node can then be deleted from the list; this also removes its credentials, commands and channels, while the measurements stay.

Local and hybrid checks

With a linked node, a check's form offers two more executions:

• Locally on nodes: only your nodes measure. Suitable for everything in the home network – private IP addresses, .local names, DNS servers in the LAN, Docker containers. Locally, intervals from 5 seconds are possible, and local measurements do not count against your account class limits.
• Hybrid: nodes and IPv64 locations measure at the same time. The detail page then shows a diagnosis inside and outside.
• Several nodes: under measuring nodes you choose one or more nodes; each is its own measuring point. Docker and Proxmox checks belong to their node; further nodes are only possible through the cluster in Node64 (areas Proxmox VE and Docker, see Node64 docs: cluster).
• Check now hands a local or hybrid check to its nodes immediately.
• The node picks up a new local check as soon as it is connected. If the only measuring node is offline, the check changes to “not monitored” after three intervals (at least 5 minutes).

Checks you create in Node64 appear in the portal as well. You reach a node's push checks online via IPv64.net and in the home network directly at the node (see Push checks).

Synchronization

• Checks, maintenance windows and notification channels are synced between portal and nodes in both directions. You can change them in the portal and on every linked node.
• Measurements, events and incidents of the nodes go to IPv64.net. Without a connection the node stores them locally and uploads them later.
• Settings for quiet hours and grouped alerts apply to the whole account (see Notifications).
• Notifications: the node sends its own channels itself; IPv64.net gives it the order. They are marked with a house icon in the portal.
• How the node handles connection losses, conflicts and the outbox is described in the Node64 docs: what is synced.

Move checks between online and local

With Umhängen (move) a check switches between online, local and hybrid – individually on the detail page, for several checks via the bulk action in the list, or with move online on a node's detail page.

• Before the switch a test run takes place: online from every chosen location, locally on every chosen node. Only when all measuring points report OK is the new execution applied. Token and measurement history are kept.
• The nodes must be online for this, and their remote management must not be “off”.
• Online is not possible for private targets, not for Docker and Proxmox checks and only as long as your measuring point limit allows.

All details are under Health checks: moving.

What only Node64 offers

The portal is deliberately kept lean. You set up these features in Node64; their checks then also appear in the portal:

• Public status pages with daily bars, announcements, status.json and badges: Node64 docs: status pages
• Monitor Proxmox VE – nodes, VMs and containers of a cluster, read-only: Node64 docs: Proxmox VE. In the portal these checks appear in the group “Proxmox VE” with a subgroup per system.
• Monitor Docker hosts – all containers of a host, also remotely: Node64 docs: Docker. In the portal they appear in the group “Docker” with a subgroup per host.
• Local push URL that also works without internet: Node64 docs: push / heartbeat
• Export and import of checks, Prometheus metrics and the cluster of several nodes, also without an IPv64 account: Node64 docs: health checks and cluster
• More notification channels such as browser and Home Assistant: Node64 docs: notifications

The node overview and the nodes of the health checks sync are also available through the health checks API.

Found a mistake or missing something? Tell us in the v64.tech forum. · Updated: 2026-10-27