BareProxy Maintenance and Failover Pages Plugin: A Static Page When the Backend Is Down

Thu, 08 Oct 2026 00:00:00 +0000

Status: built, number 1 of 21 in BareProxy’s build order, and out in BareProxy 0.4.0 as maintenance.wasm on the releases page. The plugins are built easiest first, and this one was the quickest: one callback on the way in, one on the way out. Its manual is the README in the code repository.

When an app goes down, visitors get whatever the proxy says by default: a bare “502 Bad Gateway” or “503 Service Unavailable”. That reads like the site is broken, because it is. A page that says “we’re doing maintenance, back at 14:00” with the site’s own look reads like a site that’s being looked after.

BareProxy Uptime Checks and Status Pages Plugin: A Public Status Page Served by the Proxy

Thu, 08 Oct 2026 00:00:00 +0000

Status: planned, number 14 of 21 in BareProxy’s build order. The plugins are built easiest first, and this one is two or three days of coding: checks on a timer, history in the store, a status page. It comes after the Cookie consent plugin. This post describes what it will do, and it will be updated as it is built.

When a service has trouble, the first thing its users look for is a status page: is it down, is anyone working on it, when was it last fine. Most teams pay a separate service for that page, and the page knows only what its own checks see from the outside.

Reliability on BareProxy.com

BareProxy Maintenance and Failover Pages Plugin: A Static Page When the Backend Is Down

BareProxy Uptime Checks and Status Pages Plugin: A Public Status Page Served by the Proxy