Skip to main content
Use this checklist when the Agent is installed but miner data does not appear.

​
1. Confirm the Agent is installed and online

In Nonce, verify that:
  • the farm has an Agent
  • the Agent is marked as installed
  • the Agent is online
If Agent installation was just completed, wait a few seconds and refresh the page once.

​
2. Check whether the scan task actually ran

Open the farm task list and look for the scan task.
  • If the task is still pending, wait for it to finish.
  • If the task failed, review the task output first.
  • If there is no scan task at all, the request may not have been submitted successfully.

​
3. Verify the IP range is correct

A successful Agent installation does not guarantee that the configured scan range matches the miner subnet. Common problems:
  • wrong subnet
  • scanning the management network instead of the miner network
  • scanning a range that is too broad
  • newly moved miners now living in a different VLAN or subnet

​
4. Check miner credentials on the Agent host

If the miner password was changed from the default, follow the FAQ instructions to update the Agent config:

​
5. Check the Agent service directly on the host

Useful commands: 
sudo systemctl status nonce-agent
nonce-agent summarize-ip-list
nonce-agent summarize-miner-scan-report -v
nonce-agent get-miner-meta <miner-ip> --validate --no-cache --raw --json
These commands help answer:
  • is the service running
  • which IPs are in the current monitoring list
  • what happened during recent scans
  • whether the Agent can fetch a miner directly from the host

​
6. Review local Agent reports

The Agent writes scan and fetch reports locally. These are often the fastest way to understand why miners are missing. Typical report locations: 
~/.nonce-agent/reports/MINERS_SCAN_REPORT/
~/.nonce-agent/reports/MINERS_FETCH_REPORT/failed_ips.txt
~/.nonce-agent/reports/MINERS_FETCH_REPORT/succeed_ips.txt
These files can show:
  • which IPs were scanned
  • which IPs were skipped
  • which miners were found
  • which IPs failed during metadata collection

​
7. If some miners appeared once and then stopped updating

This usually means one of these conditions happened:
  • the miner became unreachable
  • miner metadata fetch started failing repeatedly
  • the miner is no longer inside the expected IP range
  • the backend already marked the miner data as stale because no fresh update arrived for a while
If this happens, run another focused manual scan on the affected subnet and test one affected miner directly with: 
nonce-agent get-miner-meta <miner-ip> --validate --no-cache --raw --json

​
8. If the task succeeded but the Miners page still looks stale

The backend may already have processed the upload while the current page is still showing cached data. Try this before deeper debugging:
  • refresh the Miners page
  • reopen the farm page
  • check the task detail page for completion
  • wait up to the next regular refresh window if you are relying on background refresh rather than manual scan

​
9. If a miner was removed manually, why does it not reappear in the list

If a miner was previously removed manually from the list, it will not be added back automatically. Run another scan. After Agent discovers and reports the miner again, it will reappear in the Miners list.

​
10. Why are miners still missing after checking everything above

Review the Supported Miners and Firmware page. If the miner model or firmware version is not on the supported list, Agent may fail to identify it correctly or collect enough data for it to appear in the list.

​
When to Escalate

Collect logs and escalate to the team if:
  • the Agent is online but every scan task fails
  • direct fetch with get-miner-meta fails for miners that are definitely reachable
  • the scan task succeeds but no miner data is ever ingested
  • only one miner brand consistently fails while others work in the same subnet