http://localhost:4000 about miningcore HOT 5 CLOSED

use 127.0.0.1:4000/api/

from miningcore.

Take a look at the wiki page for the API.
it's 127.0.0.1:4000/api/pools/...

from miningcore.

Hello,
Thank you everyone for your input.
Because the documentation was pointing to server:4000/api I was lead to believe that /api itself would return values but instead returned a 404 and for some reason, the documented endpoint calls were returning an "internal server error".
I restarted Miningcore a few times and still had the same issue.
Finally I just restarted the whole server last night and like magic the issue went away and api was functioning.
I dont know why i was getting an internal server error since it was a fresh install from about two weeks ago and havent changed anything except for the pool configurations.
I believe the api didnt bind correctly because the port my been used by another resource during launch? idk just speculation...
Anyway thanks for the help, the issue has been resolved.

from miningcore.

It can cause an error or a 404 error if the web server is not configured as a reverse proxy to the api. The miningcore api server is only capable of http communication. If the web interface works on https, port 4000 reverse proxy in nginx configuration (/etc/nginx/sites-enabled/) is required

Example:

server {

    root /var/www/yourdomain/html;

index index.html index.htm index.nginx-debian.html;

    server_name yourdomain;

    location / {
           
            try_files $uri $uri/ =404;
           
    	}
    location /api/ {
    proxy_pass http://127.0.0.1:4000/api/;
		}

from miningcore.

Hi,
Thanks for the info. I already have it setup and the website is running.
Thanks!

from miningcore.