Troubleshooting
FlameWire miners live and die by their performance weight. If your node drops below threshold it stops earning ALPHA until the issue is resolved. The checklist below covers the most common problems operators run into—sync stalls, bad firewall rules, insufficient resources—and the quickest verified fixes. Work through the relevant row, verify after each step, and your weight should rebound within one validator cycle (~15 minutes).
weight = 0 even after an hour
Throughput test below minimum threshold
Ensure chain node is fully synced and not disk‑bound; verify RPC port accepts connections only from gateway IPs and isn’t rate‑limited by OS firewall.
“Registration failed: Insufficient TAO”
Wallet lacks the TAO fee needed for subnet registration
Top up wallet with ≥ 0.01 TAO, then rerun register.
High p95 latency score
Disk or network bottleneck; node lagging behind head block
Check NVMe health, look for I/O wait in top; upgrade bandwidth or peers if sync is slow.
Frequent container restarts / OOM kills
Memory exhausts or uncaught exception
Increase RAM/Docker limits; update miner client; inspect logs for stack trace.
Ethereum trace/debug calls time out
Geth archive under‑spec’d or Erigon pruning enabled
Switch to Erigon with recommended specs or add CPU+IOPS to Geth; confirm archive flags (--gcmode=archive, pruning off).
“RPC 403 Forbidden” from gateway
API key revoked or miner secret outdated
Rotate miner secret in dashboard, restart miner with new credential.
Disk usage ballooning
Log files or chain DB unchecked
Enable log rotation; verify Geth tracing not accidentally on (doubles disk).
Validator pings show mismatched block numbers
Node out of sync
Restart chain client; fix peers; verify system clock.
Unauthenticated traffic spikes in logs
RPC port exposed publicly
Tighten firewall: allow only gateway IP ranges; bind RPC listener to 127.0.0.1.
Need more help? Share your UID, last 200 lines of miner logs, and hardware specs in DM on Discord - we will try to help you as soon as possible.
Last updated