Skip to content

Admin Panel

http://bambuddy.local:8001, user admin, password as set in the setup wizard.

This panel manages the box. Bambuddy's own settings live inside Bambuddy, on port 8000. The separation is deliberate: the panel is an independent service, so it stays reachable when Bambuddy is restarting, misconfigured, or refusing to start at all.

Plain HTTP on a trusted LAN

Like Bambuddy itself, the panel serves plain HTTP with HTTP Basic authentication. Over HTTP, Basic credentials are base64-encoded on the wire, not encrypted. Keep the appliance on a network you trust, or put your own reverse proxy in front of it.

If no password has been provisioned, the panel refuses every route except /health with a 503. That is what makes binding to all interfaces safe by default.


Dashboard

Health at a glance:

  • CPU temperature, and the Raspberry Pi power and thermal flags — undervoltage and throttling, both right now and since boot. The since-boot flags are the ones that explain mysterious slowdowns; a cheap USB-C supply will set them.
  • Disk and memory usage.
  • Service states for Bambuddy, Docker, and the panel itself.
  • Network — hostname, mDNS name, and every address the box answers on.
  • Versions — the OS, the appliance image, and the running Bambuddy container.

Plus clean reboot and shutdown buttons. Use them rather than pulling power; an SD card interrupted mid-write is the most common way to kill an appliance.


Network

LAN connection shows the active interface and its addresses.

Secondary IP aliases add extra addresses to the LAN interface — one per virtual printer that needs its own address on your network.

bambuddy-appliance net-alias-add 192.168.1.50/24

These are added alongside the primary DHCP address. The primary IP, DHCP, and gateway configuration are deliberately never touched here, so there is no way to reconfigure the appliance off its own network from this screen.

Tailscale signs the appliance into your tailnet so you can reach it — and its virtual printers — from anywhere, without opening a port on your router. The daemon ships enabled but logged out. The panel walks you through it: it runs tailscale up, shows the sign-in URL and a QR code (Tailscale's own page handles first-time sign-up, so no console or API key is needed), then displays the 100.x tailnet address you can paste into a slicer.


Updates

Two independent lanes, each showing its current and latest version.

Bambuddy

Pulls the chosen container tag, repins the compose file, starts it, and waits for Bambuddy's health check.

Automatic rollback

If the new version doesn't come up healthy, the appliance puts the previous tag back and restarts it. Your data is never touched by an upgrade — only the container image changes.

Check for updates queries the container registry for the newest release tag and pre-fills the field for you.

Operating system

A Debian package upgrade (apt full-upgrade), with a disk-space and clock preflight.

No rollback on the OS lane

Unlike the Bambuddy lane, an OS upgrade cannot be undone. It refuses to start with less than 1 GB free, warns if the clock isn't synchronised, and tells you when a reboot is required. Take a backup first.

Both lanes

Upgrade jobs run detached from the panel. Closing the browser tab, or even restarting the panel mid-upgrade, does not interrupt them — progress streams to a file the page polls. Reopen the tab and you pick up where you left off.

The appliance image itself

The image is versioned separately (shown on the Dashboard) and is updated by re-flashing the card, not in place. See Updates & Backups for what that costs you.


Diagnostics

Tail the journal of any core service — Bambuddy, Docker, the admin panel, the setup wizard, firstboot, or the reset handler. Only these units are readable; the panel never passes a caller-supplied unit name to journalctl.

Download support bundle packages the host-side picture into one zip: system facts, per-service logs, docker compose ps and docker ps, ip addr and ip route, and the appliance configuration files.

Credentials are stripped

Secret values in bambuddy.env are masked, and the admin password hash and pending WiFi credentials are never included. The bundle is safe to attach to a public bug report.

This is the outside-the-container complement to Bambuddy's own in-app support bundle on the System page. A good bug report usually wants both.


Customising the panel

The page has a light/dark theme toggle and a language picker covering the same ten locales as the setup wizard.

Operator overrides live in /etc/bambuddy/admin.env:

# Bind loopback-only and front it with your own reverse proxy
BAMBUDDY_ADMIN_BIND=127.0.0.1
BAMBUDDY_ADMIN_PORT=8001