Self-Hosting on Pingtower

Upgrading a self-hosted box to 1.2.0

Sun, 11 Oct 2026 00:00:00 +0000

The install guide says an upgrade is a binary swap and a restart, and that a release needing more says so on this blog. 1.2.0, coming from 1.1.0, needs more. This post is the whole list.

1. Take a backup first

Startup runs 1.2.0’s schema migrations, and they only go forward. Its first start with your secret key also reseals stored secrets in a form 1.1.0 can’t read (step 3). Back up before you replace the binary:

A new look for public status pages, and what 1.1.0 changes on yours

Wed, 07 Oct 2026 00:00:00 +0000

A status page now answers “is it down, and where?” before the reader scrolls. It is live on pingtower.com. A self-hosted box’s public status pages change the moment it runs 1.1.0, through the usual upgrade. If your own agents run gRPC checks, upgrade them too: see Upgrade agents that run gRPC checks.

What your readers see

The state first. The page opens on its overall state, the components that are not operational and since when.
Checks by region. Beside it, each region’s view of the checks your components bind, now and over the last 2 hours. Only sources named like a region appear; an agent your team named anything else stays private.
Response times. Turn on Show response times on the page for a component to chart its checks’ last 24 hours, with now and by region.
Groups fold. A group shows as one row with one 90-day bar of its worst component’s days, and opens by itself when something in it is wrong.
An incident’s progress. Started, Investigating, Identified, Monitoring, Resolved, marked as it moves. The incident’s own page gives when each stage began.

It still has no JavaScript and sets no cookies on a public page. Status pages covers every part.

Upgrading a self-hosted box to Release 1

Fri, 02 Oct 2026 00:00:00 +0000

The install guide says an upgrade is a binary swap and a restart, and that a release needing more says so on this blog. Release 1 needs more. This post is the whole list.

1. Take a backup first

Startup runs Release 1’s schema migrations, and they only go forward. Back up before you replace the binary:

SQLite: stop the pingtower unit and copy the data directory, or keep a recent backup that -backup-dir wrote.
PostgreSQL: back it up the way you back up any PostgreSQL server, for example with pg_dump.

See Storage for what lives where.