To connect an ASIC miner to ViaBTC Pool, enter a current ViaBTC BTC mining URL, a correctly formatted worker name, and the password value required by your miner firmware or the pool. Then save the settings and confirm that the miner is submitting accepted shares. This is a configuration task first: do not confuse the pool address with a wallet address, and do not assume a saved setting means the miner is already mining.
The exact menu labels and restart behavior vary by ASIC manufacturer and firmware. However, the logic is usually the same. You locate the miner on your local network, open its pool settings, add the ViaBTC connection details, and verify the connection in both the miner interface and your ViaBTC dashboard.
What You Need Before Connecting Your ASIC Miner
Prepare these items before you connect an ASIC miner to ViaBTC:
- A powered ASIC miner connected to your router by Ethernet.
- Access to the same local network as the miner.
- Your ViaBTC account details and a planned worker ID.
- The current official BTC pool URL and port.
- The miner’s local IP address.
- Browser access to the miner’s management interface.
Your miner must have stable network access before pool configuration can work. A miner may obtain an IP address automatically from the router, but you still need to identify that address to open its local control panel.
Keep the official ViaBTC BTC Mining guide open while configuring the device. Verify pool endpoints and connection options immediately before use.
Understand the Three ViaBTC Pool Settings: URL, Worker Name, and Password
Most ASIC miner pool pages ask for three values: a URL, a worker name, and a password. Together, these form the basic ViaBTC pool setup.
Why the pool URL is not a wallet address
The pool URL is a mining-server endpoint, usually a Stratum address with a port number. It tells the miner where to send work requests and submitted shares. It is not a Bitcoin wallet address and should not be replaced with one.
The worker name identifies which ViaBTC account should receive credit for submitted shares. The password field is separate and may be required by the miner firmware or pool configuration. Follow the current official instructions and your miner manufacturer’s documentation for that field.
A generic worker example is account.worker01. It illustrates the structure only; it is not a final configuration value for any reader.
Step 1: Prepare Your ViaBTC BTC Mining Account and Worker Name
Sign in to ViaBTC and make sure you are working in the BTC mining context before configuring the hardware. Plan a worker name that makes the device easy to recognize later, especially if you operate more than one miner.
ViaBTC’s BTC guidance uses the format userID.workerID. The worker ID portion should use lowercase letters and numbers and must be no more than 64 characters. A concise label can help distinguish a rack, location, or unit number without exposing unnecessary personal information.
Before saving anything on the miner, double-check the account portion of the ViaBTC worker name. A small typing error can send shares to the wrong account identifier or leave the device unable to authenticate as expected.
Step 2: Find Your ASIC Miner’s Local IP Address
You need the miner’s local IP address to access its management page. Common ways to find it include:
- Checking the router’s connected-device list.
- Using the manufacturer’s IP reporting or discovery utility.
- Reviewing the miner display or local network documentation, if available.
Enter the local IP address in a browser on the same network. If the page does not load, confirm that the computer and miner are connected to the same LAN or VLAN and that the miner has completed its startup sequence.
Step 3: Open the Miner Configuration Page
After opening the miner’s local interface, sign in with the credentials set for that device. The relevant page is typically called Miner Configuration, Pool Settings, Mining Settings, or a similar label.
Do not change clock settings, performance profiles, or other advanced controls simply to complete ASIC miner pool configuration. Start with the connection fields. This limits the number of variables if you need to troubleshoot the initial setup.
If the interface presents multiple pool rows, leave them available for primary and backup endpoints. Backup configuration should follow the current official ViaBTC connection guidance.
Step 4: Enter the Current ViaBTC BTC Pool URL and Worker Details
In the primary pool row, enter the current official ViaBTC BTC mining URL, your full worker name, and the applicable password value.
Configuration values to verify before use
The official BTC Mining guide lists these endpoints:
stratum+tcp://btc.viabtc.io:3333stratum+tcp://btc.viabtc.io:443
Verify each URL and port against the official guide before copying it into a miner. Do not remove the stratum+tcp:// prefix, alter the hostname, or substitute a wallet address.
Enter the worker in the userID.workerID format. The worker name associates submitted shares with the relevant ViaBTC account. Use a meaningful device label, but keep the worker ID within the stated character and lowercase-letter-and-number rules.
The password field is not universal across ASIC devices. Some firmware accepts a simple required value, while others document a specific convention. Use the current ViaBTC instructions and the device documentation rather than guessing.
Step 5: Add Backup Connections and Save the Configuration
Configure additional ViaBTC ports or pool entries when the official guidance supports them. Backup entries give the miner an alternative way to reconnect if the active endpoint fails. They are not the same as selecting an unrelated third-party pool as a backup.
Use the same account and worker naming logic across the entries unless your operational plan requires a different worker label. Keeping names consistent makes it easier to identify one physical miner during diagnosis.
Save or apply the configuration. The miner may restart its mining process, and some devices may reboot. Wait for the interface to report that mining services have started before deciding that the settings failed.
Step 6: Confirm the ASIC Miner Is Connected to ViaBTC
A saved configuration is only the first checkpoint. Confirm the ASIC miner is connected to ViaBTC in two places:
- On the miner dashboard, look for a live pool connection, a non-zero local hashrate, and accepted-share activity.
- In the ViaBTC worker or pool dashboard, look for the worker becoming active and reporting hashrate.
The two displays do not always update at the same moment. Allow time for the miner to begin submitting work and for dashboard data to refresh, then check the current official guidance if activation appears delayed.
A non-zero local hashrate alone is not enough. Check whether shares are accepted. A miner can be powered on and hashing locally while still failing to reach the pool, using the wrong endpoint, or submitting under an incorrect worker format.
Common ViaBTC ASIC Connection Problems and Fixes
Bitcoin mining pool troubleshooting is most effective when you begin with the simple connection details rather than changing advanced miner settings.
Wrong URL, port, or worker format
Copy the URL exactly from the current official BTC Mining guide. Check the protocol prefix, hostname, and port digit by digit. A wrong port can prevent a connection even when the rest of the address looks correct.
Then review the full worker value. Confirm that it follows userID.workerID, that the account identifier is correct, and that the worker ID uses only permitted lowercase letters and numbers within the character limit.
Network, power, and temperature checks
If the miner is offline, inspect the Ethernet cable, router port, and local network status. Verify that the miner can reach the internet and that your network does not block the outbound port used by the selected endpoint.
If the miner connects briefly and then drops, investigate operational stability:
- Check for unstable power or repeated device restarts.
- Review temperature and fan readings for overheating.
- Look for hardware or pool connection errors in the miner log.
- Confirm that the miner is not receiving a different IP address after a router restart.
Do not treat a low or missing dashboard hashrate as proof of a pool issue until you have checked the miner’s local status and logs. Connection, thermal, power, and hardware faults can produce similar symptoms.
Safety and Account-Security Checks Before Leaving the Miner Running
Change default miner login credentials if they are still active, and restrict access to the management interface to trusted local users. Do not expose the miner’s control panel directly to the public internet.
Record the miner IP address, worker label, selected URL, and configuration date in your own operational notes. This makes later maintenance more reliable without publishing sensitive account details.
Before leaving the device unattended, confirm a stable connection, accepted shares, sensible temperatures, and normal fan behavior. Recheck the current pool URL and port whenever you replace firmware, move the miner, or revisit an older configuration.
FAQ: Why Is My ViaBTC Worker Offline or Showing No Hashrate?
What is the ViaBTC worker name format?
Use userID.workerID. The worker ID should use lowercase letters and numbers and be no more than 64 characters. The worker label helps attribute submitted shares to the correct ViaBTC account and identify the physical miner in the dashboard.
Why is my ViaBTC miner offline?
Start by checking that the URL and port exactly match the current official instructions. Next, confirm the worker format, Ethernet connection, internet access, and whether your network blocks the selected outbound port. Also check the miner dashboard for power, temperature, fan, or hardware errors.
Why is there no hashrate after I save the settings?
Allow time for the miner to restart and for dashboard data to update. If hashrate remains at zero, check for a live pool connection and accepted shares locally, then verify the URL, worker name, network path, and miner logs.
Connecting an ASIC miner to ViaBTC is straightforward when the endpoint, worker format, and local network are correct. Confirm successful mining through accepted shares rather than configuration alone.