Keep your node healthy and up to date with the following tools.
The node status can be seen from the node list and the view details page.
The node’s environment is being prepared
The node is starting up
The node is running.
The node is restarting.
The node is not running correctly. Check the console log for more information.
The node is stopping.
The node has been stopped.
The node is terminating
The node has been terminated. It will remain visible for 60 minutes.
View your node’s CPU, Memory, and Storage performance.
If the CPU or Memory is running high you can increase node size.
When the Storage is running out of space you can increase storage.
The following actions can be found under the
Actions menu in Node Details. They can result in downtime while the node restarts, so be cautious when performing actions on a node who’s downtime could cause issues.
Increase or decrease the node’s CPU size. The node will restart.
The node’s running costs could change after updating the node’s CPU size
Increase the node’s hard drive space. The node will restart.
The node’s running costs could change after updating the storage size
Update the node’s image version. The node will restart.
We always recommend running the network’s latest image version. If the image is out of date the following banner will be displayed in the Node Details page.
The node will be restarted with existing configuration
The node will be stopped.
Storage charges will still be incurred. Terminate the node if you wish to avoid being charged.
Resume a stopped node
The node will be deleted. This is not reversible.
Edit Launch Arguments
Edit a running node’s Launch Arguments by selecting the
Launch Configuration tab and pressing
Edit. The node will restart after saving changes.
Read Dedicated Node Launch Arguments for detailed help.
To debug issues in a node click the
Console Logs button in the node details. The rolling most recent 100 logs are shown
View the node’s action history under
Activity Logs. Values can be expanded to view details and copied