Gonka Host not found: missing from the list, or the page did not load
Not listed means this epoch’s participant list has no such index. Unavailable means the list did not load. If a previous result is still on screen, the page marks it Cached data. Not listed does not prove the machine is off. A mistyped address looks the same as a Host that is truly absent, so separate those first.
| Page status | The list | Next step |
|---|---|---|
| In this epoch | Loaded, and the whole index matches | Record epoch, weight, and models |
| Not listed in the current epoch | Loaded, but this address is absent | Check the identifier and the epoch; do not write weight 0 |
| Unavailable | No list on this attempt | Refresh; weight stays unknown if there was no earlier success |
| Cached data | The screen still shows the previous list | Do not treat it as an absence just confirmed |
On the Gonka monitor, “not listed” and “did not load” are different. Not listed means the list is on screen and your full address is not in it. Unavailable means this attempt produced no list. If a previous result is still showing, the page marks it Cached data. Do not write either case as weight 0 or income 0.
Which branch the page is on
- If the participant count and epoch are visible and the lookup says not listed: this current list has no such index.
- If the count is missing, or the page says unavailable: there is no usable list this time. Refresh once.
- If it is marked Cached data: both absence and participation are still the previous result. That is not a confirmation just made.
- If you expected a miss but it matched: check that you did not copy only the end of the address. The whole value must match. See which identifier to paste.
What to inspect after not listed
- Confirm you pasted the gonka account address, not an inference URL, a public key, or uppercase hex.
- Confirm the epoch on screen is the epoch you meant. The current list is only the current epoch.
- Use the quickstart to see whether the network node and at least one ML node have joined as a Host. The monitor cannot see whether your containers are running.
What to do next
- If the identifier was wrong: correct it and look again. Do not keep the earlier miss as weight 0.
- If the identifier is right, the list is fresh, and it is still not listed: record “not on this epoch’s list.” Weight stays unknown. For credits, see weight and GNK. Do not turn absence into a deduction.
- If it stays unavailable: keep unknown and use the API docs for the current-epoch participants. Do not fill 0 in the monitor.
- The lookup itself does not use a device slot. After you save a device, Free is five per project and Pro is 50.
Illustration
An illustrative branch, not a fault record for a real machine: a gonka1… address with a loaded list that lacks that row is not listed. Pasting an http service address also fails to match and is not listed, but the cause is the wrong identifier. When the page has no epoch at all, the branch is unavailable and weight stays unknown.
Limits
- Not listed does not prove the machine is offline, banned, or absent next epoch.
- Do not copy the document sample’s weight of 10 onto a Host that was not found.
- This page does not restart a node. AI crash analysis is free and cannot control a Gonka host.
Common questions
Does not listed mean the machine is offline?
No. Not listed only means this index is absent from the current participant list. The machine may still belong to the previous epoch, the address may be wrong, or it may not have joined this epoch as a Host. Power state belongs on your own node, not in this line.
It stays not listed after a refresh. What weight do I write?
Do not write 0. Not listed means there is no weight for this Host. The page shows a weight number only after a match. A blank stays unknown.
Does a not-found lookup use an extra free slot?
No. A lookup on the project page does not use a slot. A slot is used when you save Gonka as a device record: five per project on Free, 50 on Pro. Binding it again on the same device does not add a slot.