Upgrade
From the dashboard
Section titled “From the dashboard”- Open Settings → Updates.
- Click Check for Updates — Pier compares the installed binary with the latest GitHub release.
- If a newer build is available, click Update & Restart.
Since 1.4.3 the button asks a small root service, pier-updater, to re-run the
official installer on the server. That refreshes everything the installer owns:
- the
pierbinary; pier-net-helper(the privileged helper) andpier-agent;- their systemd units, including the updater itself.
Pier restarts on the way; the page follows the progress and shows the installer log if
something fails. .env and /opt/pier/data are preserved.
The panel can only ask for an update — the request carries no parameters. What gets installed is decided on the server: the latest release, verified by sha256.
Servers installed before 1.4.3
Section titled “Servers installed before 1.4.3”Older installs don’t have the updater, and the panel shows a banner about it. Until it is
installed, the button can only swap the pier binary through pier-net-helper — and
fails outright if the helper isn’t running (for example after a reboot: older helper
units had no [Install] section). Run the installer once over SSH; after that every
dashboard update covers everything:
curl -fsSL https://pier.team/install | sudo bash
# Check: both lines must say "enabled", and the file must existsystemctl is-enabled pier-net-helper pier-updater.pathls -l /usr/local/sbin/pier-updateWhen an update fails
Section titled “When an update fails”cat /var/lib/pier-updater/status.json # last run: running / success / failedcat /var/lib/pier-updater/last.log # full installer outputjournalctl -u pier-updater -n 50 --no-pagerRe-running the one-liner is always safe — it performs the same update by hand. If it fails
with 404 within ~10 minutes of a new commit, CI is republishing the latest release:
wait and retry.
Manual upgrade
Section titled “Manual upgrade”The one-liner above is the manual upgrade: it downloads the latest release, verifies its sha256, keeps your port and data, and restarts Pier.
Rollback
Section titled “Rollback”Install a specific release instead of latest:
curl -fsSL https://pier.team/install | sudo bash -s -- --release-tag v1.4.2Releases are listed at github.com/joveptesg/pier/releases.
Database migrations only move forward and are not undone by a rollback. If you might need
to go back, back up /opt/pier/data before upgrading.