I am trying to delete few cloudflare pages but I keep getting An unknown error occured.

I am trying to delete few cloudflare pages but I keep getting An unknown error occured. Contact your account team or Cloudflare support: https://cfl.re/3WgEyrH. (Code: 8000000) . The URL for the pages projects are 1) https://pages-assets-0.pages.dev/ 2) https://pages-assets-1.pages.dev/ . I created those projects using npx wrangler. It was working fine till today afternoon and all of a sudden I am getting this issue
8 Replies
Walshy
Walshy5mo ago
Hey, I've escalated this to support to triage
andreo
andreo5mo ago
Hi @krizh I've reached out through DM to get some details. Please share them with me when you're around. Thank you!
krizh
krizhOP5mo ago
Hi , thanks for the support . the issue is fixed . I am able to delete the pages . Thanks
andreo
andreo5mo ago
Glad to hear that! Thanks for reaching out and have a good day. (:
Chris (stof) Langton
This is happening for over a week, been trying every day
{ code: 8000010, message: "Cloudflare Pages is not properly installed on your Git account, this may cause deployments to fail. Refer to https://developers.cloudflare.com/pages/platform/git-integration/#cloudflare-pages-is-not-properly-installed-on-your-git-account-this-may-cause-deployments-to-fail" }
{ code: 8000010, message: "Cloudflare Pages is not properly installed on your Git account, this may cause deployments to fail. Refer to https://developers.cloudflare.com/pages/platform/git-integration/#cloudflare-pages-is-not-properly-installed-on-your-git-account-this-may-cause-deployments-to-fail" }
Yeah, it's revoked now, well done. so what? I'm trying to delete a project.. obviously it broke half way.. Now what?
curl 'https://dash.cloudflare.com/api/v4/accounts/e302589106b4c4287aebe65763eb4f80/pages/projects/triage-by-trivial-security' --compressed -X DELETE -H <...stuff...>
-----------
HTTP/3 500
date: Tue, 30 Jul 2024 01:21:40 GMT
content-type: application/json; charset=UTF-8
cf-ray: 8ab188252b03a97f-SYD
cf-cache-status: DYNAMIC
content-encoding: gzip
strict-transport-security: max-age=86400; includeSubDomains
vary: Origin, Accept-Encoding
access-control-allow-credentials: true
cf-auditlog-id: 0191013a-534f-7591-88ff-e29ab4edb59d
content-security-policy: object-src 'none'; script-src 'nonce-MjYwMjk4ODk5MSwyMjA0MTkzNDI2' 'unsafe-eval' 'strict-dynamic' 'report-sample' https:; base-uri 'self';
x-content-type-options: nosniff
x-envoy-upstream-service-time: 15019
server: cloudflare
alt-svc: h3=":443"; ma=86400
{
"result": null,
"success": false,
"errors": [
{
"code": 8000000,
"message": "An unknown error occured. Contact your account team or Cloudflare support: https://cfl.re/3WgEyrH."
}
],
"messages": []
}
curl 'https://dash.cloudflare.com/api/v4/accounts/e302589106b4c4287aebe65763eb4f80/pages/projects/triage-by-trivial-security' --compressed -X DELETE -H <...stuff...>
-----------
HTTP/3 500
date: Tue, 30 Jul 2024 01:21:40 GMT
content-type: application/json; charset=UTF-8
cf-ray: 8ab188252b03a97f-SYD
cf-cache-status: DYNAMIC
content-encoding: gzip
strict-transport-security: max-age=86400; includeSubDomains
vary: Origin, Accept-Encoding
access-control-allow-credentials: true
cf-auditlog-id: 0191013a-534f-7591-88ff-e29ab4edb59d
content-security-policy: object-src 'none'; script-src 'nonce-MjYwMjk4ODk5MSwyMjA0MTkzNDI2' 'unsafe-eval' 'strict-dynamic' 'report-sample' https:; base-uri 'self';
x-content-type-options: nosniff
x-envoy-upstream-service-time: 15019
server: cloudflare
alt-svc: h3=":443"; ma=86400
{
"result": null,
"success": false,
"errors": [
{
"code": 8000000,
"message": "An unknown error occured. Contact your account team or Cloudflare support: https://cfl.re/3WgEyrH."
}
],
"messages": []
}
Erisa
Erisa5mo ago
Generally would prefer if you could make your own thread as these issues are often related to individual account state and it makes escalating them easier
ale
ale5mo ago
hi Christopher, you should soon receive an email from Support to keep track of your case
Chris (stof) Langton
As the issue was first encountered during the same time of this report, and coincided with status email stating the issue was resolved around the same time the comment here says it was fixed, these made it very obvious they were related and I've read here that created new threads for things when customers didn't research to find existing issues is generally not met with politeness
Want results from more Discord servers?
Add your server