Why is my Lucky Miner not hashing or submitting shares?

By DirectPool. Published . Updated
Short answer

Check the Lucky Miner’s 2.4 GHz WiFi, pool host, port and BTC-address username first, then compare accepted shares with the local hashrate. Persistent rejects or falling output need the actual error log, stock tuning and a power and cooling check.

Is it connected to WiFi and the right pool?

Open the local IP on the miner's screen. Confirm it has joined your 2.4 GHz WiFi rather than remaining in setup mode. Keep it within a reliable signal range and check router isolation rules if the local interface cannot be reached.

For shared BTC, use host stratum.directpool.io, port 3333, your own BTC address plus an optional worker suffix, and password x. A BCH address on a BTC connection is not interchangeable. Compare the complete Lucky Miner pool settings before changing firmware.

Why is hashrate visible but no share accepted?

The local hashrate estimates chip activity; accepted shares prove that the pool received valid work. Shares arrive randomly, so a short gap alone is not evidence of a fault. Watch the last-share timestamp, accepted count and connection log together.

Look up the address without its .workername suffix on your miner dashboard. Confirm you are viewing the same pool mode as the configured port. Dashboard averages need real observations, not just a powered-on device.

What causes rejected shares?

  • Stale work after a network interruption or a new block.
  • A wrong username, wrong port or a failed authorization.
  • A difficulty mismatch with manually configured mining software.
  • Unstable frequency, voltage or hardware producing invalid work.

Read the actual rejection message before adjusting anything. Password d=number is an optional specialist setting, not a general cure for a Lucky Miner. Start with x. Do not repeatedly reconnect a rejected rental without finding its error.

What if it is hot or slower than advertised?

Return to the vendor's stock settings, clear the fan intake, leave ventilation space and check that the fan spins. Use the correct supplied adapter and a sound cable. A powered screen does not prove the supply can sustain the hash board under load.

Compare a settled average, not a single second of output, with the model's nominal rating. Do not use an unverified universal temperature limit or raise voltage to hide falling hashrate. Stop and disconnect a device that smells burnt, has damaged wiring or has a stalled fan.

What should I record before asking for help?

  1. Write down the exact LV model, firmware version and pool port.
  2. Record uptime, accepted and rejected counts, chip temperature and the exact error text.
  3. Try stock tuning and a reliable WiFi signal, then change only one setting at a time.
  4. Share a redacted settings screenshot. Never share wallet seeds, WiFi credentials or private keys.

Continue with the general connection checklist, Lucky Miner setup guide, live odds calculator, guide index or current pool connection details.

Q

Questions

Should I factory reset immediately?
No. Record your settings and error messages first. Verify WiFi, host, port and username before a reset that could remove useful configuration.
Can low WiFi signal cause rejects?
An unstable connection can delay or interrupt work and increase stale shares. Check the connection log and signal before attributing every reject to the hash board.
Why does DirectPool show a different hashrate?
The pool estimates hashrate from accepted work over a time window. The device reports its own estimate. Short windows and newly connected miners can differ substantially.
S

Sources

  1. DigLucky: Lucky Miner setup referencehttps://diglucky.com/luckyminer-lv08-setup-guide, checked 2026-11-11
  2. DirectPool: connection troubleshootinghttps://directpool.io/guides/miner-wont-connect/, checked 2026-11-11

Miners in this guide

Read next