# Prodigy returning 403 in Browser's developer console **URL:** \ **Category:** Uncategorized\ **Tags:** usage, aws, server\ **Created:** [March 7, 2023, 10:23am UTC](https://support.prodi.gy/t/prodigy-returning-403-in-browsers-developer-console/6417 "2023-03-07T10:23:42Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\ **Post date:** [March 8, 2023, 1:24pm UTC](https://support.prodi.gy/t/prodigy-returning-403-in-browsers-developer-console/6417/2 "2023-03-08T13:24:50Z")
hi @sparsh-kedia! Thanks for your question and welcome to the Prodigy community 👋 > [@sparsh-kedia](#): > > When i open the browser and send a request to localhost:8080, it opens the prodigy UI but the content isn't loaded and a message appears - `"ERROR:Can't fetch project. Make sure the server is running correctly."` Could you check your Network tab in the browser? There might be more info on why the request failed, rather than just the console line. Typically, a 403 should only happen if there's a [JWT](https://auth0.com/docs/secure/tokens/json-web-tokens) error. Have you modified any JWT settings? If not, one possibility is that JWT cookie can't be reached due to something [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) related, then the token isn't set on the request AUTHORIZATION header so the 403 appears. But if it were a CORS problem, we'd expect to see a CORS warning and then the failed request. To test if this is the problem, can you try setting `"cors": false` in `prodigy.json`. It's not really recommended to turn that off but they could determine if it is a CORS issue through that test. If this does seem to be the issue, you can set the `PRODIGY_CORS_ORIGIN` env var with the proper URLS for CORS. One other possibility is to try to modify your `"host"` in [`prodigy.json`](https://prodi.gy/docs/install#config) from `"localhost"` to either `"127.0.0.1"` or `"0.0.0.0"`. However, this is usually a fix for a different, but somewhat related error: `OSError: [Errno 99] Cannot assign requested address`: > [@OSError: \[Errno 99\] Cannot assign requested address](https://support.prodi.gy/t/oserror-errno-99-cannot-assign-requested-address/89/3): > > So I was poking at this further and I noticed I’m only able to get this working when I use host “0.0.0.0”. With “127.0.0.1” the app starts without crashing but I can’t connect to it from a browser. Some additional information. I’m running this in a docker container on my laptop. Networking is also not my strongest suite but usually when I run into these kinds of issues switching to 0.0.0.0 fixes things slight_smile Here’s my Dockerfile: FROM python:stretch MAINTAINER Michael Becker ENV PYT… Last, another user had a somewhat similar 403 issue with the same Prodigy error message `ERROR:Can't fetch project ...`. Seemed like they forgot to pass a `session_id` which would be required if you set `PRODIGY_ALLOWED_SESSIONS` in your `prodigy.json`. Any chance this could be the problem? > [@Could not fetch project if I run in docker](https://support.prodi.gy/t/could-not-fetch-project-if-i-run-in-docker/4338/4): > > Figured out the issue, it was because I didn't pass the session id. --- _[View the full topic](https://support.prodi.gy/t/prodigy-returning-403-in-browsers-developer-console/6417)._