Duplicate Workers on Bitmern Solo (Same Name Conflict)

Duplicate Workers on Bitmern Solo (Same Name Conflict)

Two boards fighting one WALLET.worker row is a quiet conflict: the dashboard looks noisy, shares scramble across one label, and reconnects look random even when stratum is fine. That is not a naming-format tutorial, and it is not the healthy multi-Bitaxe fleet path where every board has its own suffix.

If two (or more) miners use the same WALLET.worker string on Bitmern Solo, run an ordered collision checklist: confirm the duel on the matching coin tab, rename one board to a unique suffix, save/apply both firmwares, clear failover that reuses the old name, then prove two clean rows with fresh accepts. Username shape stays WALLET.worker, password exactly x. This post does not invent a product max-workers SLA.

This is the same-name conflict fix. Format rules: worker naming guide. Healthy fleet layout: multiple Bitaxe fleet. Flaps after names are unique: reconnect loops. Row gone: worker offline. Field wiring: AxeOS setup.

Bitmern Solo is solo infrastructure: flat 1% fee on finds only, you keep 99%. Fee context stays light — the job is stopping two boards from overwriting one worker identity.

Duplicate name ≠ naming guide ≠ healthy fleet ≠ offline

Four patterns get mixed up:

1. Duplicate / same-name conflict — two boards share one WALLET.worker string; one row looks busy, weird, or “offline then online” while both hash. That is this post.
2. Worker naming guide — how to format WALLET.worker correctly (dot, no spaces). That is the naming guide.
3. Healthy multi-board fleet — unique suffixes on purpose. That is the fleet guide.
4. Worker offline — row missing or marked offline for path/power reasons. That is the offline fix.

Do not invent a Bitmern Solo product default that “N workers is the hard cap.” Collision triage is about unique suffixes, not a published limit.

What usually drives a same-name duel

Common causes on Bitaxe-class and small ASIC desks:

1. Cloned config — second board flashed or copied with the same worker suffix as the first.
2. Copy-paste habit — every new board gets wallet.bitaxe1 again.
3. Fleet growth without rename — third board joins; suffix never updated.
4. Wrong coin tab — you watch one coin while both boards hash another; collision symptoms look like “ghost” activity.
5. Failover / second slot — same worker string on a secondary pool slot fighting primary attribution.
6. “Offline then online” misread — boards take turns owning the session; the row flaps without a true path failure.

Separate these from format mistakes (missing dot) in the naming guide and from intentional unique-suffix fleets in the fleet guide.

Ordered fix checklist

Run top to bottom. Stop when each physical board has its own WALLET.uniqueSuffix, both (or all) rows look stable on the matching coin tab, and accepts move under the right labels.

1. Confirm you are not offline or in a pure reconnect storm

Symptom: Worker row missing/offline with one board powered down, or reconnect counters climb with already-unique names.

Action: Leave this article. Use worker offline or reconnect loops. Duplicate-name triage assumes two live boards sharing one worker string — not a single dead path.

2. Open the matching coin tab

Symptom: One coin tab looks chaotic while another is calm — or you assume the whole account is “broken.”

Fix: Open the same coin both boards point at (or check each coin if they differ). A BTC duel will not explain LTC noise. Coin flips: switch coins.

3. Prove the collision — two boards, one string

Symptom: Two firmwares show the same WALLET.worker (same wallet prefix and same suffix); dashboard shows one busy/noisy row; hashrate or accepts look inconsistent with one board.

Fix: Physically identify both devices. Read pool username on each miner UI side by side. If the strings match exactly, you have a collision — not a mystery “pool bug.” Note which board you will rename.

4. Rename one board to a unique suffix

Symptom: Both still say .worker1 (or the same custom suffix).

Fix: On one board only, change the suffix after the dot — e.g. YOUR_WALLET.bitaxe1 and YOUR_WALLET.bitaxe2. Keep the wallet prefix aligned with the registered receive wallet for that coin. Password stays exactly x. Save and apply. Format reminders: worker naming. Fleet patterns: multiple Bitaxe fleet.

5. Lock stratum sanity while you rename (BTC easy-start)

Symptom: During the rename you also left a bad port or https paste in the pool field.

Fix: For BTC home boards, prefer:

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

Username: YOUR_WALLET.uniqueSuffix. Password: exactly x. Never treat :3102 as the Bitaxe / home default while you are untangling names. Ports depth: VarDiff ports. Field wiring: AxeOS setup.

6. Clear failover / second slots that reuse the old name

Symptom: Primary renamed; secondary slot still authenticates as the old shared string and steals attribution.

Fix: Put Bitmern Solo on the primary (or only) slot on each board. Clear failover entries that still use the duplicate name or point elsewhere while you diagnose. Save and apply both boards.

7. Wait one refresh — do not chase “offline then online” mid-rename

Symptom: Old shared row looks idle; new suffix appears; you panic and revert names.

Fix: Give the matching coin tab one refresh cycle after both boards apply. Expect the old shared label to go quiet and the new unique label to show accepts. Mid-rename flaps are not automatic proof you need reconnect loops — finish uniqueness first.

8. Prove two clean rows on the Bitmern Solo dashboard

Open the matching coin tab. Confirm:

• Two (or more) worker rows under the expected unique labels
• Fresh accepts moving under each label while that board hashes
• Hashrate readings believable per board (not one row “doing everything”)
• No intentional second board still on the old shared string

Card reading: dashboard workers / shares / effort. Here you only verify the duel ended.

9. Do not invent a “pool limit” when the real issue is a shared name

Symptom: You assume Bitmern Solo “only allows one worker” because the second board never appears as its own row.

Fix: Check firmware usernames first. If both still share one string, rename — do not invent a product max-workers policy from a collision symptom. After unique suffixes apply, two rows should be able to coexist on the matching coin tab without a fabricated account quota story.

Healthy fleet vs emergency rename

A collision fix is a surgical rename on the board that copied the wrong suffix. A healthy fleet plan is deciding suffixes before you power the next board — desk labels, stickers, or a simple bitaxe1 / bitaxe2 / bitaxe3 scheme documented in the fleet guide. Do both: clear the duel now, then stop cloning configs so the next board does not recreate it.

If shares looked “random” under one label during the duel, that was attribution noise from two hashers writing the same identity — not proof that solo variance changed, and not a reason to rewrite known-good stratum hosts after names are unique.

When naming guide, fleet, or offline is the real story

If the problem is a missing dot or bad password shape — not two boards — use the naming guide. If you are designing a healthy multi-board layout from scratch, use the fleet guide. If one row is gone with a single board, use worker offline.

What this post will not invent

• No product max-workers or “hard cap” SLA for Bitmern Solo
• No confirmation-delay SLA for when the second row must appear
• No luck formulas, dollar EV, or find-time promises from unique names
• 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%. Unique worker suffixes are an ops signal, not a fee.

Soft next step

Identify both boards, rename one to a unique WALLET.suffix, keep password x, clear failover reuse, then confirm two clean rows with fresh accepts on the matching coin tab.

Start mining

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

FAQ

Is a duplicate worker the same as a naming-format mistake?

No. Naming-format mistakes are missing dots, spaces, or wrong password. Duplicates are two boards sharing one correct-looking WALLET.worker string.

What username and password does Bitmern Solo expect?

Username WALLET.worker (unique suffix per board). Password exactly x.

Does Bitmern Solo publish a max-workers limit in this post?

No. This article does not invent a product worker-cap SLA. Use unique suffixes for every live board.

Why does the row look “offline then online”?

Two boards can take turns owning one shared identity. Rename one board; do not treat the flap as pure path failure until names are unique.

What BTC port should I use while fixing names?

Prefer :3132 on btc.bitmernsolo.com for home Bitaxe easy-start. Never treat :3102 as the default.

Where does the healthy fleet guide fit?

After collisions are cleared, use multiple Bitaxe fleet for intentional unique-suffix layouts.

Where do I confirm the fix on Bitmern Solo?

Matching coin tab → unique worker rows → fresh accepts under each label. Guide: dashboard workers / shares / effort.