How to Change an ASIC Miner Password: Login, Recovery, and Verification
Change the correct miner credential, verify a fresh login, update monitoring, and separate lost-password recovery from suspected compromise.

To change an ASIC miner password, sign in to the correct miner, open the administrator-password settings for its installed firmware, save a new unique password, and verify it in a fresh login. Keep the credential in a secure password manager and update any authorized tools that depend on it. If you have lost the current password, identify the model's recovery procedure before resetting anything; changing a pool worker password will not restore administrator access.
Which password are you changing?
Several screens can contain a field called Password. Identify the service that checks it before typing a new secret.
| Credential | What it controls | Where the change belongs |
|---|---|---|
| Miner administrator login | Access to the miner's local settings | The installed firmware's administration or system settings |
| Pool worker password | A field in the mining connection configuration | The pool's documented worker configuration, if used |
| Pool account password | Access to the pool website and account controls | The pool account's own security settings |
| Remote-access or management account | Permission to reach or manage devices through another service | That service's account and access controls |
For example, Braiins Pool's connection instructions say its worker password is unused, while the user and worker name associate the device with the pool account. That is a rule for that pool. It does not make the miner's administrator password optional, and it should not be assumed for another pool.
Never paste your miner administrator password, pool website password, or wallet recovery phrase into a worker field simply because it has the same label. Decide which credential you are rotating and leave the others alone unless they also need a deliberate change.
Match the password screen to the actual miner
Confirm the physical asset label or serial number, current network address, manufacturer, and firmware identity. A saved browser tab can point to an address that now belongs to another device. Check the interface's identity against your inventory before making a change.
BITMAIN's ANTMINER 19-series interface guide places the password control under System and pool configuration under Server Settings. Other firmware generations may use a Password tab, Administration page, or a different workflow. Use the matching official manual rather than treating one screenshot as a universal menu map.
Record who owns the credential and which monitoring or fleet tools use it. Store the secret itself in an access-controlled password manager; a maintenance spreadsheet should contain the vault entry reference, not the password. Choose a unique generated password that fits the device's documented length and character rules. Do not shorten it to a familiar shared default merely to make fleet administration easier.
If you are working remotely, arrange a local recovery contact before starting. A successful connection to the remote network does not prove that you will retain access to the miner after the credential changes. The remote-access verification guide explains how to check permitted access, revocation and onsite recovery for that separate management path.
Change one device and prove the result
Start with one known device, even if the final task covers several miners. This gives you a chance to discover unsupported characters, an unexpected menu, or a dependent tool still using the old credential before repeating the problem.
- Sign in through your approved local or private management connection. Confirm that the model and asset identity match the planned device.
- Open the documented administrator-password control. Supply the current password if requested, enter the replacement, and complete any confirmation field.
- Save or apply the change using the interface's documented action. Record the result without capturing the secret in screenshots or logs.
- Open a separate browser session that has not inherited the existing login. Authenticate with the new credential and verify the same device identity.
- Check the old credential in a fresh authentication context, subject to the device's lockout policy. One controlled rejection check is enough; do not repeatedly submit failed attempts.
- Update authorized tools that use this credential, then check their access and the miner's pool activity.
An already open dashboard can remain visible because it holds an existing session or cached authentication. Refreshing that page is a weaker test than a fresh login. Do not infer that all old sessions were revoked just because the password-change screen reported success; session behavior depends on the firmware.
Use this worksheet to decide whether the device is ready to return to routine management. Record results and times, keeping secrets out of the record.
| Check | Evidence to retain | If it fails |
|---|---|---|
| Correct device | Asset label, address, model and firmware | Stop and resolve the identity mismatch |
| New login | Fresh-session success for the intended administrator | Recheck the saved credential and documented input rules |
| Old credential | Controlled fresh-session rejection where permitted | Check session reuse and whether the change actually applied |
| Dependent tools | Current device data and successful authorized access | Update the relevant stored credential and retry once |
| Mining destination | Expected pool account and worker identity | Compare configuration with the approved baseline |
| Useful work | Accepted work visible over the pool's reporting window | Investigate the connection and worker settings separately |
| Handover | Vault entry reference, access owner and recovery contact | Complete the record before unattended operation |
Do not reboot solely to make the test feel more complete. Follow any restart instruction in the matching firmware documentation. If a restart is required, account for the interruption and verify access and mining again after initialization. A password change does not justify a factory reset when ordinary access still works.
If the new login fails, avoid turning a typo into a reset
Check the address and device identity again. Then check the username, password-manager entry, keyboard layout, accidental spaces, and whether the interface accepted the new value. A generic authentication error does not tell you which of those is wrong. Keep failed attempts within the documented lockout limits and pause if the device begins delaying or blocking access.
If the current password is truly unavailable, use the manufacturer's recovery route for that exact device. Default credentials vary across firmware and recovery instructions; do not assume that a commonly quoted username and password apply to your unit. Obtain the matching manual or support confirmation rather than cycling through guesses.
A recovery operation may remove network and pool settings. Use the factory-reset preparation checklist to preserve available configuration and fault evidence, identify the correct recovery procedure, and plan how you will rediscover the miner. If you cannot log in to export settings, record what remains available from inventory, the router, pool records and your management system. Note the gaps before proceeding.
Unexpected pool changes need a different response
If the miner changes to an unfamiliar worker or pool, repeatedly loses your settings, or shows other unexplained administrative changes, do not treat password rotation as proof that the problem is gone. Preserve the observations and isolate suspected devices from the normal management network while you investigate.
BITMAIN's guidance on compromised miners describes altered worker names and unknown pools, and places network isolation before recovery and password changes. Those observations are reasons to investigate; a single dashboard discrepancy is not a complete diagnosis. Follow current, model-specific vendor recovery instructions and review the computer or tools that manage the miner as well.
Changing the miner login also does not automatically revoke a separate remote-access account, agent enrollment, API credential or pool website session. Review those access paths individually. Do not restore a suspect configuration merely because doing so quickly makes the miner hash again.
How should a growing fleet handle credentials?
A shared password is convenient until a device changes hands, a contractor leaves, or one stored copy escapes your control. Individual device credentials reduce that shared exposure, but the operator must still be able to retrieve the right entry and recover access when a management tool fails.
The practical question is whether your inventory, password manager and supported fleet tools can keep device identity and credential ownership aligned. Before adopting a bulk workflow, test how it reports partial failures and how you will distinguish changed devices from unchanged ones. A single success message for the batch is less useful than a result for each asset.
Choose one miner and complete the worksheet before scheduling a wider rotation. As the fleet grows, revisit who can read credentials, who can change them, and how access is removed during handover. The useful record is a verifiable access history, not a spreadsheet full of reusable secrets.
Frequently asked questions
Is the pool worker password the miner login password?
They belong to different systems. The miner login protects its administration interface, while a pool worker field is part of the mining connection configuration. Some pools ignore that field; others define a use for it. Follow the chosen pool's instructions and keep administrator secrets out of worker settings. Changing the worker field will not change the password used to sign in to the miner's local dashboard.
What is the default password for an ASIC miner?
There is no default you should assume across all manufacturers, firmware releases and recovery methods. Even support material for one brand can describe different defaults for different workflows. Identify the exact model and installed firmware, then consult its matching official manual or support channel. Once authorized access is established, replace a shared default and store the replacement securely before relying on the device for unattended operation.
Does changing the administrator password stop mining?
Do not assume either uninterrupted mining or a mandatory restart for every firmware. Follow the documented apply and restart behavior of the installed version. Record the current pool and worker before the change, then check that the same account continues receiving accepted work afterward. If the documentation requires a restart, plan for that interruption and allow the miner to finish initialization before judging its mining state.
Why did monitoring fail after I changed the password?
A monitoring or management tool may still hold the previous credential. Confirm which account the tool uses, update that entry securely, and test its access to the intended device. Also check whether the miner is reachable and whether the pool still sees accepted work. A failed management login and stopped mining are separate observations; one does not establish the other without checking the relevant connection and worker records.
Should I factory-reset the miner if I forgot the password?
Recovery may require a reset or a different vendor procedure, but identify the exact device and consequences first. Preserve the configuration and logs you can still obtain, record missing information, and prepare a way to rediscover the miner afterward. Use the matching official instructions rather than another model's button sequence. If ownership, firmware or the recovery package is uncertain, resolve that uncertainty with the vendor before changing state.
Can I change all my miners' passwords at once?
Use bulk changes only when the tool supports the actual devices and firmware, and after a single-device trial succeeds. Keep a result for each miner, including fresh login verification and any dependent-tool update. A partial batch can leave different credentials active across the fleet. Maintain a secure mapping between asset identity and credential entry, and a local recovery path for devices that become inaccessible during the change.