[BUG] Status page not loading on custom domain

[ijonjic11]

Description

The status page does not open when accessed through a custom domain.

Steps to Reproduce

1. Log in to Supercheck app
2. Navigate to Status Page settings
3. Configure and save a custom domain (e.g., status.yourdomain.com)
4. Visit the custom domain in a browser

Expected Behavior

The status page should load correctly at the configured custom domain, displaying the relevant service statuses.

Actual Behavior

The status page does not open. Getting 404 page not found

Environment

• Version: 1.3.1-canary.4
• OS: Debian 13
• DNS: Bind

.env settings:

STATUS_PAGE_DOMAIN=status-dev.example.com

Bind setup:

status-dev.example.com 1200 CNAME supercheck-dev.example.com

Status page settings:

status-dev.example.com (Domain verified and active)

[krish-kant]

@ijonjic11 Thank you for the detailed report.

Root Cause

The status page system uses STATUS_PAGE_DOMAIN (e.g. supercheck.io) as the base hostname for default UUID-based subdomain routing — every status page gets a URL like <uuid>.supercheck.io. Custom domains are designed for hostnames outside that namespace (e.g. status.yourcompany.com).

When a subdomain of STATUS_PAGE_DOMAIN is entered as a custom domain, the application recognizes it as a default UUID subdomain and never routes it to the custom-domain handler. This means the custom domain setting is accepted and saved, but requests to that hostname are never matched — resulting in a 404.

What Is Fixed

We have added validation to prevent this misconfiguration:

• Settings UI — The settings page now shows a warning when a reserved hostname is entered and prevents saving.
• Domain verification — DNS verification now rejects reserved hostnames before attempting to check records.

Recommended Setup

To use a custom domain for your status page:

1. Choose a hostname outside the STATUS_PAGE_DOMAIN namespace — for example status.yourcompany.com.
2. Create a CNAME DNS record pointing that hostname to the target shown in Settings → DNS Configuration.
3. Wait for DNS propagation (5–30 minutes), then click Verify DNS in Settings.

Note: If you use Cloudflare, set the record to DNS only (grey cloud) during verification. You can re-enable the proxy afterwards.

Changes will be available in next version, but please test with recommended setup and let me know.

[ijonjic11]

I didn't quite understand what I need to do exactly:

My server is called:

supercheck-dev.example.com

DNS:

supercheck-dev.example.com 1200 A <IP_ADDRESS>
status-dev.srce.hr 1200 CNAME supercheck-dev.example.com

.env

APP_DOMAIN=supercheck-dev.example.com
STATUS_PAGE_DOMAIN=supercheck-dev.example.com

Status page UI settings:

status-dev.example.com (In the field) - active and verfied

Can you give me example what to add/change in my situation to make this working?

[ijonjic11]

Hello,

I pulled v1.3.1.-canary.8 and i see this on domain section:

APP_DOMAIN is still supercheck-dev.example.com but it pulls "localhost" from somewhere.

Can you take a look?

P.S. on v.1.3.1.-canary.7 everything looks good, it pulls APP_DOMAIN value.

Of course,status page on custom domain still not working for me.

[krish-kant]

@ijonjic11 Its not fixed yet, I'll let you know when its ready.

[ijonjic11]

Sorry for bothering,just to know,is this fixed or still in progress?

[krish-kant]

@ijonjic11 I will pick this again soon, it was taking more time then I thought, give me few days.

[ijonjic11]

No worries,just take your time :)

[krish-kant]

@ijonjic11 this is fixed in v1.3.4, please lest me know for any issue.