Custom 404 / Error Page Configuration

[tjorvenhu]

Summary

Currently, when a user accesses a non-existent resource, Pangolin returns the default 404 page.

While it is possible to implement custom error pages using Traefik, there is currently no way to configure a custom 404 page, redirect, or fallback behavior directly from the Pangolin UI.

It would be great to have native support for custom error handling within Pangolin.

Motivation

The default Traefik 404 page looks very generic and unprofessional, especially in customer-facing or production environments. Providing a simple way to configure a custom 404 page or redirect directly within Pangolin would improve the user experience and allow administrators to maintain consistent branding without requiring additional Traefik configuration.

Proposed Solution

Add a configurable option in the Pangolin UI that allows administrators to define what should happen when a requested resource is not found.

Possible options could include:

Display a custom HTML error page
Redirect to a specified URL
Redirect to a specific Pangolin-managed resource
Configure custom pages for different error codes (404, 500, 502, etc.)

Alternatives Considered

No response

Additional Context

No response

[alex3025]

Yes, this is something very needed!

Seeing a white page with just a "Bad gateway" or "404 not found" text is far from professional.