To connect to a mining pool, an ASIC miner needs three accurate configuration values: a pool address, a worker identity, and any pool-specific password setting. You then save those values in the miner’s local web interface and verify that the machine is submitting shares and appearing in the pool dashboard. The sequence is simple, but using the wrong coin algorithm, URL, port, or worker format can prevent the miner from starting.

A mining pool combines the hashrate of participating miners and distributes rewards according to its stated payout method. It is not a wallet, and it is not the company that manufactured your ASIC. This guide explains the connection process without assuming a specific model or firmware.

What You Need Before You Connect an ASIC Miner to a Mining Pool

Start with the hardware and network basics. Your ASIC must support the algorithm used by the coin you plan to mine. For example, a miner designed for one algorithm cannot be repointed to an unrelated coin simply by changing its pool settings.

Before beginning your ASIC miner pool setup, have the following ready:

• A properly installed ASIC with stable, appropriate power.
• A wired Ethernet connection to your router or switch.
• A computer on the same local network.
• The miner’s reachable local IP address.
• A pool account or the pool’s required worker format.
• The current official setup page for the exact coin and algorithm.

Do not copy a pool address from a search snippet, chat group, or old screenshot. Pool URLs and ports can change, and a valid address for one coin may be wrong for another.

Step 1: Confirm Your ASIC, Coin Algorithm, and Pool Account Details

First, identify the ASIC model and its supported algorithm. Check the manufacturer documentation or the miner’s status page. Then confirm that the target pool currently supports both that coin and algorithm.

BTC pool settings apply only to SHA-256 miners. Do not copy BTC URLs, ports, or worker settings to miners designed for other algorithms, even if the interface looks similar.

Next, prepare the login or account identifier required by the pool. A worker name usually identifies an individual machine or location under your pool account. It helps you distinguish devices in the dashboard, such as a home unit, a rack position, or a site.

Choose a simple, consistent ASIC worker name convention before adding multiple machines. For example, a suffix could describe the model or location. Follow the exact format specified by the pool; adding spaces, unsupported characters, or a wallet address where an account worker is expected can cause authentication failures.

Step 2: Find Your Miner’s IP Address and Sign In to Its Web Interface

Your miner must be visible on the local network before you can enter pool settings. You can often find its IP address in your router’s connected-device list. Some manufacturers also provide an IP discovery utility or an IP-report button on the device.

Enter the local IP address in a browser on the same network, then sign in to the miner’s web interface. If the page does not load, check the Ethernet cable, router port, DHCP assignment, and whether your computer is on the same network segment.

An Antminer miner configuration interface is one familiar example, but menu names and login procedures vary by model and firmware. Change default administrative credentials where appropriate, and do not expose the miner’s management page directly to the public internet.

Step 3: Open the Mining Pool or Miner Configuration Page

After signing in, locate the page used to configure pools. It may be labeled Miner Configuration, Pool Settings, Mining Configuration, Server Settings, or something similar.

Most ASIC miner pool setup pages contain one or more pool rows. Each row typically has these fields:

• Pool URL or Pool: the Stratum server address.
• Worker or User: your pool account and worker identity.
• Password: a pool-specific field that may be optional.

The interface may also show priority, enable/disable controls, or several pool slots. Read the labels carefully and use the pool’s current instructions.

Step 4: Enter the Official Stratum URL, Worker Name, and Password

A mining pool URL is the server address that tells the miner where to connect. A Stratum URL normally includes a protocol, hostname, and port. Copy the full value exactly from the official pool page for the coin you are mining. A missing character, an outdated hostname, or a mismatched port can stop the connection.

For the Worker or User field, enter the exact pool-required format. On ViaBTC’s current BTC guide, the worker format is userID.workerID. The guide also says that the worker ID uses numbers and lowercase letters, and that the password is optional. These rules apply to that BTC setup, so check the requirements if you select a different coin, pool, or firmware.

For Password, do not rely on a generic value from another tutorial. Some pools ignore this field, some accept any value, and others use it for a setting or credential. Follow the selected pool’s instructions.

A careful Stratum configuration has three checks:

1. The URL belongs to the pool setup page for the selected coin.
2. The port matches that exact URL and connection type.
3. The Worker/User field follows the pool’s required syntax exactly.

Step 5: Add Backup Pool Entries for Failover

If your miner supports multiple pool rows, add approved backup entries after configuring the primary one. Mining pool failover lets the device move to a lower-priority entry if it cannot reach the primary endpoint.

A backup should be a legitimate alternative for the same intended mining configuration, not an unrelated coin or algorithm. Check how your firmware orders pool rows, because some devices treat the first row as highest priority while others expose a separate priority setting.

Failover reduces the chance that a single unreachable endpoint leaves the miner idle. It does not fix local power loss, a disconnected Ethernet cable, hardware faults, or an incorrect worker format.

Step 6: Save Settings and Check That the Miner Connects

Save or apply the new settings. The device may briefly restart its mining process while it reconnects. Keep the browser open and check the status page for a pool connection state, accepted shares, real-time hashrate, fan operation, and temperatures.

Do not expect the displayed hashrate to match a nameplate rating immediately or exactly. Startup time, temperature, firmware behavior, network latency, and the averaging window all affect what you see.

If the status page shows repeated connection attempts, compare the entered URL and worker string character by character with the pool instructions. Then check the network and device logs.

Step 7: Verify the Worker and Hashrate in Your Pool Dashboard

A successful miner-side connection is only the first confirmation. Sign in to the pool dashboard and look for the worker you configured. Depending on the pool, the dashboard may take time to recognize a new worker and calculate a stable hashrate.

Compare the worker status with the miner’s local status page. The values can differ because they are measured at different points and over different time windows. A miner can report local hashrate while the pool dashboard is still waiting for enough submitted shares to show a reliable reading.

For ViaBTC BTC mining, the current guide indicates that operation and earnings can be checked after the miner stabilizes. Treat the dashboard as the pool-side confirmation that the ASIC worker name is recognized and submitting work.

Common Problems When an ASIC Miner Will Not Connect to a Mining Pool

URL or worker mistakes

An invalid mining pool URL, port typo, or incorrect Stratum configuration is a common cause of connection failures. Recopy the exact value from the coin-specific setup page. Then confirm that the worker format matches the pool’s rules and that you did not enter an account password in the Worker field by mistake.

Common status messages

Status wording varies by manufacturer and firmware, but messages such as “connection refused,” “pool timeout,” or “cannot connect” usually point to a URL, port, DNS, or network-path problem. “Authorization failed” or “unauthorized” usually indicates a worker, account, or password-handling issue. Check the exact log message before changing multiple settings.

Local network or DNS problems

If the miner cannot reach any configured endpoint, inspect the Ethernet connection, router, gateway, DNS settings, and firewall policies. Test with more than one approved failover entry where supported. A pool-side address cannot work if the miner has no usable network path.

Authentication, temperature, firmware, or hardware issues

Authentication errors usually point to a worker, account, or password-handling problem. High temperatures, stopped fans, hashboard errors, outdated firmware, or power issues can also prevent normal mining even after the pool connection succeeds. Review the device status page and logs before changing firmware or resetting the miner.

If you are unsure whether a problem is pool-related, separate the checks: confirm the endpoint and credentials first, then the local network, then the miner’s health indicators.

ViaBTC Setup Example: What to Verify Before Entering BTC Pool Details

For a BTC example, use the current official ViaBTC BTC mining guide immediately before entering settings. The guide describes entering pool details through the Antminer Miner Configuration page, using a userID.workerID worker format, and configuring multiple entries for continuity.

Before saving, verify all of the following:

• Your ASIC is a SHA-256 miner that supports BTC mining.
• The selected ViaBTC BTC URL and port are current.
• Your Worker/User value follows the current worker rule.
• Your password entry follows the current pool guidance.
• Backup entries are approved and correctly prioritized.
• The miner status and pool dashboard both show normal progress after stabilization.

That final verification is what turns a saved configuration into a confirmed connection. When you connect to a mining pool with current settings and monitor both sides of the connection, you can identify errors early without making assumptions about rewards or performance.