-
Notifications
You must be signed in to change notification settings - Fork 424
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
Web interface never appearing #493
Comments
Is it meant to be on port 8080? We have the same issue and we are getting |
Hold on have you done this step? https://github.com/Snipa22/nodejs-pool#manual-sql-configuration I think that the deploy bash script has a problem with the SQL installation and you need to manually do it |
Didn't even get there. In the end of the deploy.bash the API should start so this is not necessarry, port 8080 appears when manually starting the poolui (and has nothing to do with the API). |
yh ill try solving this, good luck with your own fork |
Thank you. My fork is basically just meant to improve the readme and is exactly same to this pool so if you find something or I do it would apply to both out issues. |
Okay so I think I found how we can check. Run |
When I run |
Is it displayed in green ('running', 'ok' or sth like that)? And where do you host the pool? |
yup, it's green and so is everything else. What do you mean by where do I host it. like the provider? |
im looking at your fork but cant write issues there, is there any way to notify you |
I ran everything in the readme just like it is stated there but I am stuck at step 6. Connecting to /admin.html & :8080 (without / at the end or at any subfolder, just IP:8080) results in a "connection refused" even though I started the poolui stuff correctly (running on localhost:8080). What should I do now? Opening the port does not help. (sudo ufw allow 8080)
a curl to localhost:8080 works.
My firewall config is:
The text was updated successfully, but these errors were encountered: