Skip to content

[BUG] STATUS_PAGE_DOMAIN #282

@kfrancis

Description

@kfrancis

Description

When STATUS_PAGE_DOMAIN is set to a subdomain (e.g., supercheck.example.com), the application appears to strip the subdomain and use only the root domain (example.com) as the CNAME target for custom domains and for default UUID-based status page URLs.

Steps to Reproduce

  1. Deploy Supercheck self-hosted (K3s via setup-k3s.sh)
  2. Set STATUS_PAGE_DOMAIN=supercheck.example.com (a subdomain, not a root domain)
  3. Redeploy the application
  4. Create a status page and configure a custom domain (e.g., status.otherdomain.com)
  5. Observe the CNAME target shown in Settings → Custom Domain → DNS Configuration

Expected Behavior

The CNAME target should show supercheck.example.com (the full STATUS_PAGE_DOMAIN value), and default status page URLs should be generated as [uuid].supercheck.example.com.

Actual Behavior

The CNAME target shows example.com (the root domain), suggesting the subdomain portion is being stripped. When STATUS_PAGE_DOMAIN is unset, the target falls back to supercheck.dev.

Environment

  • Version: d27104e
  • OS: Ubuntu 24 (Azure VM)
  • Deployment: K3s with Traefik, via setup-k3s.sh

Context

This is a common scenario where the root domain (example.com) hosts a corporate website on separate infrastructure, and Supercheck runs on a subdomain (supercheck.example.com). Setting STATUS_PAGE_DOMAIN to the root domain is not viable as it would direct CNAME targets to the wrong server.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions