Quote from: TrailingStop on April 19, 2019, 06:12:17 PM

Quote from: Shivoreun on April 19, 2019, 05:12:45 PM

Quote from: TrailingStop on April 19, 2019, 02:37:02 PM

Quote from: Shivoreun on April 19, 2019, 02:20:40 PM

Hi to community.
The remote API response in v2.2.2 is not working? Or there is some trick needed to get it to work?
I'am using Awesome Miner, and it can get the stats from the miner, but any other software can't connect to the specified port. The Awesome Miner uses --api-bind 127.0.0.1 network, but I assume this will allow only localhost connections, that's why it's working.
I've tried the -b 0.0.0.0:4034 and --api-bind 0.0.0.0:4034 (and different ports), but miner is not responding. According to the TCPview, the tt-miner.exe is binding on the specified port (4034), but no connection Sad

Is there some additional options that should be set to get remote stats via API?..

Hi,

0.0.0.0 will be translated to localhost (127.0.0.1). The default port is 4068. So if you have only a single network card installed on your rig you may want to try:
-b 127.0.0.1:4034

Did it work with an older version of TT and is now broken with 2.2.2, or is this just the first time that you try to get TT to work with Awesome Miner???

Thanks for reporting.

Thanks for reply

Previously I was using 2.1.14 and there were no such problem Undecided

Didn't tested another older versions yet...
Then, what I should set in "-b" option to allow API requests from any address?.. Looks like, that regardless of the settings, the miner accepts only connections from locahost Sad

Hi,

the miner does not filter any addresses. It looks to me like you have 2 (or more) network interfaces and the API bind to the wrong. The address you use for the api command is to tell the miner which network interface to enable for api access. If you have only one localhost is fine, if you have more it makes sense to tell the miner which one to use. You can check your IPs with 'ipconfig -all' command in the console. Let me know if that help or if you still have problems to get connected.

No, there is no 2nd interface present. The ping command to "localhost" corresponds to 127.0.0.1
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.

When miner starting, it says:
API-Interface enabled. Listening on 1

Any ideas?..