Worker Offline on Bitmern Solo (Diagnose & Fix)

Worker Offline on Bitmern Solo (Diagnose & Fix)

A worker can vanish from the Bitmern Solo dashboard while AxeOS or ASIC firmware still looks “connected.” That split is confusing — and it is not the same problem as never getting accepts, or as turning on email alerts after the fact.

If Bitmern Solo shows a worker offline, empty, or missing while the miner UI still claims a pool connection, run an ordered triage: Wi-Fi and power, matching coin tab, username WALLET.worker with password x, stranded stratum (wrong host or port), then decide whether to restart the board or re-point fields. For BTC home/Bitaxe, easy-start stays :3132 (never treat :3102 as default). This post does not invent a product “offline after N seconds” rule.

This is the offline / disappeared-worker checklist. Alerts that mail you when shares stop live in email alerts setup. If accepts never started, use Bitaxe not submitting shares first. How to read the live cards once the row is back: dashboard workers / shares / effort. Field wiring: AxeOS setup. Reject path (accepts exist, rejects loud): rejected shares fix.

Bitmern Solo is solo infrastructure: flat 1% fee on finds only, you keep 99%. Fee context stays light here — the job is getting the worker visible and hashing again.

Offline on the dashboard ≠ “no shares ever”

Three patterns get mixed up:

1. Never had accepts - firmware may say connected, but Bitmern Solo stays at 0 workers and shares never climb. That is the no-shares path.
2. Was healthy, then went quiet - worker row existed, shares moved, then the row shows offline, empty, or disappears while the board still looks busy. That is this post.
3. You want mail when silence lasts - configure email alerts after the worker is healthy. Alerts notify; they do not replace stratum triage.

Do not invent a Bitmern Solo product default that “offline means exactly N seconds of silence.” Read the live Workers view, your miner UI, and the ordered checklist below. Alert delay defaults belong in the alerts guide, not as a dashboard physics claim here.

What usually makes a worker look offline

Common causes on Bitaxe-class and small ASIC desks:

1. Wi-Fi or power drop - board rebooted, AP kicked the client, guest network isolation, or a brief outage that left stratum stranded.
2. Wrong coin tab - miner pointed at BTC while you are staring at LTC (or another coin) on the account.
3. Wallet.worker rename or typo - suffix changed, dot missing, or username prefix no longer matches the registered receive wallet for that coin.
4. Stranded stratum - still aimed at an old pool URL, wrong *.bitmernsolo.com host, or a port that never worked for that board class.
5. Firmware “connected” without account mapping - dial tone on the miner does not prove the dashboard sees the worker.

Separate these from high rejects with climbing accepts — that is the rejected shares checklist, not an empty-row offline case.

Ordered fix checklist

Run top to bottom. Stop when the matching coin tab shows the worker again and shares move while the board hashes.

1. Confirm you are not in the never-had-shares case

Symptom: Board never produced accepts on Bitmern Solo; dashboard always empty.

Action: Leave this article. Follow no-shares fix. Offline triage assumes the worker mapped at least once, or you are debugging a sudden disappearance after a known-good connect.

2. Power, LAN, and 2.4 GHz Wi-Fi

Symptom: AxeOS unreachable, intermittent disconnects, or the board vanished from the LAN after a router reboot.

Fix: Confirm power and fans. For Bitaxe-class Wi-Fi, prefer a stable 2.4 GHz SSID (or mixed AP with 2.4 enabled). Avoid guest networks that block device access. Open the miner UI from a phone or laptop on the same LAN before you rewrite pool fields. If you cannot load firmware, you are not debugging Bitmern Solo yet.

3. Open the matching coin tab

Symptom: One tab looks empty while another coin might still show history — or you assume “the whole account is down.”

Fix: Open the same coin the miner is pointed at. A BTC-pointed board will not populate LTC. Coin flips: switch coins.

4. Lock BTC easy-start :3132 (never treat :3102 as default)

Symptom: Home Bitaxe on BTC with reconnect loops, “connected” that never settles, or a worker that used to map and now does not.

Fix: Point BTC at:

stratum+tcp://btc.bitmernsolo.com:3132

Username: YOUR_WALLET.worker1 (or your preferred worker suffix after the dot). Password: exactly x.

Never treat :3102 as the Bitaxe / home default. Other VarDiff ports exist once the easy path is stable — see VarDiff ports. Re-pointing to a random higher port before :3132 works cleanly usually makes diagnosis harder.

5. Username and password shape (rename traps)

Required:

WALLET.worker
password: x

Traps that strand mapping: missing dot, spaces, underscore instead of the dot, wrong wallet prefix vs the registered receive address, password not exactly x, or renaming the suffix without realizing the old dashboard row was the previous label.

If you renamed the worker suffix on purpose, expect a new row under the new label once shares land. The old label going quiet is expected — not proof the pool is broken.

6. Stranded stratum — host and primary slot

Symptom: Firmware still shows an old pool URL, a second failover pool stealing the connection, or a host for the wrong coin.

Fix: Put Bitmern Solo on the primary (or only) pool slot. Host must match the coin (btc.bitmernsolo.com for BTC, and the matching *.bitmernsolo.com host for other coins). Save and apply so the board is not still bound to a previous solo pool or a shared-pool URL. Migration checklist if you are mid-move: migrate miners.

7. Restart vs re-point — choose deliberately

Restart the board when Wi-Fi flapped, AxeOS hung, or power recovered but stratum looks half-alive. A clean reboot often restores a known-good config.

Re-point fields when host, port, username, or password are wrong — restart alone will not fix a bad :3102 habit or a mistyped wallet prefix.

After either action, wait until the miner is hashing again, then prove the account side (next step). Do not invent a product SLA for “how many seconds until the row flips online.”

8. Prove it on the Bitmern Solo dashboard

Open the matching coin tab. Confirm:

• Worker row present under the expected label
• Shares moving while the board hashes
• Current Effort leaving a stuck empty reading when attribution works

Card reading stays in the dashboard guide. Here you only verify the offline fix landed on the account, not only on the miner UI.

When to turn alerts back on

Once the worker is healthy, enable email alerts so the next silent failure pages you. Offline mail is a notification layer — it does not replace this triage, and it does not invent luck or find odds.

What this post will not invent

• No product default “dashboard marks offline after exactly N seconds”
• No luck formulas, dollar EV, or find-time promises from downtime length
• No claim that :3102 is the home Bitaxe default
• No competitor fee comparisons

Fee reminder only if you need it: flat 1% on finds; you keep 99%. Offline is an ops signal, not a fee.

Soft next step

Stabilize stratum on the easy path, confirm the worker row and climbing shares on the matching coin tab, then optionally enable alerts so the next drop does not stay silent.

Start mining

Start Mining — after login, open the matching coin tab and confirm workers / shares.

FAQ

Is “worker offline” the same as no shares?

No. No-shares means accepts never land / the dashboard stayed empty from the start — use the no-shares checklist. This post covers a worker that mapped (or should map after a known-good config) and then went quiet or missing.

What BTC port should a home Bitaxe use first?

:3132 on btc.bitmernsolo.com. Never treat :3102 as the Bitaxe / home default. See VarDiff ports.

What username and password does Bitmern Solo expect?

Username WALLET.worker (wallet prefix must match the registered receive wallet for that coin). Password x.

Should I restart or change stratum first?

If fields look correct and the board just recovered from Wi-Fi or power, restart first. If host, port, or username are wrong, re-point — then verify on the dashboard.

Where do email alerts fit?

After the worker is healthy. Setup: email alerts. Alerts watch silence; they do not fix stranded stratum for you.

Where do I confirm the fix on Bitmern Solo?

Matching coin tab → worker row → climbing shares → effort moving when attributed. Guide: dashboard workers / shares / effort.