RMS Troubleshooting

Follow the complete path: miner → local RMS port → public network → RustMinerSystem RMS port → upstream pool. Locate the failed segment before changing settings.

Miners Cannot Reach RMS

• Confirm miners use the local address copied from the RMS table.
• Check whether DHCP changed the RMS device IP.
• Verify the local listener is running and not occupied.
• Allow the port through LAN and host firewalls.
• Confirm a remote server port was not entered directly into miners.

RMS Cannot Reach the Server

• Verify hostname-or-ip:port formatting.
• Confirm the server listener is running and reachable from the site.
• Match coin, protocol, and password exactly.
• Do not mix RMS3, RMS3(Zstd), RMS3(NB), and RMS2.
• Check security groups, firewalls, carrier filtering, and intermediate proxies.

RMS3(NB) Cannot Save or Connect

• Select BTC or LTC only.
• Select RMS3(NB) on both server and client.
• Keep every multi-address target on the same coin and NB protocol.
• Do not connect an NB mapping directly to RMS3 or RMS3(Zstd).

Reject Rate Increases

1. Check upstream latency, packet loss, and server CPU.
2. Increase the outbound connection count per port.
3. Reduce protocol compression strength.
4. Reduce miners handled by one RMS instance.
5. Return a small group to the bypass address for comparison.

Change one variable at a time and wait for metrics to stabilize.

Unexpected Outbound Count

Different local ports and coins form separate groups; multiple remote targets add paths; automatic and manual ports may run together. Confirm the current connection count was saved and applied.

Blank GUI or Inaccessible Backend

For a blank Windows GUI, keep WebView2Loader.dll beside rms-production-gui.exe and install the Edge WebView2 Runtime. For backend access, check the process, management port, firewall, and safe path. A safe-path URL requires the trailing /.

Rollback Checklist

Keep a direct RustMinerSystem bypass address, RMS version and mappings, compression settings, RustMinerSystem port JSON, previous working configuration, and upgrade logs. During a major incident, stop expanding and return the pilot group to bypass. Restore the recorded connection count and compression settings. When changing protocols, create a new matching server/local port pair; never change only one side.