Dashboard settings

Open Settings → Configuration with an administrator account. The page opens on the address the dashboard answers at, the checkout and .env it runs from, and its state. Stack draws the path a request takes through Caddy, the frontend, and the backend, beside Restart and Rebuild. Settings groups Certificate, Address, Access, Sessions, and Features. A Danger zone at the end holds the uninstaller.

If someone edited .env over SSH without restarting, the page says .env differs from what is running and lists the differences; Restart adopts them. An installation without a Compose project shows its settings read-only and says to change them in .env.

Change an address or certificateCopy Anchor Link

1. Keep an alternate path to the host, such as an SSH session, before changing the address or allowlist.
2. In Certificate, choose Tailscale, Self-signed, or Plain HTTP. Tailscale fills in the machine's MagicDNS name, its tailnet address as the listening interface, and the tailnet in the allowlist when the host has a usable Tailscale identity. Plain HTTP moves the address back to localhost. Each field remains editable.
3. Review Address and Access together. Address holds the address, port, listening interface, and, under Internal ports, the frontend and backend ports. Access holds the allowlist (JD_ALLOWED_CIDRS) as a list of networks; the connecting client's IP must fall inside it. Keep loopback in that list so an SSH tunnel remains possible.
4. Select Apply and restart in the bar at the foot of the page. Read the before-and-after values in the confirmation. If the address changes, open the new URL after the services return.

The settings flow monitors the restart and puts the previous configuration back if the new one fails to come up. Plain HTTP is allowed only on loopback. For the tradeoffs among Tailscale, an SSH tunnel, and certificate modes, see Private access.

Change access, sessions, and featuresCopy Anchor Link

• Require two-factor under Access makes every account enroll an authenticator. An enrolled account is asked for its code either way.
• Sessions sets Session lifetime and Idle timeout as durations such as 12h or 60m.
• Features turns the Web terminal on or off (off removes its routes, not just the page) and controls Check for new versions.

These changes also apply with Apply and restart.

Restart or rebuildCopy Anchor Link

Use Restart after a service needs a clean start without rebuilding images; it recreates every container on the settings already on disk and keeps sessions. Use Rebuild when the checkout or its dependencies changed and fresh images are needed. The page follows each run, including its stages and transcript, after the dashboard reconnects. For an upgrade to another release, follow Upgrade.

UninstallCopy Anchor Link

Uninstall… in the Danger zone removes the dashboard from the server. You choose Keep for a reinstall, which leaves deployments running and keeps the data, backups, and key, or Wipe everything, which also removes deployments and the dashboard's data and asks you to type the server's host name. See Uninstall.

Know where settings liveCopy Anchor Link

The installer writes the active .env, and this page exposes the settings the dashboard can safely apply itself. Advanced tuning, including paths and worker counts, lives in environment variables listed in the configuration reference. A malformed duration or boolean stops startup with an error instead of silently reverting to a default.