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

(node:42836) electron: Failed to load URL: http://localhost:4927/#/main with error: ERR_CONNECTION_REFUSED (Use electron --trace-warnings ... to show where the warning was created) #27

Closed
liosixer opened this issue Nov 19, 2024 · 5 comments

Comments

@liosixer
Copy link

No description provided.

@prorower40
Copy link

Seeing the same issue in production @daltonmenezes
image

@daltonmenezes
Copy link
Owner

@liosixer @prorower40 It's very difficult for me to help you with just this little information. Could you provide a reproducible repository/example of this problem so I can test and check what's wrong? Check if the port you are reporting is correct, if there is no other service already using it and if the firewall or antivirus is not blocking it.

Copy link

Hello @liosixer. Please provide a minimal reproduction using a GitHub repository. Issues marked with needs reproduction will be closed if they have no activity within 7 days.

@prorower40
Copy link

Hey as this post is from months ago I don't remember exactly how to reproduce but I do know there was an issue in the main process. I had to start my project over beginning with setting up routing via this library and creating a production build with every on every commit to keep tight track that routing was still working in production.

@daltonmenezes
Copy link
Owner

daltonmenezes commented Jan 30, 2025

Hey as this post is from months ago I don't remember exactly how to reproduce but I do know there was an issue in the main process. I had to start my project over beginning with setting up routing via this library and creating a production build with every on every commit to keep tight track that routing was still working in production.

@prorower40 Thanks for the feedback.

I'll be closing this issue for now, in case anyone else faces this problem again, now we have an issue template in the repository to better obtain info and a link to a reproducible issue test repository. This will help us better to resolve any problems that arise, since I was unable to simulate the reported issue in my tests.

@github-actions github-actions bot locked and limited conversation to collaborators Feb 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants