Binding algod to 0.0.0.0 causes 404 not found

#1

Right now it seems like:

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

With algod listening on 0.0.0.0:8080 (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 0.0.0.0 to listen?

#2

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

#3

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

#4

so it does appear to bind to 0.0.0.0 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
[ttaylor@node]$
#5

whereas if I change the netaddress back to “”

[ttaylor@node]$ curl http://localhost:8080/v1/status -H "X-Algo-API-Token:<OMITTED>"
{"lastRound":893575,"lastConsensusVersion":"v8","nextConsensusVersion":"v8","nextConsensusVersionRound":893576,"nextConsensusVersionSupported":true,"timeSinceLastRound":12953189576,"catchupTime":33868122324}
[ttaylor@node]$ sudo netstat -ntlup | grep 8080
tcp        0      0 127.0.0.1:8080          0.0.0.0:*               LISTEN      17255/algod
#6

I’ve also had this problem.:slightly_smiling_face: