Thanks again 
b4f5baca8d70a9c6c568350099554ed1dd3fd5dc5ed0f30705aa80d283dab658
congrats!b4f5baca8d70a9c6c568350099554ed1dd3fd5dc5ed0f30705aa80d283dab658
thats awesome!
Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 258. (Read 1514780 times)
December 26, 2015, 09:40:06 PM
thats awesome!
December 26, 2015, 07:35:56 PM
I haven't seen any burps at all, actually. Been running solo.ckpool as primary, de.ckpool as #2, Slush as #3, since your post on having taken care of the DDoS stuff. No failovers.
Appreciate you.
Thanks for the feedback. I go to great lengths to make all transitions seamless at the mining end to avoid any downtime. However given your feedback it doesn't sound like you're using miningrigrentals? They're the ones having issues with the DDoS protection.Appreciate you.
No, I'm not using the MRRs. As I don't pay for power, I own my machines and enjoy a relatively short ROI, so long as spot stays reasonable (and I mine on Slush). I decided to go solo for a while (as a profiler mentor used to say, "just for giggles"), but shortly after changing configs I couldn't get to any of the three sites during the period when they were all down (thought I was SOL). After you put in the redirects (I'm assuming that's what you did...it's what I would have done) they returned to "normal" on 3333. FWIW...I run 4 S3s (I call them Dopey, Sneezy, Sleepy, and Grumpy) and one S2 (Doc...highly modded to run reliably in tropical conditions without A/C) that was my first box. Will be adding two more S3s on the first. Would prefer to have 3 S7s, as I have about 60A of available power on three circuits, and it would manage those well, giving me around 12Th, as opposed to the max 6.5 I could produce using S3s...but I have to wait to generate the capital for that.
December 26, 2015, 07:30:30 PM
Should we still be using port 3335 for tubes? I haven't been able to connect back up since the attack.
Really? It seems to be working fine as far as I can see. Only solo.ckpool.org has a tube proxy on port 3335 December 26, 2015, 07:22:01 PM
Should we still be using port 3335 for tubes? I haven't been able to connect back up since the attack.
December 26, 2015, 06:17:23 PM
Just rented some hash at mrr and used port 3333 for both de and solo pools was achieving half hashrate (-40TH of 80TH rented).
Have changed ports to 3334 and hashrate now showing correctly @ 80TH
.
Well that's no good... will have to investigate further, thanks for the feedback. Stick to 3334 for now Have changed ports to 3334 and hashrate now showing correctly @ 80TH
.Thank you. Sorry to give you more of a headache but thought you needed to know
. December 26, 2015, 06:11:06 PM
Just rented some hash at mrr and used port 3333 for both de and solo pools was achieving half hashrate (-40TH of 80TH rented).
Have changed ports to 3334 and hashrate now showing correctly @ 80TH.
Well that's no good... will have to investigate further, thanks for the feedback. Stick to 3334 for now Have changed ports to 3334 and hashrate now showing correctly @ 80TH
. December 26, 2015, 06:06:10 PM
Just rented some hash at mrr and used port 3333 for both de and solo pools was achieving half hashrate (-40TH of 80TH rented).
Have changed ports to 3334 and hashrate now showing correctly @ 80TH.
Have changed ports to 3334 and hashrate now showing correctly @ 80TH
. December 26, 2015, 06:02:17 PM
I haven't seen any burps at all, actually. Been running solo.ckpool as primary, de.ckpool as #2, Slush as #3, since your post on having taken care of the DDoS stuff. No failovers.
Appreciate you.
Thanks for the feedback. I go to great lengths to make all transitions seamless at the mining end to avoid any downtime. However given your feedback it doesn't sound like you're using miningrigrentals? They're the ones having issues with the DDoS protection. Appreciate you.
December 26, 2015, 05:58:29 PM
For miners who were having trouble with MRR rentals on port 3333, could you please try it once more and see if it's any better and report back? It may still come up with a warning, but I'm hoping they will stay connected and mine now. I'll keep port 3334 up for the time being...
For people who were using the solopass.ckpool.org name please revert back to solo.ckpool.org and choose one port for your work case instead please. Sorry about all the shuffling. I want to just use the solo. and de. URLs only.
I haven't seen any burps at all, actually. Been running solo.ckpool as primary, de.ckpool as #2, Slush as #3, since your post on having taken care of the DDoS stuff. No failovers.
Appreciate you.
December 26, 2015, 05:29:34 PM
For miners who were having trouble with MRR rentals on port 3333, could you please try it once more and see if it's any better and report back? It may still come up with a warning, but I'm hoping they will stay connected and mine now. I'll keep port 3334 up for the time being...
For people who were using the solopass.ckpool.org name please revert back to solo.ckpool.org and choose one port for your work case instead please. Sorry about all the shuffling. I want to just use the solo. and de. URLs only.
December 26, 2015, 01:21:11 PM
when we rent from nicehash big th/s, there are lots of miners. must we set diff in password area anything? because mining same btc adress lots of miners on your solo pool.
Ckpool has vardiff which sets it all automatically you don't have to do anything manually. December 26, 2015, 11:23:27 AM
Just put another 20TH of my miners to DE pool... Let's get some blocks
December 26, 2015, 11:10:13 AM
when we rent from nicehash big th/s, there are lots of miners. must we set diff in password area anything? because mining same btc adress lots of miners on your solo pool.
December 26, 2015, 09:34:53 AM
Renters that have incompatible services (such as MRR) can use port 3334 alternatively. Added this comment to the opening post.
Trying to find the best way to serve everything is tricky when MRR doesn't support every stratum feature...
Trying to find the best way to serve everything is tricky when MRR doesn't support every stratum feature...
December 26, 2015, 09:02:47 AM
+1
Mrr problem ??
Mrr problem ??
December 26, 2015, 07:58:02 AM
I am having a similar problem. My Mining Rig Rentals hash rate is showing as 0 but when i view statistics i can see a hash rate.
December 26, 2015, 07:53:27 AM
Both my Mining Rig Rentals stop hashing when I put them back here. Ideas?
See your private messages. 
December 26, 2015, 07:50:25 AM
Both my Mining Rig Rentals stop hashing when I put them back here. Ideas?
December 26, 2015, 07:40:21 AM
Are the pools working again?
Sure are, behind extra layers of protection now.Woo Hoo!!! Last night my Mining Rig Rentals didn't like either pool. The seem to be working now.
December 26, 2015, 07:37:16 AM
Are the pools working again?
Sure are, behind extra layers of protection now. Jump to: