Stratum Password on Bitmern Solo (Why It’s Just x)

Stratum Password on Bitmern Solo (Why It’s Just x)

The host looks right. The port looks right. The wallet prefix looks familiar. Yet firmware still refuses to authenticate, rejects the session, or never lands accepts — because the stratum password field was filled with a wallet unlock password, an exchange PIN, a blank, or a random string copied from another pool.

If your Bitaxe or home ASIC will not show accepts on Bitmern Solo because the stratum password field is wrong, run an ordered password checklist: confirm the string is already clean (btc.bitmernsolo.com:3132 for BTC easy-start, username WALLET.worker), set password to literally x (not your wallet seed, unlock phrase, or exchange PIN), save and re-apply on the primary slot, then prove first accepts on the matching coin tab. Never treat :3102 as the Bitaxe / home default. This post does not invent Bitmern Solo auth error codes or product “password policy” screens.

This is the stratum-password lane. Wrong host / port shape: stratum URL mistakes. Wallet address rejected / invalid shape: invalid wallet rejects. Shares rejected after connect: rejected shares fix. Worker label chaos: worker naming guide. Field wiring: connect ASIC.

Bitmern Solo is solo infrastructure: flat 1% fee on finds only, you keep 99%. Fee context stays light here — the job is putting the correct password so the board can authenticate and work.

Password ≠ URL mistakes ≠ invalid wallet ≠ rejected shares ≠ naming

Five patterns get mixed up:

1. Wrong stratum password — host/port/user may be close, but password is blank, a wallet unlock string, an exchange PIN, or another pool’s worker password. That is this post.
2. Stratum URL mistakes — wrong scheme, host, or port shape. Use stratum URL mistakes.
3. Invalid wallet rejects — username wallet prefix does not match a valid registered receive address for that coin. Use invalid wallet rejects.
4. Rejected shares after connect — session authenticates; work is rejected for other reasons. Use rejected shares fix.
5. Worker naming / attribution — password is fine; the suffix label is wrong or duplicated. Use worker naming guide.

Do not invent a Bitmern Solo “auth error code table,” a guaranteed login SLA, or a claim that the pool “always returns message X.” The product facts that matter: per-coin hosts (for BTC, btc.bitmernsolo.com), BTC easy-start :3132, username WALLET.worker, password literally x.

What usually looks like “auth failed” when the password is wrong

Common password desks on Bitaxe-class and small ASIC setups:

1. Wallet unlock / seed pasted into password — operators treat stratum like a wallet login and paste the unlock phrase or a password manager entry.
2. Exchange account PIN or API secret — copied from a trading account into the miner’s pool password field.
3. Blank password — some firmwares allow empty; Bitmern Solo expects exactly x.
4. Another pool’s worker password — old CK / public-pool style secrets left in failover or primary slots.
5. Spaces or quotes around x — "x", x, or X (wrong case) depending on how the UI stores the field.
6. Username and password swapped — worker string in password; x in username.
7. Correct password, wrong host/port — looks like auth fail when the string is still on :3102 or a non-coin host (cross-check stratum URL mistakes).

Separate these from a clean auth that still rejects shares (rejected shares fix) or an invalid wallet prefix (invalid wallet rejects).

Ordered fix checklist

Run top to bottom. Stop when the matching coin tab shows the worker under the expected label, fresh accepts move, and firmware is no longer stuck on auth / password / reject-on-login symptoms.

1. Confirm the stratum string shape first

Symptom: You have never verified host/port/user; “password” is a guess.

Action: First pass host / port / user cleanliness. For BTC easy-start:

stratum+tcp://btc.bitmernsolo.com:3132
WALLET.worker
password: x

Never treat :3102 as the Bitaxe / home default. Host must match the coin (btc.bitmernsolo.com for BTC; other coins use their matching per-coin hosts). Only after the string shape is clean do you treat empty accepts as a password problem.

2. Set password to literally x

Symptom: Password field holds anything other than a single lowercase x.

Fix: Clear the field. Type exactly:

x

No quotes. No spaces. No uppercase X if your firmware is case-sensitive. Do not paste a wallet unlock string, seed fragment, exchange PIN, or API secret. Bitmern Solo stratum password is the pool password — it is not your wallet password.

3. Confirm username is WALLET.worker (not the password)

Symptom: Username is only x, or only the wallet with no worker suffix, or password holds the worker label.

Fix: Username must be WALLET.worker where WALLET matches the registered receive address prefix for that coin, and worker is your chosen label. Password stays x. Naming detail: worker naming guide. Invalid wallet shape: invalid wallet rejects.

4. Open the matching coin tab before you blame auth

Symptom: You watch LTC (or another coin) while the board points at BTC — or the reverse — and conclude “password rejected.”

Fix: Open the same coin the miner is pointed at. A BTC-pointed board will not populate LTC worker cards.

5. Clear leftover passwords from failover slots

Symptom: Primary has x; secondary still has an old pool password / secret; board flaps onto the secondary and never stays authenticated on Bitmern Solo.

Fix: Put Bitmern Solo on the primary (or only) pool slot. Clear or disable failover slots that still carry foreign passwords. Save and apply. Also see stratum URL mistakes if host/port differ per slot.

6. Re-save and power-cycle after the password change

Symptom: You typed x but firmware still shows the old auth failure line.

Fix: Save pool settings, reboot the board (or full power-cycle), and watch logs for a new connect / auth attempt — not a stale “bad password” line from before the change.

7. Separate password fail from invalid wallet

Symptom: Password is x; wallet prefix is wrong or not registered for that coin.

Fix: Leave this post and use invalid wallet rejects. Password x does not repair a bad receive address.

8. Separate password fail from rejected shares after connect

Symptom: Session authenticates; accepts still fail or reject after work starts.

Fix: Use rejected shares fix. That is not a stratum-password problem.

9. Prove first accepts on the Bitmern Solo dashboard

Open the matching coin tab. Confirm:

• Worker row present under the expected WALLET.worker label
• Fresh accepts moving (not stuck empty)
• Hashrate reading believable 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 password + string landed work on the account.

10. Soft fee reminder only after work lands

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

When URL mistakes, invalid wallet, rejected shares, or naming is the real story

If host/port/scheme is wrong, switch to stratum URL mistakes. If the wallet prefix is invalid for the coin, use invalid wallet rejects. If shares reject after a clean auth, use rejected shares fix. If the worker label is duplicated or confusing, use worker naming guide. First-time fields: connect ASIC.

What this post will not invent

• No Bitmern Solo product “auth error code” table or password-policy screen
• No claim that :3102 is the home Bitaxe default (easy-start is :3132)
• No “first accept within N seconds” guarantee after a correct password
• No luck formulas, dollar EV, or find-time promises from a correct password
• No competitor fee comparisons

Fee reminder: flat 1% on finds; you keep 99%. Password x is stratum auth, not wallet security theater.

Quick retest sequence after changing the password

After you replace a wallet unlock string, exchange PIN, or blank with x, do not stare at a stale firmware line forever. Use a short retest loop:

1. Save the stratum string again (BTC easy-start still btc.bitmernsolo.com:3132, WALLET.worker, password x).
2. Reboot or power-cycle the board so it opens a new auth attempt.
3. Watch for a clean connect instead of another bad-password / auth-reject line.
4. Open the matching coin tab and wait for the worker row + first accepts — not for a luck promise.

If the board connects cleanly then rejects shares, leave this post and use rejected shares fix. If the wallet prefix is wrong, use invalid wallet rejects.

Soft next step

Lock password to literally x, keep BTC easy-start on btc.bitmernsolo.com:3132 with WALLET.worker, clear foreign passwords from failover slots, then confirm first accepts on the matching coin tab before you chase deeper hardware or share issues.

Start mining

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

FAQ

Is the Bitmern Solo stratum password my wallet password?

No. Stratum password is literally x. Never paste your wallet unlock phrase, seed, or exchange PIN into the miner pool password field.

What BTC port should a home Bitaxe use first?

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

What username and password does Bitmern Solo expect?

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

Does Bitmern Solo publish an auth error-code table for wrong passwords?

This guide does not invent that. Use the ordered checklist: correct string, password x, primary slot, prove accepts.

Can a blank password work?

Do not rely on blank. Set password to exactly x, save, re-apply, and prove accepts.

Where do invalid wallet rejects fit?

If password is already x but the wallet prefix is wrong or unregistered for that coin, use invalid wallet rejects.

Where do I confirm the fix on Bitmern Solo?

Matching coin tab → worker row → fresh accepts → believable hashrate. Guide: dashboard workers / shares / effort.