-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Error: connect ECONNREFUSED 127.0.0.1:3000 #568
Comments
Looks like you forget to start the backend or mock server at |
Open file opendevin/frontend/vite.config and there corect these lines of code "const BACKEND_HOST = process.env.BACKEND_HOST || "127.0.0.1:3000"; // check BACKEND_HOST is something like "example.com" // check BACKEND_HOST is something like "example.com" |
Why do you need the backend to be accessible over the network? Are you running backend and front end on different boxes? I suspect your setup will run fine if you dropped If you need to keep it, you need to set the environment variable |
You should check the log. I guess it is also related to #573 |
@JustinLin610 - Yes it is the issue Success have a question though, do I have to start the back end separately? If so, where can I have a nohup added? |
The newest makefile has a |
@lijom80 You don't need to, now |
i've got the same problem with the new make run command, giving me this error:
|
Backend always take some time to start, it there any output logs from backend? |
no thanks, for me the issue was some cuda library not properly installed on the wsl. |
My services are running as well. I realised after reboot the node, and
running backend again, it installed few more components.
Also, the new make run does not run the backend automatically for some
reason.
I have a question, what is the ideal infra requirements for make it run
smoothly?
…On Wed, 3 Apr 2024, 22:02 Francesco Dotta, ***@***.***> wrote:
no thanks, for me the issue was some cuda library not properly installed
on the wsl.
I solved it.
—
Reply to this email directly, view it on GitHub
<#568 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BF3SFTXL2WJLBENCJ2EGGO3Y3QVLLAVCNFSM6AAAAABFTF6E7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGA3TAMBZHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Seems user can run opendevin now. But maye still keep an eye on backend launch slowly problem. |
Describe the bug
on the frontend, I am getting this error
ERROR: Failed connection to server. Please ensure the server is reachable at ws://:3001/ws.
at the backend, I am getting the below error
Running the app...
VITE v5.2.7 ready in 578 ms
➜ Local: http://localhost:3001/
➜ Network: http://:3001/
➜ press h + enter to show help
4:38:45 PM [vite] http proxy error: /litellm-agents
Error: connect ECONNREFUSED 127.0.0.1:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1481:16)
4:38:45 PM [vite] http proxy error: /litellm-models
Error: connect ECONNREFUSED 127.0.0.1:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1481:16)
4:38:45 PM [vite] http proxy error: /litellm-models
Error: connect ECONNREFUSED 127.0.0.1:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1481:16) (x2)
4:38:45 PM [vite] http proxy error: /litellm-agents
Error: connect ECONNREFUSED 127.0.0.1:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1481:16)
4:38:45 PM [vite] ws proxy error:
Error: connect ECONNREFUSED 127.0.0.1:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1481:16)
Setup and configuration
Current version:
commit c37124d (HEAD -> main, origin/main, origin/HEAD)
Author: Xingyao Wang xingyao6@illinois.edu
Date: Tue Apr 2 14:58:28 2024 +0800
My config.toml and environment vars (be sure to redact API keys):
My model and agent (you can see these settings in the UI):
Initializing agent (may take up to 10 seconds)... nothing after that
Commands I ran to install and run OpenDevin:
Steps to Reproduce:
@cd frontend && npm run start -- --port $(FRONTEND_PORT) --host "0.0.0.0" <- added 0.0.0.0 to be accessible over the network.
Logs, error messages, and screenshots:
Additional Context
The text was updated successfully, but these errors were encountered: