Why Train at Home looks stuck on "Running speedtest..."

You start Train at Home, the window shows Running speedtest..., and then nothing changes for hours. It is tempting to assume something broke and restart the app. In most cases nothing is broken: your miner is moving through the registration queue, and the app simply can't tell you.

What is really going on

When your miner registers, it joins a queue and waits for its turn. While it waits, it regularly tries to report its queue position so the app can show it, through a request named register.queue_state. That request fails every time:

register_set_queue_state exhausted retries (3): POST /register/queue_state failed 503:
{"detail":"unsupported: No handler for register.queue_state"}

Since no position update ever arrives, the window keeps showing the last step it knew about, "Running speedtest...", while the miner keeps advancing underneath. The detailed version of this, with the log fields to read, is in the queue position guide.

What about "Failed to run speedtest"?

You may also see this line in the log:

Failed to run speedtest: Unable to connect to servers to test latency.

It looks alarming, but it is logged at debug level and is non-fatal: registration continues past it. It is not what is holding you back. If the speed test result itself looks too low, that is a different question, covered in the speed test guide.

Where the real state lives

The real state is written to Train at Home's CLI log:

~/Library/Logs/IOTA Train at Home/<YYYY-MM-DD>-cli.log

Look for 'position' values going down over time. subnera automates exactly that: it reads this log on a timer and shows your queue position, its trend and an ETA in the menu bar, read-only and from local files by default, with only an anonymous daily update check. See how to install it.

What to do

1. Don't restart the app because the screen looks frozen. A restart gets a new queue id and puts you at the back of the line.
2. Check the real position, in the log or the menu bar. If it goes down, you are fine.
3. If it goes up (▲), something re-registered you: stop restarting and let it run.
4. If the log has not moved for several minutes and the menu bar shows off, something really is wrong. Start with the troubleshooting guide.