Nubila operators verify activity directly in the dashboard, mainly through:
This is the fastest way to confirm your node is doing real validation work.
1) Validation Tasks Panel (How to read it)
Current Task (CID)
Shows the CID your node is validating right now
If it shows N/A, that can be normal (node is between tasks or waiting for the next job)
Current Block (example: 104°E, 30°N)
Shows the geographic “block” your node is currently assigned to validate
This is the region bucket your node is working on
Task History (TIME / BLOCK / STATUS)
This table is the most important operational indicator.
Healthy signals:
new rows appear over time
Status shows Completed consistently
2) Operation Logs Panel (What “proof of work” looks like)
This panel provides the most direct evidence your node is working.
You should see entries like:
Successfully validated CID …, Lon …, Lat …
Healthy signals:
repeated “Successfully validated CID …” messages
fresh timestamps appearing continuously
consistent success markers with no persistent error loops
3) Quick self-check: “Am I good?”
You’re good if:
Validation Tasks shows recent rows with Completed
Operation Logs shows repeated Successfully validated CID entries
timestamps keep moving forward
If all three are true, your node is running normally.
4) Troubleshooting dashboard issues
A) No new validations/logs for a long time
Try:
Refresh the dashboard page
Confirm you’re connected to the correct wallet
Confirm the node process is running (not paused/crashed)
Restart the node (if VPS/Docker/CLI)
Check system clock accuracy
B) Node looks online, but logs are empty
Try:
wait a few minutes (node may be between tasks)
if it persists, capture screenshots and contact support
C) Timestamps are stuck
Try:
check internet connection / firewall rules
confirm MON balance if the workflow requires signing actions
5) What to send support
When reporting an issue, include:
screenshot of Validation Tasks + Operation Logs
wallet address (operator)
node tier (Cloud/Rainy/Sunny)
deployment mode (Web UI / Docker / CLI)
time window when issue started