search

Snipa22 / nodejs-pool

Other
480 stars 423 forks source link

Web interface never appearing #493

Open OlMi1 opened 2 years ago

OlMi1 commented 2 years ago

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:

To                         Action      From
--                         ------      ----
8080                       ALLOW IN    Anywhere
8080/tcp                   ALLOW IN    Anywhere
8080 (v6)                  ALLOW IN    Anywhere (v6)
8080/tcp (v6)              ALLOW IN    Anywhere (v6)
S1700 commented 2 years ago

Is it meant to be on port 8080?

We have the same issue and we are getting Connection Refused on /admin.html and on port 8001

S1700 commented 2 years ago

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

OlMi1 commented 2 years ago

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). Currently working on my own fork of it with improved docs and already edited a lot but I'm not really understanding what env PATH=$PATH:pwd/.nvm/versions/node/v8.9.3/bin node sql_sync.js wants to do since it just errors... I'm completely lost on this shit repo. I am getting a connection refused on 8080 too and the readme here seems to be absolute shit. It would be great to exchange info about the issue if one of us finds any. Until then, good luck! (And please tell me if you find a fix)

S1700 commented 2 years ago

yh ill try solving this, good luck with your own fork

OlMi1 commented 2 years ago

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.

OlMi1 commented 2 years ago

We have the same issue and we are getting Connection Refused on /admin.html and on port 8001

Okay so I think I found how we can check. Run pm2 list and the namespance API should appear, I think?

S1700 commented 2 years ago

When I run pm2 list I do have the API module running

OlMi1 commented 2 years ago

Is it displayed in green ('running', 'ok' or sth like that)? And where do you host the pool?

S1700 commented 2 years ago

yup, it's green and so is everything else. What do you mean by where do I host it. like the provider?

helly2 commented 2 years ago

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:

To                         Action      From
--                         ------      ----
8080                       ALLOW IN    Anywhere
8080/tcp                   ALLOW IN    Anywhere
8080 (v6)                  ALLOW IN    Anywhere (v6)
8080/tcp (v6)              ALLOW IN    Anywhere (v6)

im looking at your fork but cant write issues there, is there any way to notify you