TMS troubleshooting

TMS Troubleshooting

Most TMS issues come from mismatched server/client settings, local port reachability, aggressive compression, or route/security changes.

Miners Cannot Connect To TMS

Check:

• Miners are using the TMS local address, not the remote server port.
• The local listening port is created and running.
• LAN firewall allows miner access to the TMS host and port.
• The port is not occupied by another process.
• The miner URL uses the copied stratum+tcp://LOCAL_TMS_IP:PORT format when appropriate.

TMS Cannot Connect To Server

Check:

• Remote address uses address:port format.
• The TCMinerProxy server TMS protocol port is running.
• Local remote protocol matches the server listening protocol.
• Coin is the same on both sides.
• Password is identical on both sides, or empty on both sides.
• Security group, firewall, or upstream network does not block the server port.

Reject Rate Increases

Use a conservative rollback path:

1. Lower TMS3 compression level.
2. Disable super compression on both server and local TMS client.
3. Increase connection compression count.
4. Reduce miner count per TMS client.
5. Check upstream pool latency and server CPU.

Small coins or uncommon miner firmware may be more sensitive to aggressive TMS3 settings.

Outbound Connection Count Is Unexpected

Check:

• Connection compression count.
• Different coins and different local ports form separate outbound groups.
• Multiple remote peers can create more outbound paths.
• Auto-fetched and manual ports may both be running.

Backend Route Or Password Problem

If the safe access route was configured incorrectly:

• Remember that the route must not start or end with / during input.
• When visiting it, the final URL should end with /.
• If the program restarted and the route is lost, use the saved preview URL or local service access method from your deployment notes.

If the backend password was changed and lost, follow your deployment’s reset procedure or restore from a known configuration backup.

Rollback Plan

Before production rollout, keep:

• A direct TCMinerProxy proxy address for miners.
• TMS client version and port configuration backup.
• TCMinerProxy port JSON backup.
• Original compression count, compression level, and super-compression state.

During a major incident, first return to low compression or disable super compression. If the site is still unstable, point miners back to the direct TCMinerProxy proxy address while TMS is repaired.