Quote from: TrailingStop on April 25, 2019, 10:28:06 AM

Quote from: Balzhur on April 25, 2019, 09:26:51 AM

Quote from: Shivoreun on April 25, 2019, 07:10:38 AM

Commandline for the miner is:
tt-miner -a mtp -A MTP-100 -P stratum+tcp://

.nvidia01:x@zcoin-eu.mintpond.com:3000 --api-bind 127.0.0.1:4035

The rig is on Win10, has local IP 192.168.128.21, firewall is disabled for all networks, WinDefender disabled via registry. IPv6 is disabled.

The telnet localhost 4035 - miner answering.
The telnet 127.0.0.1 4035 - miner answering.

Trying from another rig, in the same network (192.168.128.20)
telnet 192.168.128.21 4035 - connection denied.

No wonders as you have bound API to 127.0.0.1 which is localhost. It is not accessible from LAN.
Technically you should modify the command line to utilize --api-bing 0.0.0.0:4035

0.0.0.0 means ALL of the computer IP addresses present, so it should include 127.0.0.1 and 192.168.128.21 which I assume is your LAN IP address.

However, looking at what TrailingStop wrote above "0.0.0.0 will be translated to localhost (127.0.0.1)." I doubt this will work until TT fixes this behavior.

OR

Just use --api-bind 192.168.128.21:4035 and API will be accessible from LAN, but you may have issues with your miner (awesomeminer or NHML or smth else) if any.

Hi,

This is 100% correct. I bound 127.0.0.1 to localhost. I was not aware that it should bound to all. Will fix that in next release.
Thanks for pointing to this issue.

Dear developer, when we can expect for fixing this issue? Roll Eyes

BTW, thanks for this miner. It's the best now for MTP