🐛 BUG: HTTP status 403 returned when fetching from worker on non-local wrangler dev
See original GitHub issueWhat version of Wrangler
are you using?
2.0.6
What operating system are you using?
Mac
Describe the Bug
It’s outlined in the readme of the repo I put together, but I’ll paste here too:
- Install deps
- Run with
pnpm dev
(Runs in non-local mode on Cloudflare’s network) - Load the in a browser application @ http://localhost:8787
- Observe stringified HTTP 403 error due to the
fetch
call - With the terminal still open, turn on local mode with
l
- After the application rebuilds, reload the browser window
- Observe the app rendering the response handled by the worker as expected
Issue Analytics
- State:
- Created a year ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
403 Forbidden on `wrangler dev` with Durable Workers starter ...
Describe the bug. I wanted to try out Durable Workers, but I'm getting this error when running wrangler dev when following the guide....
Read more >403 Forbidden on `wrangler dev` - Cloudflare Community
I am trying to get started with my first workers project, and after running ... Error: HTTP status client error (403 Forbidden) for...
Read more >ssl - CloudFlare workers fetch HTTPS works on workers.dev ...
When I test locally ( wrangler dev ) and even publish to a workers subdomain this works fine. When I curl https://foo.bar.workers.dev/myEndpoint ...
Read more >403 Forbidden - HTTP - MDN Web Docs - Mozilla
The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.
Read more >Glitch 403 forbidden. py of your django project and create a ...
Worker works in “wrangler preview” and “wrangler dev” and when deployed to ... The 403 Forbidden error is an HTTP status code that...
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
I think the best bet is to move the API to a completely different Zone.
From the discussion we have had, I don’t think that this is a bug with Wrangler itself, but more of a concern of how Workers themselves function. So I’m going to close this issue.
@chrstntdd - please comment or reopen the issue if you feel there is more that Wrangler needs to do here.