Website hosting returning "Page Not Found" after successful deployment

Ask the Community
,
1

Hi, this is a technical infrastructure issue with website hosting on my Developer Tier enrollment.

Issue: My OSDK React app’s hosted domain returns “Page Not Found” even though the domain shows “Domain ready” and version shows “Live” in Developer Console.

Details:

  • Domain: REDACTED.apps.euw-3.palantirfoundry.co.uk
  • Developer Console shows domain is ready and version 0.1.0 is deployed with 9 files
  • OAuth login completes successfully (consent screen works)
  • But the callback redirects to a “Page Not Found” from the hosting infrastructure
2

Key fact: Foundry automatically routes unmatched paths (like /auth/callback) to index.html, but only if your build doesn’t include a 404.html file. If your deployed assets contain a 404.html (some Vite/CRA templates or static-site generators add one by default), Foundry serves that real 404 instead of falling back to index.html, and your OAuth callback handler JS never runs.

Check this first:

  1. Look at your 9 deployed files, is there a 404.html in there? If yes, remove it (or make sure your build doesn’t generate one) and redeploy. That’s the most likely fix.

If there’s no 404.html, check these next, in order:

  1. Zip structure — when you compressed your dist/ folder, did you zip the contents (index.html at the root of the zip) or the folder itself (dist/index.html)? Foundry’s docs explicitly warn against including the directory itself, if index.html isn’t at the zip root, every route breaks, not just /auth/callback.
  2. Redirect URL match confirm the redirect URL is set to exactly https://REDACTED.apps.euw-3.palantirfoundry.co.uk/auth/callback in two places, and that they match character-for-character (no trailing slash mismatch):
  • In your app code (OSDK auth config)
  • In Developer Console → your application’s OAuth/redirect URL setting
  1. Deployment target — confirm version 0.1.0 was actually deployed to production, not just uploaded/previewed. Developer Console has a separate “preview” vs “deploy to production” step “Live” should mean production, but worth double-checking you’re not looking at a preview URL vs the production domain.

Felipe Montes
Development Advisor
Follow me @ linkedin.com/in/felipemontesl/ or GitHub: Brazillianerd