Repository navigation
Facing issues while running the development server - Error while proxying request in localhost:8000/providers to http://localhost:3000/ [ECONNREFUSED] #6382
Description
Description of the issue
I'm trying to start a development server for Huly platform in my Windows machine. Rush has installed and linked all the dependencies but I'm getting errors while starting the server. The error says
Error while proxying request in localhost:8000/providers to http://localhost:3000/ [ECONNREFUSED]
My environment
- Version of huly - 0.6.11
- Browser (and version) - Brave
- Your operating system (and version) - Windows 11
Steps to reproduce
Clone the repository with --depth=1 flag. Go to the /dev/prod folder and install the dependencies by running rush install
Once done, run the development server by typing rushx dev-server
Application is starting, I can see the frontend but nothing is working. Even registration is throwing an error. If there are any CORS issues, they should be resolved. Or else, let me know if there's any config I'm missing while starting the dev-server.
Activity
lexiv0re commentedon Aug 23, 2024
@DezyNation it looks like you skipped the step with building and getting up the docker containers. Check https://github.com/hcengineering/platform?tab=readme-ov-file#build-and-run.
HardasSteel commentedon Aug 27, 2024
I'm not gonna lie to anybody. I have no idea what I'm doing. I was trying to wing it, but I guess I need the figure out what's going on my bad. To everybody that was so serious. I apologize if I messed anything up.I would like to learn what y'all are doing now
MichaelUray commentedon Oct 20, 2026
This reads as a local development setup question (the backend services were not running) rather than a code defect or a concrete feature request. It may be better suited to the community channels or documentation. If maintainers agree, please consider closing.
MichaelUray commentedon Oct 20, 2026
@DezyNation — as explained above, this does not look like something that can be addressed in the codebase. Could you please close this issue if you agree? If you think there is a code change needed after all, please describe what should change.