How do I set a backup pool in XMRig?

To set a backup pool in XMRig, add a second pool to the pools list in your config.json file, below your main pool. XMRig tries pools in list order and can move to the backup if the main pool becomes unavailable.

Add the backup to your configuration

Stop XMRig and make a copy of your current config.json before editing it. This gives you an easy way to undo changes.

Here is a minimal example with one main pool and one backup:

{
  "retries": 5,
  "retry-pause": 5,
  "pools": [
    {
      "algo": "rx/0",
      "url": "primary.pool.example:3333",
      "user": "YOUR_MONERO_WALLET_ADDRESS",
      "pass": "x",
      "enabled": true,
      "tls": false
    },
    {
      "algo": "rx/0",
      "url": "backup.pool.example:3333",
      "user": "YOUR_MONERO_WALLET_ADDRESS",
      "pass": "x",
      "enabled": true,
      "tls": false
    }
  ]
}

These pool addresses are placeholders, not working servers. Replace them with the addresses and ports supplied by your chosen Monero pools.

If your file already contains other settings, keep them. Add the second pool inside the existing pools list rather than replacing your whole configuration.

JSON, the settings-file format XMRig uses, requires careful punctuation. Put a comma between the two pool entries, but not after the last entry.

Match each pool’s connection settings

Check each pool’s setup instructions separately. Your backup does not have to use the same connection settings as your main pool.

• url is the pool’s server address and port number. A port identifies the connection service at that address.
• user is usually your Monero wallet address. Some pools require a different account or worker format.
• pass is often "x", but a pool may use it for a worker name or other options.
• tls enables an encrypted connection. Set it to true only when using a pool port that supports TLS.
• algo: "rx/0" selects RandomX, the mining calculation method Monero uses.

Use a Monero pool endpoint, not an endpoint intended for another coin. Never enter your wallet’s recovery phrase or private keys; a pool does not need them.

Understand when the backup takes over

The first enabled entry is your main choice. The second is a fallback, not a second pool that receives half your mining work.

The top-level settings control connection retries:

• retries: 5 allows five retries before switching to another server.
• retry-pause: 5 sets a five-second pause between retries.

Those settings do not guarantee a switch in exactly 25 seconds. Detecting a failed connection and waiting for connection attempts can take additional time.

Restart and check the result

Save your file, then restart XMRig using that configuration. Check its console output for the expected pool address and accepted shares—pieces of mining work the pool has verified.

For a controlled backup test, temporarily disable the main entry with "enabled": false and restart. Confirm that the backup connects and accepts shares. Then re-enable the main entry and restart again.

Each pool tracks earnings separately. A short backup session may leave a balance below that pool’s minimum payout.

The bottom line

Put your main pool first and your backup second. Verify both pools’ settings, test the backup, and remember that failover protects mining continuity—not combined payouts.