Trying one of the provided bash scripts:
curl -X POST http://127.0.0.1:8181/api/execute -H "Content-Type: application/json" -d '{"command":"version"}'
gives:
|
curl: (56) Recv failure: Connection reset by peer
Though scaller.log shows:
2025/11/06 01:42:40 Server is starting on :8080...
2025/11/06 01:42:40 Server is running on :8080...
How to troubleshoot/fix this using exec?
Running a sidecar container and poke the API from inside doesnt seem to work either so is it right to assume there is nothing listening on 8080?
docker run --rm -it --network container:sekin-sekai-1 curlimages/curl \
-sv -H "Content-Type: application/json" \
-d '{"command":"version","args":{}}' \
http://127.0.0.1:8080/api/execute
Sekaid seems to be rolling and getting blocks:
INF executed block height=8588 module=state num_invalid_txs=0 num_valid_txs=0
Trying one of the provided bash scripts:
curl -X POST http://127.0.0.1:8181/api/execute -H "Content-Type: application/json" -d '{"command":"version"}'gives:
|
curl: (56) Recv failure: Connection reset by peerThough scaller.log shows:
How to troubleshoot/fix this using exec?
Running a sidecar container and poke the API from inside doesnt seem to work either so is it right to assume there is nothing listening on 8080?
Sekaid seems to be rolling and getting blocks:
INF executed block height=8588 module=state num_invalid_txs=0 num_valid_txs=0