-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Server not Available #508
Comments
Based on the provided information, there doesn't seem to be any issue with starting the backend server using uvicorn. The server is running successfully on http://127.0.0.1:3000, and the application startup has completed without any errors. However, since you mentioned starting both the backend and frontend, it's possible that there could be an issue with the frontend part (npm start). The output provided here only pertains to the backend server. If you are encountering any issues with the frontend, please provide additional information or error messages related to that part of your application. |
@linxule the 500 errors are suspicious. There should be some logs from uvicorn--can you share those? |
For Frontend, Error message in the browser is "ERROR: Failed connection to server. Please ensure the server is reachable at ws://localhost:3001/ws."
For Backend, there seems no be no error:
|
Try adding --host 0.0.0.0 to the uvicorn command
|
Backend works.
Encountered the same error with frontend.
|
I have also enabled |
I believe I have the same issue. The backend server starts fine at port 3000 The frontend comes up on port 3001, then tries to connect to The node app proxies |
but then the
|
I tested the endpoint and got
|
Was working earlier, but did |
tl;dr: downgrade to node 16 and it works again. |
The issue seems to be related to this change from a few hours ago: 1ae3f1b And the cause seems to be this issue: nodejs/node#40537 I don't know the proper fix, but downgrading node to v16 goes around the issue by using |
Alternatively, for node 17+, start your backend with:
|
@foragerr amazing. thank you so much for this! |
It seems that |
Thank you for time and consideration!
The text was updated successfully, but these errors were encountered: