⛏️ Mining Configuration
BTC SOLO Mining Ports
Bitcoin solo mining — the full block reward goes to whoever finds itTLS / SSL
stratum+ssl://btc.onpool.net:3334
TCP
stratum+tcp://btc.onpool.net:3333
BTC PPLNS Mining Ports
Bitcoin PPLNS — rewards shared in proportion to submitted workTLS / SSL
stratum+ssl://btc.onpool.net:3345
TCP
stratum+tcp://btc.onpool.net:3344
BCH SOLO Mining Ports
Bitcoin Cash solo miningTLS / SSL
stratum+ssl://bch.onpool.net:4445
TCP
stratum+tcp://bch.onpool.net:4444
BCH PPLNS Mining Ports
Bitcoin Cash PPLNS — proportional rewardsTLS / SSL
stratum+ssl://bch.onpool.net:4456
TCP
stratum+tcp://bch.onpool.net:4455
LTC+DOGE SOLO Mining Ports
Litecoin + Dogecoin merged mining, soloTLS / SSL
stratum+ssl://ltc.onpool.net:5556
TCP
stratum+tcp://ltc.onpool.net:5555
LTC+DOGE PPLNS Mining Ports
Litecoin + Dogecoin merged mining, PPLNSTLS / SSL
stratum+ssl://ltc.onpool.net:5567
TCP
stratum+tcp://ltc.onpool.net:5566
XMR SOLO Mining Ports
Monero solo miningTLS / SSL
stratum+ssl://xmr.onpool.net:5594
TCP
stratum+tcp://xmr.onpool.net:5593
XMR PPLNS Mining Ports
Monero PPLNS — proportional rewardsTLS / SSL
stratum+ssl://xmr.onpool.net:5596
TCP
stratum+tcp://xmr.onpool.net:5595
Need help setting up your Bitaxe or Nerdminer?
Read Setup Tutorials on our Blog🛠️ Common Errors & Troubleshooting
1. "Unauthorized Worker" / IP Ban
Your miner is getting 10s temporary bans in our logs.
Cause: Using a prefix like BTC: or bitcoin:.
Fix: Use ONLY your clean wallet address as username.
BTC:bc1qxs2j...
bc1qxs2j...
2. Difficulty Too High / No Shares
Miner connected but 0 Shares on dashboard.
Cause: one of two things
- A fixed difficulty in the password field (something like
d=8192). That switches automatic difficulty off entirely and leaves your device stuck at a value that does not match its hashrate. - The device only just connected and the difficulty has not settled yet. This is normal — it takes a few minutes for the pool to measure your hashrate and land on the right value.
Fix: put just x in the password field and nothing else. The pool sets the difficulty itself and adapts to your hardware within minutes. Which port you choose no longer has anything to do with difficulty.
3. SSL/TLS Handshake Failed
Fix: If using stratum+ssl://, make sure to use our dedicated TLS ports (BTC SOLO: 3334; BTC PPLNS: 3345; BCH SOLO: 4445; BCH PPLNS: 4456; LTC+DOGE: 5556 / 5567; XMR: 5594 / 5596). Our German node supports full TLS 1.2/1.3 for maximum security.
root@server1 ~ # echo | openssl s_client -servername public-pool.io -connect public-pool.io:4333 2>/dev/null | openssl x509 -noout -dates
notBefore=Feb 19 01:37:55 2026 GMT
notAfter=May 20 01:37:54 2026 GMT
root@server1 ~ # echo | openssl s_client -servername btc.onpool.net -connect btc.onpool.net:3334 2>/dev/null | openssl x509 -noout -dates
notBefore=Feb 10 00:00:00 2026 GMT
notAfter=Mar 13 23:59:59 2027 GMT
4. Duplicate Shares (normal on Bitaxe / NerdQaxe)
Your miner shows 2–4% "duplicate shares"? No worries — this is a well-known behavior of the Bitaxe / NerdQaxe firmware (ESP-Miner), not a pool issue.
Cause: On job transitions the firmware occasionally resubmits the same share. This happens on EVERY pool (public-pool, ckpool, Ocean …).
Fix: Nothing to do. Your rewards and block chance are NOT affected — the pool correctly detects and ignores duplicates. Your miner works perfectly. ✅