Your comments
Had this "timeout" happen moments ago. From log:
i 13:07:51|stratum Received new job #0000018c
i 13:07:51|CUDA0 set work; seed: #d4f2e152, target: #000000068709
m 13:07:51|main Speed 30.34 Mh/s gpu/0 30.34 [A159+7:R0+0:F0] Time: 00:47
m 13:07:53|main Speed 30.34 Mh/s gpu/0 30.34 [A159+7:R0+0:F0] Time: 00:47
m 13:07:55|main Speed 30.34 Mh/s gpu/0 30.34 [A159+7:R0+0:F0] Time: 00:47
m 13:07:57|main Speed 30.34 Mh/s gpu/0 30.34 [A159+7:R0+0:F0] Time: 00:47
X 13:07:59|stratum Read response failed: End of file
i 13:07:59|stratum Reconnecting in 3 seconds...
i 13:08:02|stratum Connecting to stratum server eth.poolmining.org:3072
X 13:08:03|stratum Could not connect to stratum server eth.poolmining.org : 3072 , No connection could be made because the target machine actively refused it
i 13:08:03|stratum Reconnecting in 3 seconds...
X 13:08:06|CUDA0 Can't submit solution: Not connected
i 13:08:06|stratum Connecting to stratum server eth.poolmining.org:3072
X 13:08:07|stratum Could not connect to stratum server eth.poolmining.org : 3072 , No connection could be made because the target machine actively refused it
i 13:08:07|stratum Reconnecting in 3 seconds...
i 13:08:10|stratum Connecting to stratum server eth.poolmining.org:3072
X 13:08:10|CUDA0 Can't submit solution: Not connected
X 13:08:11|stratum Could not connect to stratum server eth.poolmining.org : 3072 , No connection could be made because the target machine actively refused it
i 13:08:11|stratum Reconnecting in 3 seconds...
i 13:08:14|stratum Connecting to stratum server eth.poolmining.org:3072
i 13:08:14|stratum Connected to stratum server eth.poolmining.org : 3072
Tested, confirmed, all good now! Thanks!
I checked the cookie, and it has an expiration status of "At end of session", so closing the browser expires the cookie. You probably want to set a different expiration state for it.
I don't think ethminer logs by default, would have to add that capability. So unfortunately no log to share from me, but will work on getting a log set up.
I think something similar has happened to me at around 15:20 CET today. I did not get that error but I noticed that my miner sort of hanged, it just stopped receiving new jobs and was stuck on one. The command line wasn't frozen, I could terminate with ctrl+c easily. Restarted then. I even noticed a massive drop in hashrate for the entire pool, instead of 1GHZ it showed around 600Mh for a minute or two.
I'm on ethminer.
Customer support service by UserEcho
Publicity - I noticed this, and this is how I hopped on. I do like your genuine honest and non-pushy approach.
Miner Trust - I also noticed the issues. Bugs happen, and I think you handled it well, offering to compensate to those that came out. Miner's complaining on Dash - well, yeah sorry miners, difficulty volatility is a b*, so yes, your way to go is to explain and educate. Maybe write a blog or reddit post on this from your POV, and post it in your answers to those that complain here? The public post can then again support the aforementioned publicity / awareness.
I honestly think lots of tech influence nowadays is through forums & reddit. Maybe a suggestion to you for not waiting for someone to drop a question on what pool to mine on, is to passively mention your pool in your reddit/forum posts, so if there is some mining related discussion, just chip in with a comment and passively and casually mention poolmining.org . I've mentioned your pool myself on some crypto discussions in Discord.