Help Center

Some mining devices and mining software need special connection handling to work correctly with Mining Rig Rentals.

Mining Rig Rentals uses stratum routing to connect your miner to the correct rig endpoint. For many miners, this works automatically. Some miners, especially certain ASIC firmware versions, do not fully support the stratum client.reconnect command. These miners may need to connect directly to the rig’s assigned port instead of using the standard connection port.

This article explains what that means and when to use the direct rig port.

What is client.reconnect?

client.reconnect is a stratum command that tells a miner to reconnect to a different host or port.

Mining Rig Rentals may use this command to move your miner from a general connection endpoint to the specific port assigned to your rig. You can think of this like a front desk: the miner connects to the general address first, then Mining Rig Rentals directs it to the correct rig connection.

Most miners that properly support stratum reconnect handling will follow this instruction automatically.

Why Mining Rig Rentals uses reconnect routing

Mining Rig Rentals needs to route each miner to the correct rig connection so that rentals, pool changes, worker tracking, and hashrate accounting work correctly.

Reconnect routing helps Mining Rig Rentals:

• assign miners to the correct rig,
• keep rig connections organized,
• route rental traffic properly,
• switch pool targets when needed,
• track worker activity,
• avoid requiring every miner to manually use a unique port from the start.

For miners that support client.reconnect, this process is usually automatic.

When automatic reconnect works

Automatic reconnect usually works when the miner or ASIC firmware:

• supports standard stratum behavior,
• accepts client.reconnect,
• reconnects to the new host and port when instructed,
• preserves the configured worker name and password,
• resumes mining after reconnecting,
• submits accepted shares normally.

Most traditional Bitcoin-like stratum miners support this behavior. Many ASICs and GPU miners also support it.

If your miner supports reconnect correctly, you normally only need to use the standard Mining Rig Rentals connection information shown on your rig setup page.

When direct rig port connection is needed

Some miners do not follow the client.reconnect command correctly.

This is increasingly common with some modern ASIC firmware. The miner may connect to the standard Mining Rig Rentals address but fail to move to the assigned rig port.

When this happens, the miner may:

• show as connected locally but not appear correctly on Mining Rig Rentals,
• connect and immediately disconnect,
• keep reconnecting in a loop,
• never show active workers,
• fail to submit accepted shares,
• ignore the reconnect instruction,
• remain on the standard port instead of moving to the assigned rig port.

If your miner does not support reconnect properly, use the direct or assigned rig port shown in the rig’s connection information.

Standard connection vs direct rig port

Mining Rig Rentals may provide more than one way to connect a miner.

The direct rig port bypasses the automatic reconnect step. Instead of connecting to the general endpoint and being redirected, the miner connects directly to the port assigned to your rig.

This is often the correct solution for ASIC firmware that does not support client.reconnect.

How to use the direct rig port

To connect a miner using the direct rig port:

1. Open the rig’s connection information page.
2. Locate the red rig port button and click it.
3. Copy the server hostname and assigned port shown for that rig.
4. Enter that hostname and port into the miner or ASIC pool configuration.
5. Use the correct worker name and password from the rig setup page.
6. Save the miner settings.
7. Restart or reload the miner if required.
8. Confirm the worker appears online in Mining Rig Rentals.
9. Confirm accepted shares are increasing.

The key point is that the miner should connect to the rig-specific port rather than the generic starting port. The hostname and port are unique, the port is not valid on other servers.

ASIC setup notes

For ASIC miners, the direct rig port is usually entered in the ASIC’s pool configuration page.

A typical ASIC pool configuration includes:

• pool URL,
• worker name,
• password,
• backup pool URL,
• backup worker,
• backup password.

Use the Mining Rig Rentals connection information for the pool URL and port.

Make sure the ASIC is configured for the correct algorithm. The correct port will not fix an algorithm mismatch.

Backup pools and failover

If your ASIC supports multiple pool entries, configure backup entries carefully.

Do not point failover pools directly to a normal external pool unless you understand the effect. If the ASIC fails over away from Mining Rig Rentals during a rental, the renter may not receive the hashrate they paid for.

Recommended behavior:

• primary pool should point to the correct Mining Rig Rentals endpoint,
• backup Mining Rig Rentals endpoints may be used if provided,
• external failover pools should not interfere with active rentals,
• the miner should return to Mining Rig Rentals after a reconnect or restart.

If a miner frequently fails over, investigate the cause before listing the rig.

Confirm the miner is working

After changing connection settings, verify the rig through Mining Rig Rentals.

Check:

Do not rely only on the ASIC web interface saying “Alive” or “Connected.” Confirm accepted shares and worker activity.

Common problems

Miner connects but does not appear online

Possible causes:

• miner ignored client.reconnect,
• wrong port,
• wrong worker name,
• wrong password,
• firewall or network issue,
• miner is connecting to an old endpoint,
• ASIC firmware does not support the connection method.

Recommended action:

Use the direct rig port from the rig connection information page and verify the worker name.

Miner reconnects repeatedly

Possible causes:

• firmware does not handle reconnect correctly,
• wrong pool URL,
• wrong algorithm,
• network instability,
• miner watchdog restart,
• pool failover loop,
• bad DNS resolution,
• firewall interruption.

Recommended action:

Try the direct rig port, check miner logs, and confirm the ASIC is not failing over to another pool.

Miner appears online but has no accepted shares

Possible causes:

• wrong algorithm,
• wrong pool/rental target,
• unsupported ASIC firmware,
• bad worker or password format,
• share difficulty issue,
• miner is connected but not receiving valid work,
• renter pool is rejecting shares.

Recommended action:

Check the Workers tab, ASIC logs, rejected share messages, and pool-side status.

Miner works directly to a pool but not through Mining Rig Rentals

Possible causes:

• miner does not support client.reconnect,
• firmware has non-standard stratum behavior,
• worker name is not being passed correctly,
• the miner requires direct rig port connection,
• pool failover settings are interfering,
• the algorithm or port does not match the rig listing.

Recommended action:

Use the assigned/direct rig port and test again through Mining Rig Rentals.

Port changes and stale configuration

If your miner was configured a long time ago and suddenly stops connecting, confirm that it is still using the current connection information from the rig setup page.

Do not assume an old copied hostname or port is still valid. The hostname and port are unique, the port is not valid on other servers, change your rig's primary server and re click the port to obtain the new details.

If the assigned port changes, update the miner’s pool configuration with the current direct rig port information.

Summary

Most miners can use the standard Mining Rig Rentals connection information because they support stratum client.reconnect.

Some ASICs and mining software do not support this command correctly. Those miners should connect directly to the rig’s assigned port using the direct connection information shown on the rig connection page.

If the miner connects but does not appear online, reconnects repeatedly, or never submits accepted shares, check whether it needs the direct rig port.