Quote from: cryptodredge on August 06, 2018, 11:25:18 AM

Quote from: sidog on August 06, 2018, 01:06:31 AM

the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?

Quote from: Burnie on August 06, 2018, 02:53:14 AM

Does CryptoDredge close the sockets properly before exiting?
I see a lot of TIME_WAITs when CryptoDredge is running, and they slowly disappear when CryptoDredge is stopped.
If CryptoDredge is started after 3-4 minutes, the api seems to start ok.

Quote from: darkneorus on August 06, 2018, 03:06:51 AM

yup, often the miner tries to use the default API bind address and port (127.0.0.1:4068) instead of using the address from its command line arguments.

Quote from: pgj69 on August 06, 2018, 05:20:09 AM

With 0.8.2 the API server is not always started as set by the command line.

Quote from: terryborg on August 06, 2018, 07:13:34 AM

Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.
thanks

Quote from: elkiki1 on August 06, 2018, 10:25:05 AM

+1 on API fix, good miner but unusable by most of us in actual state!

Quote from: BartVanseer on August 06, 2018, 09:48:58 AM

It still mines correctly but you cannot see what you are making and awesome miner will restart the miner because the accepted share does not increase.. need a fix quickly

This bug has already been fixed, update will be delivered soon. What OS do you use?

Win7 X64 ,
thanks