Troubleshooting
Node Shows Offline
Section titled “Node Shows Offline”- Confirm the service is running:
curl http://localhost:8080/health - Check the logs:
tail -50 ~/.ee-cdn/logs/ee-cdn-edge-node.err.log - Verify network connectivity: can your node reach
cp.3dge.app?
Node Appears as a New Node
Section titled “Node Appears as a New Node”If your node shows in the portal as a new entry with no history, it enrolled with a different machine identity. The usual causes:
- The operating system was reinstalled.
- A container node was recreated without a fixed hostname and a persistent machine ID.
/etc/machine-idwas removed or regenerated on Linux.
The previous node’s record still exists, and its Active Node Hours stopped at its last check-in. Your account balance and payouts are not affected.
If none of the above applies, contact us with both node names and the approximate date.
High Memory Usage
Section titled “High Memory Usage”- Check the goroutine count in the admin dashboard (Resources column)
- Normal range: 15-30 goroutines and under 100 MB RAM
- If you’re seeing more than 1,000 goroutines, restart the service
Content Not Cached
Section titled “Content Not Cached”- Your node needs at least one heartbeat cycle (30 seconds) to receive workload assignments
- Check for cached files:
ls ~/.ee-cdn/cache/workloads/ - Make sure your allocated cache capacity isn’t full
WebRTC Connections Failing
Section titled “WebRTC Connections Failing”- Your node needs TURN credentials from the control plane, which arrive via the heartbeat
- Check your logs for the message:
Updated ICE config with TURN credentials - If you’re behind a strict corporate firewall, TURN on port 443 may be required