Bitmern Solo
Bitmern Solo
Log inStart Mining
← Back to blog

Guest WiFi / AP Isolation Killing Bitmern Solo

If guest WiFi, AP isolation, or client isolation is killing your Bitaxe on Bitmern Solo — miner offline on the guest network, stratum blocked by AP/client…

11 min read
Guest WiFi / AP Isolation Killing Bitmern Solo
Guest WiFi / AP Isolation Killing Bitmern Solo

Your Bitaxe sits on the guest SSID, an IoT VLAN, or a client-isolated AP — and Bitmern Solo never sees a durable session. Connecting never clears. DNS for btc.bitmernsolo.com fails or hangs. Or firmware briefly Authorizes, then the worker goes stale because outbound stratum cannot stay open between isolated clients and the internet path you expect.

If guest WiFi, AP isolation, or client isolation is killing your Bitaxe on Bitmern Solo — miner offline on the guest network, stratum blocked by AP/client isolation, or DNS/outbound path broken on an IoT VLAN — run an ordered checklist: confirm BTC easy-start bare host btc.bitmernsolo.com with port :3132 (never treat :3102 as the Bitaxe / home default), username WALLET.worker, password x, then move the board off isolation (or allow outbound stratum/DNS) before you blame “the pool.” This post is not the wifi-drops-stratum lane, the ethernet-vs-wifi lane, the firewall-blocking-stratum lane, the dns-resolve-fix lane, or the vpn-proxy-stratum-fix lane — and Current Effort is not a find guarantee.

This is the guest-WiFi / AP-isolation lane. Wireless flaps without an isolation story: WiFi drops killing stratum. Wired vs wireless choice: ethernet vs WiFi. Router firewall rules (not guest isolation): firewall blocking stratum. DNS-only failures: DNS resolve fix. VPN/proxy path: VPN / proxy stratum fix.

Bitmern Solo is solo infrastructure: flat 1% fee on finds only, you keep 99%. Fee context stays light here — the job is to restore an outbound path when guest / AP isolation blocks the session.

Guest / AP isolation ≠ WiFi drops ≠ ethernet choice ≠ firewall ≠ DNS ≠ VPN

Six patterns get mixed up:

  1. Guest WiFi / AP / client isolation — the SSID or VLAN policy blocks client-to-internet (or client-to-DNS) paths the Bitaxe needs for Bitmern Solo. That is this post.
  2. WiFi drops — the radio flaps without an isolation policy story. Use WiFi drops killing stratum.
  3. Ethernet vs WiFi — choosing wired for stability. Use ethernet vs WiFi.
  4. Firewall blocking stratum — explicit firewall / ACL rules on the main LAN path. Use firewall blocking stratum.
  5. DNS resolve fix — name resolution only, without a guest-isolation root cause. Use DNS resolve fix.
  6. VPN / proxy stratum — traffic forced through a VPN or proxy that breaks stratum. Use VPN / proxy stratum fix.

Do not invent Bitmern Solo “isolation timeout SLAs,” guest-SSID product guarantees, or a claim that Current Effort predicts finds. Product facts that matter for retest: BTC host btc.bitmernsolo.com, easy-start port :3132, username WALLET.worker, password x. Home router guest modes vary — follow your AP’s docs; Bitmern Solo does not publish a guest-SSID compatibility matrix.

What guest / AP isolation usually looks like on a Bitaxe desk

Common desks:

  1. Bitaxe joined the guest SSID “so IoT stays separate” — guest mode enables client isolation by default.
  2. Connecting forever on guest; same board works on main LAN — classic isolation / outbound block.
  3. DNS for btc.bitmernsolo.com fails only on guest — guest DNS sinkhole or no upstream DNS.
  4. Brief Authorized, then dead — outbound TCP to stratum port cannot stay open through isolation.
  5. IoT VLAN allows local discovery only — no path to public stratum hosts.
  6. Phone on guest browses the web; Bitaxe still fails — browsers may use DoH / captive paths; the miner needs plain DNS + TCP :3132.
  7. You already tried WiFi-drop checklists — RSSI is fine; policy is not.
  8. Firewall posts did not help — main-LAN firewall is open; guest SSID is a different network object.

Separate these from pure radio flaps (WiFi drops killing stratum) and from main-LAN ACL stories (firewall blocking stratum).

Ordered diagnose-and-fix checklist

Run top to bottom. Stop when firmware holds a clean Authorized / Subscribed session on a path that allows outbound DNS + TCP to Bitmern Solo, the matching coin tab shows the worker, and accepts can move — without inventing an isolation-timeout product SLA.

1. Confirm BTC easy-start string before you blame the SSID

Symptom: You chase guest settings while the miner still has a wrong host, leftover :3102, or a bare wallet username.

Fix: On the Bitaxe (AxeOS or equivalent), set:

btc.bitmernsolo.com

Port:

3132

Username:

WALLET.worker

Password:

x

Never treat :3102 as the Bitaxe / home default. Wallet must be registered for that coin on Bitmern Solo.

2. Prove the same board on the main (non-guest) SSID

Symptom: Guest fails; you have not A/B tested the primary LAN.

Fix: Move the Bitaxe to the main home SSID (or ethernet if available). Keep the same stratum fields. If the session holds only off guest, isolation / guest policy is the active story — not a broken Bitmern Solo endpoint.

3. Check whether guest / AP isolation is enabled

Symptom: Guest SSID has “AP isolation,” “client isolation,” “station isolation,” or “guest mode” toggles on.

Fix: On many consumer APs, guest mode blocks client-to-client and sometimes restricts outbound in ways that break IoT/miner TCP. For mining, prefer: (a) main SSID / trusted VLAN with outbound internet, or (b) a dedicated IoT VLAN that explicitly allows outbound DNS + TCP to public hosts (including btc.bitmernsolo.com:3132). Do not invent a Bitmern-published “approved guest SSID” list.

4. Confirm DNS works on the network the miner uses

Symptom: Host looks right but resolve fails only on guest / IoT VLAN.

Fix: From a laptop on the same SSID/VLAN as the Bitaxe, resolve btc.bitmernsolo.com. If DNS fails there, fix guest DNS / upstream resolvers first. DNS-only without isolation: DNS resolve fix. Isolation often causes the DNS failure — stay here when guest policy is the root.

5. Confirm outbound TCP to stratum is allowed

Symptom: DNS works; TCP to :3132 still fails from the guest path.

Fix: From the same network segment, verify you can open a TCP path to btc.bitmernsolo.com:3132 (router allow-list, VLAN firewall, or move off guest). This is not a claim that Bitmern Solo requires inbound ports on your home WAN — outbound from the miner is enough. Related: no inbound ports.

6. Separate isolation from flapping WiFi

Symptom: RSSI dips, roam thrash, or intermittent association without a guest toggle story.

Fix: Use WiFi drops killing stratum. Isolation is a policy wall; drops are a radio / roam wall.

7. Separate isolation from main-LAN firewall ACLs

Symptom: Main SSID has custom firewall rules blocking stratum; guest is not involved.

Fix: Use firewall blocking stratum. Return here when the durable story is guest / AP / client isolation or an IoT VLAN deny.

8. Separate isolation from VPN / proxy paths

Symptom: Guest forces a VPN profile, transparent proxy, or “secure browsing” MITM that breaks stratum.

Fix: Use VPN / proxy stratum fix. Isolation and VPN can co-exist — fix the path that actually carries the Bitaxe.

9. Prefer ethernet when the desk allows it

Symptom: You need durability and can wire the board.

Fix: Wired path guidance: ethernet vs WiFi. Ethernet does not “bypass” a VLAN firewall if the cable lands on the same isolated VLAN — still allow outbound DNS + :3132.

10. Open the matching coin tab and prove the session

Symptom: You declare failure while staring at the wrong coin tab after a network move.

Fix: Open the same coin the miner uses. Confirm the worker under WALLET.worker. Card reading: dashboard workers / shares / effort.

11. Prove the session — not a luck promise

After a clean network path + new session:

  • Firmware holds Authorized / Subscribed (or equivalent)
  • Matching coin tab shows the worker under the expected label
  • Fresh accepts can move while the board hashes
  • You are not treating Current Effort as a find clock

Current Effort is an ops signal — not a find guarantee.

12. Soft fee reminder only after the session holds

Fee reminder only if you need it: flat 1% on finds; you keep 99%. Clearing guest isolation is an ops win, not a fee event.

When WiFi drops, firewall, DNS, ethernet, or VPN is the real story

If the radio flaps without isolation, use WiFi drops killing stratum. If main-LAN ACLs block stratum, use firewall blocking stratum. If DNS alone is broken on an otherwise open LAN, use DNS resolve fix. If you are choosing wired for stability, use ethernet vs WiFi. If a VPN/proxy owns the path, use VPN / proxy stratum fix.

What this post will not invent

  • No Bitmern Solo “guest WiFi isolation timeout SLA” product guarantees
  • No claim that :3102 is the home Bitaxe default (easy-start is :3132)
  • No luck formulas, dollar EV, or find-time promises from Current Effort
  • No fabricated “official guest SSID whitelist” sold as Bitmern Solo policy
  • No competitor fee comparisons

Fee reminder: flat 1% on finds; you keep 99%. A clean outbound path + correct port is desk hygiene, not a luck product.

Quick retest sequence after a network or SSID change

After you leave guest, disable AP isolation, or allow outbound on the IoT VLAN:

  1. Confirm BTC easy-start still btc.bitmernsolo.com + :3132.
  2. Confirm username WALLET.worker, password x.
  3. Save / apply and reboot so firmware opens a new session.
  4. Open the matching coin tab — not a neighbor tab.
  5. Watch for Authorized / Subscribed and a worker row — not Current Effort as a find promise.

If the board only works on main LAN, keep it there (or fix guest policy). If DNS still fails on an open LAN, leave for DNS resolve fix.

Common guest / AP isolation mistakes to avoid

  1. Parking the Bitaxe on guest “because IoT” — guest isolation often blocks the stratum path you need.
  2. Treating :3102 as “the Bitmern port” — easy-start for Bitaxe / home BTC is :3132.
  3. Skipping .worker — username format matters for attribution after every reconnect.
  4. Using a non-x password — Bitmern Solo expects password exactly x.
  5. Reading the wrong coin tab after a SSID move — prove the worker on the matching tab.
  6. Inventing an isolation-timeout SLA — home AP policies vary; Bitmern Solo does not sell a guest-mode guarantee.
  7. Blaming Bitmern Solo before A/B testing main vs guest — prove the same string on a non-isolated path first.

None of these mistakes invent a guest SLA. They only restore a path from an isolated SSID/VLAN to a real session and proven accepts.

How this checklist fits the ops library

Start here when guest / AP / client isolation (or an IoT VLAN deny) is the active failure. Move sideways when the symptom clearly belongs to another lane.

Soft next step

Move the Bitaxe off guest isolation (or allow outbound DNS + TCP :3132 on that VLAN), lock BTC easy-start btc.bitmernsolo.com with port :3132, keep WALLET.worker with password x, open a new session, then confirm Authorized / Subscribed plus a worker row — before you chase luck myths or invent an isolation SLA.

Start mining

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

FAQ

Can I run a Bitaxe on my router’s guest WiFi for Bitmern Solo?

Often guest mode enables AP/client isolation that blocks durable stratum. Prefer main LAN / a VLAN with outbound DNS + TCP to btc.bitmernsolo.com:3132, or disable isolation if your AP allows a safe exception. Bitmern Solo does not publish a guest-SSID guarantee.

What BTC port should a home Bitaxe use?

: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 must be registered for that coin). Password exactly x.

Is guest isolation the same as a WiFi drop?

No. Drops are radio / roam failures — WiFi drops killing stratum. Use this post when policy (guest / AP / client isolation / IoT VLAN) blocks the path.

Does Current Effort mean I am about to find a block?

No. Current Effort is an ops / attribution signal — not a find guarantee. See the dashboard guide.

Where do I confirm the fix on Bitmern Solo?

Matching coin tab → worker row → firmware holds Authorized / Subscribed → fresh accepts when the board hashes. Guide: dashboard workers / shares / effort.

Related posts