Skip to content

Show the app's own 404 page, and know the explorer's own domains - #318

Merged
HDauven merged 1 commit into
mainfrom
fix/not-found-page
Nov 3, 2026
Merged

HDauven merged 1 commit into
mainfrom
fix/not-found-page

Conversation

@HDauven

@HDauven HDauven commented Nov 3, 2026

Copy link
Copy Markdown
Member

Two changes ahead of moving the explorer to Cloudflare and its own domains (explorer.dusk.network, explorer.testnet.dusk.network):

  • The build writes 404.html, which DigitalOcean and Cloudflare both serve for a missing page, so visitors see "Page not found" in the normal layout rather than the host's plain page. Tried in a browser with a server that behaves that way: status 404, the layout, and a working Home link.
  • makeNodeUrl picks the right node on those hostnames. The apps.* ones keep working.

Nothing changes on the live sites until the next deploy.

The build writes a 404.html that hosts serve for a page that isn't there,
so the explorer says "Page not found" in its own layout. The explorer's
planned domains read their own network's node.
@HDauven
HDauven merged commit 9b7fd4e into main Nov 3, 2026
1 check passed
@HDauven
HDauven deleted the fix/not-found-page branch November 3, 2026 14:39
@HDauven HDauven mentioned this pull request Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant