Nosana host jobs do not match: check in this order
A lookup that never sends, two unknown cells, running jobs at 0, and a large network total are four different situations. Change one condition at a time, then read the next successful result.
| Symptom | Check first | Do not |
|---|---|---|
| No request after paste | Node public key, and no spaces | Try random wallets |
| Unavailable or a dash | Read the same address again later | Write the failure as 0 or NOS |
| No running jobs and the number is 0 | Online state and eligibility on the official node page | Call it offline or hashrate 0 |
Stay with the symptom you actually see
Open the Nosana monitor and keep only this node address. Do not compare it with the network cells above yet. Explain this host’s status line and its two figures. What the counts mean is in node counts.
Check in this order
- No lookup appears: the address must be the node’s public Solana key, Base58, with no leading or trailing spaces, decoding to 32 bytes. A job id does not start a lookup. Wallet versus node is in Host address.
- The status is unavailable, or both cells are dashes: this read did not return counts. Record unknown. Read the same address again later. Do not record 0 and do not record a NOS amount.
- The status is no running jobs and the running cell is 0: that is a successful empty list. On the dashboard, see whether the official page shows the host online, eligible, or assigned a job. Zero is not offline; see idle and offline.
- Completed jobs disagree with what you remember: compare completed jobs only across two successful reads of the same address. A larger network total is expected, because that row does not filter to your node.
- You expected money: the monitor does not provide it. Rules are Host GPUs and rewards in the Nosana docs. The difference between job counts and NOS is in jobs and NOS.
A schematic case
Illustrative, not a fault log: the first refresh says unavailable. The second refresh of the same address shows running 0, completed 4, and the status no running jobs. The record is: first read unknown; second read an empty running list and a completion count of 4. Do not rewrite the first read as 0, and do not write 4 as NOS.
What to do next
- The official docs include Troubleshooting. System, driver, and grid-join steps belong there. The monitor cannot change the Nosana process on the host.
- After the address is correct, saving this host for later uses one device slot for this project. Free is five saved devices per project, and Pro is 50. Another binding on the same saved device does not take another slot.
Limits
Do not use the Train at Home agent on a Mac to restart Nosana. Crash analysis does not read a Nosana host. This page cannot promise when a job will arrive, and it cannot turn counts into a reward.
Common questions
The network shows running jobs, but my node is 0. Is that a fault?
Not yet. The network row does not select your node. Confirm this host’s online state and assignment on the official node page.
Two unavailable reads in a row. Should I store them as 0?
No. Two unknowns stay unknown. After the same address successfully returns numbers, record that read’s running and completed jobs.
Can the monitor restart the node while I am here?
No. It only reads the public job index. Restart, driver, and join steps are in the official Troubleshooting. The Train at Home Mac agent does not control Nosana.