Custom 404 doesn't load on Cloudflare Pages

[JG-devo]

What version of astro are you using?

2.0.6

Are you using an SSR adapter? If so, which one?

None

What package manager are you using?

npm

What operating system are you using?

Mac

Describe the Bug

Cloudflare Pages is looking for a 404.html file to handle 404 responses, however, the production build of the final files includes a 404 folder with index.html inside. This seems to happen with SSG mode and dynamic routing.

I've tested this by going to domain.com/404/ and the page loads up on Cloudflare pages. Going to domain.com/404 goes back to the home page. I've also checked the build folder (/dist) and verified this result.

I've created a version of this bug with stackblitz linked below. Simply add /404/ to the end and try without i.e. /404

Thanks!

Link to Minimal Reproducible Example

https://stackblitz.com/edit/withastro-astro-daj2vt?file=src/pages/index.astro

Participation

• I am willing to submit a pull request for this issue.

[matthewp]

This is a non-standard feature that some hosts like Netlify support. It is not necessarily supported by all hosts. You can likely configure Cloudflare to use that page for your 404. I couldn't tell you how to do that, however. But it's not something Astro controls.

[JG-devo]

This is a non-standard feature that some hosts like Netlify support. It is not necessarily supported by all hosts. You can likely configure Cloudflare to use that page for your 404. I couldn't tell you how to do that, however. But it's not something Astro controls.

The bug isn't necessarily with Cloudflare or any host. If I create a 404.astro file directly, it automatically resolves to a 404.html file. Dynamic routing seems to put it in a folder.

[fcanmekikoglu]

setting assets.not_found_handling to "404-page" on wrangler.jsonc fixed the issue for me.

{
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "mysitedotcom",
    "compatibility_date": "2025-04-06",
    "assets": {
        "directory": "./dist",
        "not_found_handling": "404-page", 
    }
}