Skip to main content
The StackKits Node Hub is the first page to open after a Base Kit rollout. It lives at base.<domain> and points to setup steps, important links, service URLs, and the public guide for each installed service.

​
Prerequisites

You need a completed StackKits rollout and the domain or local DNS name printed by the installer or CLI.

​
Steps

1

Open the Node Hub

Open https://base.<domain> when HTTPS is enabled, or http://base.<domain> for local-only HTTP deployments.
2

Follow Getting Started

Complete the top checklist first: sign in through TinyAuth, create the first PocketID passkey, then verify status before exposing services outside the LAN.
3

Open a service

Use the service table to open the installed tool. Disabled services are intentionally hidden from the Node Hub.
4

Use the how-to link

Each row links to the public guide for that service. Open the guide before changing first-run admin, DNS, or access settings.

​
Verify

  • The page title is StackKits Node Hub.
  • The service table only lists enabled services.
  • Every visible service row has a service URL and a how-to link.

​
Troubleshooting

Check whether the rollout used local DNS, kombify Point, or public DNS. If local DNS is expected, confirm the server LAN IP and resolver settings printed by StackKits.
Missing rows usually mean the service is disabled in the generated StackKits variables or the module was not part of the selected kit.

​
Next steps

Base Kit

See what the default kit deploys.

Rollout paths

Compare installer, CLI, and TechStack rollout paths.