Core apps
The node installs its core apps onto the pool by itself, one at a time:
- Terminal opens a shell on the node from the browser.
- Authelia owns the accounts everything else signs in with.
- Traefik answers on the node’s name and routes to its apps.
Each app is downloaded and then installed. The app being worked on shows what it is doing, and the ones after it wait their turn.
Certificate
Section titled “Certificate”Once all three are running, setup waits for the node’s certificate.
Let’s Encrypt issues the certificate once it can reach the node on TCP 80 at its name. The name has to resolve on the internet to your public IP address, and TCP 80 has to be forwarded to the node.
The node gets a wildcard certificate from Let’s Encrypt through its fleet registration: the fleet answers Let’s Encrypt’s DNS check, so nothing on your network has to be reachable from the internet for it.
Waiting
Section titled “Waiting”While the certificate is being issued, Back and Continue are locked.
Issued
Section titled “Issued”When the certificate is issued, the waiting line disappears and Continue becomes available.
Not ready after a minute
Section titled “Not ready after a minute”If the certificate is still missing after a minute, setup explains why and unlocks Back. The line under the warning shows that setup is still checking, and both disappear once the certificate is issued.
Continue unlocks too, so setup can finish without the certificate.
The name does not resolve yet. DNS may still be propagating, or the A record was not created.
No certificate yet. Let’s Encrypt has to reach the node on TCP 80: check the port forwarding, that the A record points to your public IP, and that your connection is not behind CGNAT.
Continue stays locked until the certificate is issued.
No certificate yet. The check runs through fleet: the node has to reach fleet, and the router must not intercept DNS. See No certificate on univrs.cloud.
Let’s Encrypt error
Section titled “Let’s Encrypt error”When Let’s Encrypt returned an error, setup shows it, followed by the same checks as under No certificate yet.
If an app fails to install, setup cannot continue until it is installed and running.