Node Tile
Confirmed - the node is working properly and the node has been confirmed on the block chain.
Started - the node has been started in Zelcore but not yet confirmed on the blockchain.
Expired - the node missed it's last confirmation block because of either failed benchmarks or it wasn't online. To fix this you need to investigate why the node went offline and once fixed it must be restarted in Zelcore.
DOS - the node was started before it was ready and wasn't confirmed on the blockchain. The DOS timer lasts 180 blocks. You will not be able to restart the node until that timer is 0 and your issues with the node have been fixed.
This is the amount of time you have to perform necessary maintenance on your node or network before your node is up to confirm on the blockchain (which is around 120 blocks).
Maintenance Window is calculated with this equation (120 - (currentHeight - lastConfirmedHeight)) * 2
This means that your node is not setup to have a static IP IP and that you need to make sure your router has a static reservation for your node so the IP does not change after a router reboot.
This checks to see if your node's API and GUI are accessible from the internet. If these ports show closed then you have an issue with either port forwarding or upnp setup.
To fix this using port forwarding you need to forward these ports to your node 16124-16128, 30000-39999
This checks to see if UPNP is enabled and if the ports used by Flux GUI and Flux API are routed to your local node IP address. If this shows disabled, or blank then you have an issue with your upnp setup. (ONLY IF YOU ARE USING UPNP WHICH IS USED FOR MULTI HOME NODE SETUPS)
To investigate this please use this command and check for active flux_backend and flux_ui ports mapped to your local IP. upnpc -l
-
Unable to detect Flux IP- normally an IP update issue. Sometimes running toolbox option 10 will fix this error -
Daemon not yet synced- wait for daemon to sync OR run toolbox option 5 -
Flux geolocation service is awaiting- Network has gone down or node is restarting -
Connection timed out while searching for the gateway- Network has gone down OR node is just booting up. -
Node hardware requirements not met- check benchmark debug log to see what hardware requirement hasn't been met.