Skip to content
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

[Issue] AWS ECS backend AxiosError Network Error #993

Closed
xmuruaga opened this issue Aug 21, 2023 · 4 comments
Closed

[Issue] AWS ECS backend AxiosError Network Error #993

xmuruaga opened this issue Aug 21, 2023 · 4 comments

Comments

@xmuruaga
Copy link

I had Quivr running locally. Supabase and the rest are configured and everything worked fine in localhost.
I'm now trying to run it in Vercel + AWS ECS Fargate.

I've deployed the frontend to Vercel, and the backend to AWS ECS Fargate. I've also ensured that the SG in AWS have inbound and outbound rules for port 5050.

I've changed the frontend.env to the following:
NEXT_PUBLIC_ENV=production
NEXT_PUBLIC_BACKEND_URL=http://x.x.x.x:5050 (AWS ECS Public IP)

The ECS container is running, I can reach it through the browser (status 200):
image

But when trying to create a Brain from the frontend I get the following error:
image

{"message":"Network Error","name":"AxiosError","stack":"AxiosError: Network Error\n at u.onerror (https://....)","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"adapter":["xhr","http"],"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"Accept":"application/json, text/plain, /","Content-Type":"application/json","Authorization":"....."},"baseURL":"http://x.x.x.x:5050","method":"post","url":"/prompts","data":"{\"title\":\"asd\",\"content\":\"asd\"}"},"code":"ERR_NETWORK","status":null}

Has anyone face this same issue?

@lugfug
Copy link

lugfug commented Aug 25, 2023

What was the solution to this issue? I'm having a similar problem.

@Croccodoyle
Copy link

Croccodoyle commented Sep 12, 2023

This was closed with no explanation?

@xmuruaga
Copy link
Author

I closed it because the same is happening in quivr.app live version, and there is already an issue for that.

@jchico77
Copy link

I closed it because the same is happening in quivr.app live version, and there is already an issue for that.

which issue? I'd like to follow it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants