Quote from: mdude77 on December 08, 2014, 11:31:49 PM

Would you please run the "get miner info" button in the latest beta on your non monitorable S3 and PM me the output please?

Download link: MMinerMonitor40ba.zip

M

Get Miner Info sent via PM as requested.

Cheers n beers

HPmuirt

P.S. I thought I would check the log as the new beta also had the reboot selected by default and found the following: -

08/12/2014 23:54:07: M's Miner Monitor v4.0b1 starting
08/12/2014 23:54:07: Initiated Ant refresh
08/12/2014 23:54:08: ERROR when querying S3:0.102 (step 1): Object reference not set to an instance of an object.
08/12/2014 23:54:08: Attempting to reboot S3:0.102 via the web because the API query errored out.
08/12/2014 23:54:08: REBOOTING S3:0.102 via SSH
08/12/2014 23:54:26: Reboot of S3:0.102 FAILED: Permission denied (password).
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:59:11: Initiated Ant refresh
08/12/2014 23:59:11: ERROR when querying S3:0.102 (step 1): Object reference not set to an instance of an object.
08/12/2014 23:59:11: Attempting to reboot S3:0.102 via the web because the API query errored out.
08/12/2014 23:59:11: Need to reboot S3:0.102 but it hasn't been long enough since last reboot

Is the reason that the App cannot monitor unit 102 that it has not accepted the IP address even though the config screen reports the correct IP address?