Binding algod to causes 404 not found


Right now it seems like:

curl http://XXX:8080/v1/status -H “X-Algo-API-Token:XY”

With algod listening on (set in NetAddress) causes a 404 page not found. This works bound to localhost

Has anyone found a method to set algod to bind to to listen?


Did you try just “:8080”? shouldn’t work as far as I know.


Correction, it appears you tried just “” without a port number. “” or “” should work for you.


so it does appear to bind to but the problem is when it does I get a 404 returned

[ttaylor@node]$ sudo netstat -ntlup | grep 8080
tcp6       0      0 :::8080                 :::*                    LISTEN      17213/algod
[ttaylor@node]$ curl http://<external facing ip>:8080/v1/status -H "X-Algo-API-Token: <OMITTED>"
404 page not found

whereas if I change the netaddress back to “”

[ttaylor@node]$ curl http://localhost:8080/v1/status -H "X-Algo-API-Token:<OMITTED>"
[ttaylor@node]$ sudo netstat -ntlup | grep 8080
tcp        0      0*               LISTEN      17255/algod

I’ve also had this problem.:slightly_smiling_face: