# Error Pages

Error Pages is a lightweight Go service that replaces your HTTP server's default error pages with original, eye-catching designs, with no third-party runtime dependencies. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4915/error-pages

## Description

Error Pages is a lightweight Go service that replaces your HTTP server's default error pages with original, eye-catching designs, with no third-party runtime dependencies. It ships a curated collection of unique HTTP error page templates, lets you bring your own custom templates, and includes a static pre-rendering utility, all served through a small server that integrates into your existing infrastructure. It is the easy way for homelabbers to make self-hosted sites return polished, branded 4xx and 5xx pages instead of generic defaults.

## Platform availability

Available on 2 of 10 platforms: Unraid, Helm.

## Health score

75/100 (Good), based on 4 of 5 factors.
- Maintained: 98 (last commit 17 days ago)
- Popular: 64 (1,512 GitHub stars)
- Easy to install: 20 (2 install platforms)
- Security check: 100 (no serious findings, CI, tests)

## Links

- GitHub: https://github.com/tarampampam/error-pages
- Official website: https://tarampampam.github.io/error-pages/
- Kubernetes (Helm): https://artifacthub.io/packages/helm/geek-cookbook/error-pages

## Common questions

### What must error-pages do when used as a direct backend?

When used as a direct backend, it must return the correct status code itself.

### What dependency footprint is described for the server?

It is described as a tiny, zero-dep HTTP server.

### Where do I configure a custom error page in a Swag proxy?

The provided thread does not state the configuration location; it only reports that a user wanted to replace Swag’s 403 page with a custom error page or redirect.

---
Source: Our Local Host (https://ourlocalhost.com/app/4915/error-pages), the self-hosted and open-source app directory.
