🐛 BUG: A request to the Cloudflare API (/memberships) failed. [code: 9109]
See original GitHub issueWhat version of Wrangler
are you using?
2.0.16
What operating system are you using?
Linux (Manjaro)
Describe the Bug
Steps 1-3 work fine per: https://developers.cloudflare.com/pub-sub/get-started/guide/ - validated the pubsub token - “This API Token is valid and active”. exported the token variable to the console. and verified that the token has all account access with Editing rights.
However get the following message when creating a namespace:
~ wrangler pubsub namespace create thenamespacename ✔
✘ [ERROR] A request to the Cloudflare API (/memberships) failed.
Unauthorized to access requested resource [code: 9109]
If you think this is a bug, please open an issue at: https://github.com/cloudflare/wrangler2/issues/new/choose
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:13 (4 by maintainers)
Top Results From Across the Web
API access error 9109 - Cloudflare Community
Hi everyone! While using API with an active whitelist of IP addresses, periodically the request fails with error 403.
Read more >Add error message for a workaround · Issue #1683 - GitHub
This was referenced on Aug 15. 🐛 BUG: A request to the Cloudflare API (/memberships) failed. [code: 9109] #1422.
Read more >Unauthorized to access requested resource (err code: 9109 )
As you are not properly using Cloudflare, you are not providing the correct Cloudflare API key which leads to Cloudflare not recognizing the...
Read more >Cloudflare - Make
The operation failed with an error. [403] Error 9109: Unauthorized to access requested resource. Add the permission to your API Token that is...
Read more >The pfSense Documentation
Fixed: Error dummynet: bad switch 21! when using Captive Portal with ... Added support for new CloudFlare Dynamic DNS API tokens #9639.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
A workaround to this issue is to add an account_id in your wrangler.toml, or set it as an environment variable with CLOUDFLARE_ACCOUNT_ID. We could probably add this tip in the error message itself.
I’m using:
but it still throw this error…