Closed bitnom closed 11 months ago
@bitnom since you are running backend on different IP, did you add it in docker-compose.yaml ?NEXT_PUBLIC_API_BASE_URL in docker-compose.yaml should have backend URL and to avoid CORS in main.py in origin array add the frontend URL if not running locally.
NEXT_PUBLIC_API_BASE_URL
Yes, NEXT_PUBLIC_API_BASE_URL
got auto-replaced and as I forgot to mention, I also added every possible IP combo to the CORS list.
I had to get back to my regular work for now but thinking about it, it might be as simple as not thinking to add a UFW rule (I do have UFW running) for the ports. However, the 404 might indicate something else.
I copied my config.yaml to an AWS server running Ubuntu 22.04 and it ran as expected.
Hey @bitnom , to further solve this issue we've introduced Nginx as a reverse proxy, which should resolve all CORS issue. Please take the latest pull and try again. Even on codespaces, you can run SuperAGI much simply.
Is this issue resolved?
Mac users: Updating Docker Desktop and macOS fixed this error for me
Attempting to load in the browser shows connection errors. The software returns a 404 page
GET http://192.168.0.247:3000/ 404 (Not Found)
which displays this:In the browser console I also have:
and here's the docker log:
I did see #275 but none of the accepted solutions there worked. I replaced all instances of
localhost
and127.0.0.1
with my LAN IP address, and my config.yaml is up-to-date with the latest commit of the config template includingENV: 'DEV'
present.I am on Arch Linux.