Miner Is Running but Worker Is Offline

Learn why an ASIC miner may appear to be running while its worker remains Offline in the PECPool panel. This guide explains how worker status is determined and provides step-by-step checks for pool settings, worker names, network connectivity, rejected shares, miner hardware, and firmware problems.

An ASIC miner may appear to be powered on, display normal temperatures, and even show local hashrate while its worker remains Offline in the PECPool panel.

This normally means that the miner is operating locally, but PECPool is not receiving recent valid shares from the configured worker.

A powered-on miner and an Online worker are not the same thing. The worker becomes Online only after the miner connects to a PECPool stratum server, authenticates with the correct mining account, and begins submitting valid shares.

This guide explains the most common causes of an Offline worker and provides a practical troubleshooting process for Antminer, WhatsMiner, and other compatible Bitcoin SHA-256 ASIC miners.

How PECPool Determines Worker Status

PECPool determines worker status from valid mining activity received through its stratum servers.

The normal connection process is:

1. The ASIC miner powers on and initializes its hashboards.
2. The miner connects to the configured PECPool stratum server.
3. The miner authenticates using the mining account and worker name.
4. PECPool sends mining jobs to the worker.
5. The miner performs SHA-256 calculations.
6. The miner submits mining shares.
7. PECPool validates the shares.
8. The worker appears Online after valid activity is received.

If PECPool does not receive recent valid shares from the worker, the worker may remain or become Offline even when the miner itself is powered on.

Running Miner vs Online Worker

Status	Meaning
Miner Running	The ASIC device is powered on and may be performing local calculations.
Pool Connected	The miner has established a connection to a configured stratum server.
Accepted Shares Increasing	PECPool is receiving valid mining work from the worker.
Worker Online	The pool has received recent valid shares from the worker.
Worker Offline	No recent valid mining activity has been received from the worker.

Start with the Miner Status Page

Open the miner's local management interface and review its mining status before changing any settings.

Depending on the manufacturer and firmware, the page may be named:

• Miner Status
• Mining Status
• Dashboard
• Pool Status
• CGMiner Status
• Overview

Check the following information:

• Pool connection status
• Active Pool URL
• Worker name
• Accepted shares
• Rejected or stale shares
• Local hashrate
• Average hashrate
• Hashboard status
• Temperature and fan speed
• Miner uptime

The most important initial question is whether the accepted-share counter is increasing.

Check Whether Accepted Shares Are Increasing

Accepted shares confirm that the miner is successfully submitting valid work to PECPool.

If the accepted-share counter is increasing, the miner is normally connected and mining correctly. A recently connected worker may still require approximately 10 to 20 minutes to appear or fully update in the PECPool panel.

If accepted shares remain at zero, the miner is not successfully submitting valid mining work and further troubleshooting is required.

Common Causes of an Offline Worker

The most common causes include:

• Incorrect Pool URL or port
• Incorrect mining account or worker name
• Internet or DNS problems
• Blocked stratum ports
• Pool authorization failure
• Wrong mining algorithm
• Miner firmware problems
• Hashboard or power problems
• Frequent miner restarts
• Temporary routing instability

Check the PECPool Stratum Address

An incorrect Pool URL prevents the miner from connecting to PECPool.

The complete address must include:

• The stratum+tcp:// protocol
• An official PECPool hostname
• A supported port

Example:

stratum+tcp://btc-eu.pecpool.com:3333

Official PECPool Bitcoin stratum servers include:

Region	Server	Available Ports
Global	btc.pecpool.com	3333, 443, 25
United States	btc-us.pecpool.com	3333, 443, 25
Europe	btc-eu.pecpool.com	3333, 443, 25
Russia	btc-ru.pecpool.com	3333, 443, 25
Asia	btc-as.pecpool.com	8443, 443, 25
Iran	btc-ir.pecpool.com	8443, 443, 25
Iran Alternative	btc.pecpool.cc	8443, 443, 25

Do not enter the PECPool website or control panel address in the miner's Pool URL field.

Incorrect:

https://cp.pecpool.com
https://pecpool.com

Correct:

stratum+tcp://btc-eu.pecpool.com:3333

Configure All Three Pool Entries

Most ASIC miners support Pool 1, Pool 2, and Pool 3.

Configure three official PECPool addresses so the miner can switch to a backup connection when the primary route becomes unavailable.

Example:

Pool 1

URL: stratum+tcp://btc-eu.pecpool.com:3333
Worker: myaccount.miner01
Password: x

Pool 2

URL: stratum+tcp://btc.pecpool.com:443
Worker: myaccount.miner01
Password: x

Pool 3

URL: stratum+tcp://btc-us.pecpool.com:25
Worker: myaccount.miner01
Password: x

The same mining account and worker name should normally be entered in all three pool entries of the same physical miner.

Check the Mining Account and Worker Name

The recommended worker format is:

AccountName.WorkerName

Example:

myaccount.miner01

In this example:

• myaccount is the PECPool mining account.
• miner01 identifies the physical ASIC miner.

Copy the mining account name directly from the Accounts section of the PECPool panel.

Do not use:

• Your email address
• Your Bitcoin wallet address
• Your PECPool login username when it differs from the mining account
• The miner's serial number unless it is intentionally used as the worker suffix

Common Worker Name Mistakes

Missing Account Name

Incorrect:

miner01

Correct:

myaccount.miner01

Missing Separator

Incorrect:

myaccountminer01

Correct:

myaccount.miner01

Spaces in the Worker Name

Incorrect:

myaccount. miner01
myaccount .miner01
myaccount.miner 01

Correct:

myaccount.miner01

Wallet Address Used as Worker

Incorrect:

bc1qexamplebitcoinaddress

Correct:

myaccount.miner01

Check the Pool Password

The Pool Password field is not your PECPool login password.

When no special stratum password is required, enter:

x

Never enter any of the following in the Pool Password field:

• Your PECPool login password
• Your email password
• Your Two-Factor Authentication code
• Your API Secret
• Your Bitcoin wallet private key
• Your wallet seed phrase

Check the Pool Status

The active PECPool connection may appear as:

• Alive
• Active
• Connected
• Working

If the pool displays Dead, Disconnected, or another error, the miner cannot establish or maintain the stratum connection.

Check:

• The complete Pool URL
• The port number
• The miner's internet connection
• DNS resolution
• Router and firewall restrictions
• The selected PECPool region

Authorization Failed

An authorization error means that the miner reached the stratum server but the submitted account or worker information was not accepted correctly.

Possible causes include:

• Incorrect mining account name
• Incorrect worker format
• Spaces or unsupported characters
• Wallet address entered as the worker
• Incomplete account name
• Wrong account selected in PECPool

Correct the Worker field and save the configuration again.

Check the Miner Algorithm

PECPool Bitcoin mining requires a SHA-256 ASIC miner.

A miner designed for another cryptocurrency algorithm cannot mine Bitcoin by simply changing the Pool URL.

Compatible miner families include many Bitcoin models from:

• Bitmain Antminer
• MicroBT WhatsMiner
• Other SHA-256 ASIC manufacturers

Verify the exact model and supported mining algorithm before troubleshooting the stratum connection.

Check the Internet Connection

The miner requires continuous network access to receive mining jobs and submit shares.

Check:

• The Ethernet cable is connected securely.
• The network switch port is active.
• The router has internet access.
• The miner has a valid IP address.
• The gateway and subnet mask are correct.
• The DNS server is reachable.

A miner may continue displaying local hashrate briefly even after losing internet access because the hashboards are still operating. However, no useful work reaches PECPool during the disconnection.

Test DNS Resolution

DNS converts the PECPool hostname into the IP address used for the connection.

From a Windows computer on the same network, use:

nslookup btc-eu.pecpool.com

Or in PowerShell:

Resolve-DnsName btc-eu.pecpool.com

From Linux:

getent hosts btc-eu.pecpool.com

If no IP address is returned, review the router's DNS configuration or test another trusted DNS resolver.

Test the Stratum Port

A hostname may resolve correctly while the required port remains blocked.

From Windows PowerShell:

Test-NetConnection btc-eu.pecpool.com -Port 3333

Look for:

TcpTestSucceeded : True

From Linux:

nc -vz btc-eu.pecpool.com 3333

If port 3333 is unavailable, test another supported PECPool port such as 443 or 25 for that region.

Do Not Rely Only on Ping

Ping can provide basic information about latency or packet loss, but it is not a complete stratum test.

Example:

ping btc-eu.pecpool.com

A server may ignore Ping while still accepting mining connections. A successful TCP port test and increasing accepted shares are more important.

Check Firewall and Router Rules

Network-security rules may block outgoing stratum connections.

Check:

• Router firewall rules
• Corporate or hosting-provider network restrictions
• ISP port filtering
• VLAN access rules
• Gateway routing
• DNS filtering

ASIC miners normally initiate outbound connections to the PECPool stratum server. The network must permit the selected hostname and port.

Try Another PECPool Server or Port

A regional server may be reachable through one internet provider but unstable through another because of routing differences.

If the primary server does not connect:

1. Try another supported port on the same hostname.
2. Try the PECPool Global server.
3. Try another nearby regional server.
4. Save the configuration.
5. Check whether accepted shares begin increasing.

Do not change servers repeatedly every few minutes. Allow enough time to evaluate each connection.

Check the Miner Log

The miner's system or kernel log often shows the exact reason for a connection failure.

Look for messages containing:

• Pool Dead
• Socket Connect Failed
• Connection Refused
• Network Unreachable
• DNS Error
• Authorization Failed
• Invalid User
• No Shares
• Connection Reset
• Stratum Connection Interrupted

Use the log message to identify whether the problem is related to DNS, network access, authorization, firmware, or miner hardware.

Check Hashboard Status

A miner may connect to the pool but fail to submit useful shares when its hashboards are not operating correctly.

Check:

• All expected hashboards are detected.
• ASIC chips are detected normally.
• Local hashrate is above zero.
• Hardware errors are not unusually high.
• Temperature is within the normal range.
• Fans or the required cooling system are operating.

Missing hashboards, power faults, or overheating are miner-level problems rather than PECPool account problems.

Local Hashrate Is Visible but Accepted Shares Are Zero

Local hashrate only confirms that the miner reports internal calculation activity.

Accepted shares remaining at zero may indicate:

• The miner is working on an incorrect or inactive pool.
• The miner is not authorized.
• The network connection is blocked.
• The firmware is not submitting valid work.
• The hashboards are unstable.

Do not consider the miner successfully connected until accepted shares begin increasing.

Rejected Shares Are Increasing but Accepted Shares Are Not

This means the miner is submitting results, but the results are not being accepted as valid mining contribution.

Possible causes include:

• Incorrect worker configuration
• Authorization failure
• Low-difficulty shares
• Duplicate shares
• Unstable custom firmware
• Excessive overclocking
• High network latency

Review the exact rejection reason in the miner log and return unstable performance settings to a safe level.

Check Miner Date and Time

Incorrect date and time may cause problems in some miner firmware versions, log records, or secure network functions.

Configure the miner to receive time automatically when supported and verify the correct gateway and DNS settings.

Restart the Mining Process

After correcting the pool configuration:

1. Save or apply the settings.
2. Wait for the mining process to restart.
3. Check the active pool status.
4. Confirm that accepted shares begin increasing.
5. Wait for the PECPool worker status to update.

Avoid repeatedly disconnecting power while the miner is saving settings or initializing its hashboards.

When Should You Restart the Router?

Restart the router or network equipment when:

• Multiple miners lose connection simultaneously.
• DNS resolution fails across the mining network.
• The gateway stops responding.
• The internet connection is unstable.
• Network equipment has been running incorrectly after a configuration change.

If only one miner is affected while other miners on the same network remain Online, focus on that miner's configuration, cable, switch port, firmware, or hardware.

One Worker Is Offline but Other Workers Are Online

When only one worker is affected, check:

• That miner's Ethernet cable
• Its switch port
• Its Pool URL
• Its worker name
• Its accepted shares
• Its hashboards and temperature
• Its miner logs

Because other workers are connected, the general PECPool server and farm internet connection are less likely to be the main cause.

All Workers Are Offline

When every worker under a mining site becomes Offline at approximately the same time, check:

• The farm internet connection
• The main router or gateway
• DNS services
• Firewall changes
• ISP routing
• The shared network switch
• The configured PECPool stratum server

Also test a different official PECPool regional server and port.

Worker Is Online but Hashrate Is Zero

Worker status and hashrate are related but not identical.

A worker may briefly remain Online based on recent share history while current hashrate has already fallen to zero.

Check:

• Last-share time
• Accepted-share activity
• Current hashrate
• 1-hour hashrate
• Miner status
• Hashboard operation

If no new shares arrive, the worker will eventually update to Offline.

Worker Recently Reconnected but Still Shows Offline

After resolving the problem, the worker may require time to submit valid shares and update in the PECPool panel.

Confirm that:

• The active pool shows Alive or Connected.
• Accepted shares are increasing.
• The correct worker name is displayed.
• The miner has stable local hashrate.

Allow approximately 10 to 20 minutes for a newly connected or restarted worker to appear or fully update.

Old Worker Remains Offline After Renaming

When you change the worker name in the miner, PECPool begins receiving shares under a new worker identity.

For example:

Old Worker: myaccount.miner01
New Worker: myaccount.rack01m01

The old worker may remain visible as Offline because it contains historical data. The new worker should appear after valid shares are received.

Example 1: Incorrect Worker Name

The miner configuration contains:

Pool URL: stratum+tcp://btc-eu.pecpool.com:3333
Worker: miner01
Password: x

The PECPool mining account is myaccount.

The correct Worker field is:

myaccount.miner01

After correcting the worker and saving the settings, accepted shares should begin increasing if the remaining configuration is valid.

Example 2: Blocked Port

The miner uses:

stratum+tcp://btc-eu.pecpool.com:3333

The hostname resolves correctly, but the network blocks port 3333.

Test an alternative official port:

stratum+tcp://btc-eu.pecpool.com:443

If the miner connects and accepted shares begin increasing, the original problem was related to port accessibility.

Example 3: Miner Lost Internet Access

The miner displays:

• Power: On
• Fans: Running
• Local hashrate: Visible
• Pool status: Dead
• Accepted shares: Not increasing

This indicates that the miner is operating locally but cannot communicate with PECPool. Check the Ethernet connection, IP configuration, gateway, DNS, and router.

Example 4: Hardware Problem

The miner displays:

• Pool status: Connected
• Accepted shares: Zero
• Local hashrate: Zero
• One or more hashboards missing

The network connection is available, but the miner is not producing mining work. Inspect the power supply, hashboards, signal cables, temperature, and miner logs.

Recommended Troubleshooting Order

1. Confirm that the miner is powered on.
2. Check that the miner has a valid IP address.
3. Open the miner's status page.
4. Check the active Pool URL.
5. Check the mining account and worker name.
6. Confirm that the Pool Password is x.
7. Check the pool connection status.
8. Check whether accepted shares are increasing.
9. Review the miner log.
10. Test DNS and the stratum port.
11. Try another official PECPool server or port.
12. Check hashboards, temperature, and hardware errors.
13. Save the corrected settings and wait for status updates.

Quick Checklist

• The miner is powered on and stable.
• The Ethernet cable is connected.
• The miner has a valid IP, gateway, and DNS configuration.
• The Pool URL uses an official PECPool stratum address.
• The port is supported and reachable.
• The worker uses AccountName.WorkerName format.
• The Pool Password is x.
• The miner uses the SHA-256 algorithm.
• The active pool shows Alive or Connected.
• Accepted shares are increasing.
• All expected hashboards are detected.
• Temperature and cooling are normal.
• The miner log contains no repeated connection errors.
• Enough time has passed for the PECPool status to update.

When to Contact PECPool Support

Contact PECPool Support when:

• The miner connects to an official PECPool server but authorization repeatedly fails.
• Accepted shares are visible but the worker does not update after sufficient time.
• Multiple independent networks cannot reach the PECPool server.
• The panel and miner display inconsistent worker information.
• The problem continues after completing all connection checks.

Provide:

• The PECPool mining account name
• The complete worker name
• The miner model
• The configured Pool URL and port
• A screenshot of the miner status page
• The relevant miner log messages
• The approximate time the issue started

Do not send:

• Your PECPool login password
• Your email password
• Your Two-Factor Authentication code
• Your API Secret
• Your Bitcoin private key
• Your wallet seed phrase

Official PECPool Support Channels

Use only official PECPool support channels:

• The Support section in the PECPool panel
• The official PECPool community channels
• support@pecmine.com

Final Checklist

• A running miner does not automatically mean the worker is Online.
• PECPool needs to receive recent valid shares from the worker.
• The accepted-share counter should be increasing.
• The Pool URL and port must be correct.
• The worker must use the correct mining account.
• The Pool Password must not be the PECPool login password.
• The network must allow outbound stratum connections.
• DNS, gateway, and routing must operate correctly.
• Hashboards must produce valid mining work.
• The miner log should be reviewed for the exact error.
• The worker may require 10 to 20 minutes to update after reconnection.

Focus on Valid Shares

When a miner is running but its worker remains Offline, the most important question is not whether the fans are spinning or whether local hashrate is displayed.

The important question is whether PECPool is receiving recent accepted shares from the correct worker.

Start by checking the active Pool URL, worker format, accepted shares, network connectivity, and miner logs. These checks identify most Offline-worker problems quickly and prevent unnecessary changes to unrelated account settings.