Quote from: Mikestang on February 03, 2016, 05:42:40 PM

Quote from: -ck on February 03, 2016, 11:19:32 AM

Hmm that reminds me I've had this problem before. If you authed first on the DE pool you cannot auth on the main pool later on. I thought I'd fixed this bug but it seems to have returned. That would explain it. I'll look into it.

Is this related to a bug I posted about a couple weeks ago? Well, I guess I don't know if it's a bug or a flaw in the way the miner operates, but just wondering.

Quote from: Mikestang on January 21, 2016, 06:07:08 AM

Quote from: Mikestang on January 21, 2016, 01:29:14 AM

Quote from: -ck on January 20, 2016, 11:35:48 PM

The IP address of solo.ckpool.org changes after a DDoS and perhaps these devices almost never look up the IP address using a cached result for ages. In which case a restart might be required, either of cgminer or the whole device.

I have restarted the whole device 3 times (one of those was power off for 20+ minutes) and it still is in failover, I'll see if I can't flush its dns cache or something, thanks.

Quote from: Nthused on January 20, 2016, 11:30:18 PM

I had the same bug a couple of weeks back, all I had to do was change the address I was mining to.

I could not locate any sort of dns reset in the S3 interface so I tried changing addresses and the pool was ALIVE again. I changed back to the old address thinking maybe I had cleared up the issue, but the old address reports the pool as DEAD. A new solo address for the US node it is then! Problem solved, thanks.

Changed mining to a new address and all seems to be well. Note that it had to be an entire new address, not just worker name. (so now I have different addresses for DE and main, but I suppose that's OK)