CD
Cloudflare Developers•9mo ago
Marcel Overdijk

Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH

I've see multiple Failed: an internal error occurred errors here, but non of them helped me track down why my app is giving me the same. Unfortunately there is no detailed error log, it just gives me: 
22:53:42.785    Success: Finished cloning repository files
22:53:44.548    wrangler.toml config file detected
22:53:45.465    Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
22:53:42.785    Success: Finished cloning repository files
22:53:44.548    wrangler.toml config file detected
22:53:45.465    Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
It's a very small app, the dist folder just being 7 files and 508 KB. It has some functions using Prisma using the D1 binding. Locally the app runs fine with wrangler dev... Deployment ID: 03c8c103127e788e820573a1587a5cab0808522a
5 Replies
Walshy
Walshy•9mo ago
Hey @Marcel Overdijk I'm having someone take a look but that doesn't look like a deployment ID, can you follow this: ?pages-deployment-id
Flare
Flare•9mo ago
The Pages deployment ID is a unique build identifier. It's the UUID in the browser bar (for example, a URL would be dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID where the deployment ID looks something like a398d794-7322-4c97-96d9-40b5140a8d9b). This ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.
Marcel Overdijk
Marcel OverdijkOP•9mo ago
Hi @Walshy | Deploying here is the deployment id: 920e6411-8ba5-4339-9b1e-6cd30f165c98 (and thx for looking into this)
Walshy
Walshy•9mo ago
There's a bug causing this to fail when it wouldn't usually. It seems you have [env.production] but your d1 binding isn't in there, can you put it in the environment?
Marcel Overdijk
Marcel OverdijkOP•9mo ago
Thx a lot! I indeed had this in my wrangler.toml: 
[env.production]
compatibility_date = "2024-04-05"
[env.production]
compatibility_date = "2024-04-05"
and actually don't where it came from... I think from https://blog.cloudflare.com/pages-workers-integrations-monorepos-nextjs-wrangler $ npx wrangler@latest pages download config <PROJECT_NAME> but to be honest I'm not sure. Removing these 2 lines solved my issue and I was able to deploy my Pages - Functions - D1 - Prisma proof of concept 💪

Did you find this page helpful?