Documentation

Troubleshooting

Common issues and solutions when working with Inery nodes, monitoring, and GUI.

Node Startup

Node not starting

  • Verify Ubuntu prerequisites, SSH/Git, and that the clone completed cleanly
  • Confirm ports 8888, 7778, 8080, 9010, and 8900 are not in use
  • Inspect logs: tail -f nodes/inery/nodine.log or docker-compose logs -f

Port conflicts

Free or remap conflicting services before starting the node. Default mapped services:

  • 8888 — RPC API
  • 7778 — Monitoring dashboard
  • 8080 — Database GUI
  • 9010 — P2P
  • 8900 — Wallet (kined)

Git clone fails

  • Check network connectivity to git.webservice-host.net
  • Verify authentication credentials in the clone URL

Verification Checklist

cline get info
# or
curl -s http://localhost:8888/v1/chain/get_info

Healthy response includes head_block_num. Monitoring: http://localhost:7778. GUI: http://localhost:8080.

Wallet Issues

Locked wallet

  • Use cline wallet unlock -n <name> with your password.

Wallet created during genesis

  • genesis_setup.py creates a wallet automatically when none exists. Keep the generated credentials secure.

Docker / Windows Issues

Container Up but localhost refuses connection

Usually caused by Windows CRLF line endings corrupting scripts after clone.

docker-compose down -v
docker-compose build --no-cache
docker-compose up -d
docker-compose logs --tail=60

Prevent CRLF conversion before cloning again:

git config --global core.autocrlf false

GUI not accessible

  • Re-run GUI setup with --force
  • On Docker: docker exec -it inery-node-container python3 /app/scripts/setup_gui.py --force

API Errors

Connection refused on :8888

  • Confirm the node process is actually producing/receiving blocks in logs
  • Wait 15–30 seconds after docker-compose up -d before genesis/GUI setup

403 Forbidden

  • Check HTTP access rules in node config and CORS if calling from a browser
Previous Page<-Inery Orbit SpecsNext PageBest Practices->