New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ERROR] ParseError: A request to the Cloudflare API (/accounts/***/workers/services/wildebeest-do) failed. #149
Comments
Same issue. I enabled the unbound paid workers plan. |
@bvwjr Does the paid plan solve the issue? |
No. Signed up for paid plan, getting the same error. |
Same here, just wanted to give the project a try...
|
Hey,
|
So yes, you need the paid plan. Then you can enable durable objects using the provided URL from the error message and your account ID. Regarding the token, since I misunderstood it first: OP added the scopes from the "Edit Cloudflare Workers" API Template to the already created Wildebeest token. I can confirm that it works then. So let's update documentation ;-) Note: as a complete Cloudflare newbie, I was unable to correctly configure the API scopes in the Deploy Button parameters. Perhaps somebody can add this. |
I don't think using Cloudflare Workers Paid Plan and enabling Durable Objects like @The-F4m3 mentioned is enough to fix this issue. My Github Action run or running it locally e.g. I have filed a bug on Wrangler project cloudflare/workers-sdk/issues/2611 I did finish the deployment by doing |
@number5 you also need add new permissions to the API Token. I don't know which is missing. But adding all missing ones compared to the "Edit Cloudflare Workers API" Template to the existing Token solved the permission problem. |
The Authentication error should now be fixed. There was a typo in the API token generation. For existing tokens, manually add the Account Workers Scripts Edit permission to your token. |
Update dependency prettier to v3.0.1
I have tried many times, the deploy sequence always stop at Publish DO ,error log is
cURL for the same token returns code 10000 but with success
I changed worker's default subdomain in the first time deploying, otherwise all default setting.
Tried different browser, same error.
The text was updated successfully, but these errors were encountered: