Dear user 136CrBTFqaLShQVTzhH2MRUauRrrzP7JbG please fix your miners. You have been connecting and disconnecting continuously hundreds of thousands of times for months now without ever successfully mining, so I have blocked your IP address.
Would this situation be similiar to a small ddos attack on the server? Can a script be written to flag and deny access to these connect / disconnect users? The pool already gracefully handles them, I just log to see what's going on in case someone needs help. |
|
|
|
|
Dear user 136CrBTFqaLShQVTzhH2MRUauRrrzP7JbG please fix your miners. You have been connecting and disconnecting continuously hundreds of thousands of times for months now without ever successfully mining, so I have blocked your IP address.
|
|
|
|
|
So on further consideration, I've decided to abandon port 443 mining on the pool. Given the hosting provider is censoring access without my involvement, it is not really serving any purpose and is just confusing the https issue. If there are any objections, please speak up now or I'll drop it within the next week.
|
|
|
|
|
I figure what happened when I tried to set up a relay in Germany is that I rented a VPS from an American hosting provider with a presence in Germany and all the big hosting providers from the USA are obligated to block Iran. If I'd gone with a European provider it might not have been a problem, as evidenced by O solo miner succeeding with his passthrough.
|
|
|
|
I have a dumb question I hope you can answer, What argument do I use to change difficulty for your pool? is it only by port? ive never used an s9 before and ive tried d= diff= --suggestdiff but non seem to stick.
S9s never supported the main cgminer code so they never adopted the --suggest-diff setting properly. However, normally there's no point in adjusting diff anyway, the pool knows best, and diff is purely cosmetic when mining solo anyway. The only reason to manually set diff when mining solo is to minimise bandwidth by setting diff up. If you really want your bandwidth to be as low as possible, just mine on the high diff port 4334. The pool won't accurately report your hashrate but it makes no difference to your chance of finding a block. |
|
|
|
I've created a script for Ubuntu (suggest 20.04) or Debian linux which should automate the setup, configuration, and install of a ckproxy to mine on the solo pool, though you can edit it afterwards to mine wherever you like. I do not suggest using something like an RPi as you want reasonable performance from your proxy to avoid any added latency. Download the following script: http://ck.kolivas.org/apps/soloproxy/setupsoloproxy.sh It will not be directly executable, so execute it with And follow the prompts. Tell me how you go. |
|
|
|
I could probably create a simple package for people to use if there's demand for one.
Only the last couple weeks alone i read a handful of people asking for it, in many none "1st class" countries internet is very expensive and limited, also some farms are hosted in remote places and rely on limited cellular data, a simple package for newbies would be really really great IMO. Sure thing. I'll make installing it as simple as possible and will probably have something shortly. |
|
|
|
Would you be so kind and make a newbie guide for how to set the mining proxy? I see a good number of people having issues with limited bandwidth and using a proxy is probably their best option, there is a lack of documentation online in regards to that subject, or at least I have not found any article that explains the steps to the average joe, so if you could do that it will be huge and very highly appreciated.
I could probably create a simple package for people to use if there's demand for one. |
|
|
|
@ -ck
where is the ckproxy discussion at?
i redid my linux system and need to readup
a little bit on that topic
it used to be in your sig but not anymore
The link is on the solo homepage, but here it is again: https://bitbucket.org/ckolivas/ckpool |
|
|
|
I've added a redirection to the stats provided by our gracious user @bedla at http://solostats.ckpool.orgI'd love to host the stats page on the pool itself but unfortunately bedla hasn't offered to provide the code so for the time being you'll have to be redirected to his setup. I'll probably be dicking with the secondary IP today to make http to https redirect work properly. Long term I will be removing port 443 mining, as it appears to not be helping anyone and making the website unnecessarily complex. |
|
|
|
People have asked me how long the miner who solved the block has been mining for. I don't know exactly since their hashrate may have fluctuated over that time. However, assuming they always mined to the same address, they currently have 2486021304645 shares. Dividing that by the current difficulty of 13732352106018.34 that means he found the block at about 18% diff, so in less than 1/5th of the expected time for the current diff. If they've been mining with a stable 70TH all along, they've been mining for a very long time here.
It was not always 70 Th) sometimes there was a rental of about 1PH. I figured as much. Ah so it was you. Your previous message was a little cryptic. block solved)
Thanks)
Congratulations  There was no need to reveal yourself, but I'm sure you'll be happy to be congratulated. |
|
|
|
|
People have asked me how long the miner who solved the block has been mining for. I don't know exactly since their hashrate may have fluctuated over that time. However, assuming they always mined to the same address, they currently have 2486021304645 shares. Dividing that by the current difficulty of 13732352106018.34 that means he found the block at about 18% diff, so in less than 1/5th of the expected time for the current diff. If they've been mining with a stable 70TH all along, they've been mining for a very long time here.
|
|
|
|
|
Funnily enough, with this block solve, I've finally found out why the pool's best share counter lags behind after a block solve. It only increments with a user's "bestever". It's a harmless cosmetic problem only, but will be addressed in the next pool restart whenever that happens. There are no outstanding bugs or issues so I don't really see much point in restarting it for such a cosmetic issue. The only reason I might consider restarting it is to provide an extra IP for port 80/443 mining, and use the correct port for https on the pool. As it stands there isn't much demand for any of the above so I'm loathe to messing with the status quo.
|
|
|
|
Looks like a block hit!!!
And there it is! It's nice to have confirmation everything's working perfectly fine on the pool, and to finally break through that 8 bit barrier for our 256th block! Congratulations to the miner, and all the people who contributed to help keep the pool alive. And only a 50TH miner! [2020-06-03 21:30:14.977] Possible block solve diff 26941303407284.085938 !
[2020-06-03 21:30:15.042] BLOCK ACCEPTED!
[2020-06-03 21:30:15.043] Solved and confirmed block 632928 by 1JfDwdSURAxgWqbQRQz4sY12wniGY3Sxtj.18
[2020-06-03 21:30:15.043] User 1JfDwdSURAxgWqbQRQz4sY12wniGY3Sxtj:{"hashrate1m": "49.1T", "hashrate5m": "52.9T", "hashrate1hr": "55.2T", "hashrate1d": "77.1T", "hashrate7d": "77.7T"}
[2020-06-03 21:30:15.043] Worker 1JfDwdSURAxgWqbQRQz4sY12wniGY3Sxtj.18:{"hashrate1m": "11.4T", "hashrate5m": "12.4T", "hashrate1hr": "12.7T", "hashrate1d": "13.6T", "hashrate7d": "13.5T"}
[2020-06-03 21:30:15.046] Block solved after 22464198046703 shares at 148.4% diff
|
|
|
|
|
Please note that from now on I will be archiving stats from users who have not mined in a month for efficiency reasons. If for some reason you want them reinstated, you can just ask.
|
|
|
|
The thing is that port 80 works just fine, HTTP requests go through just fine, when he managed to connect earlier I guess it was on can you enable port 80 for testing? stratum+tcp://solo.ckpool.org:80 if not, or if that doesn't work, setting up a relay in EU if other people agree to it will be worth it, I can only assume that a good number of miners reside in the east side of the world, so a relay pool will solve both ISP restrictions and latency. No, when he connected the denode port 80 hadn't been enabled yet. I can't enable port 80 on the pool since that's where the http server is. Connecting with http doesn't mean you'll be able to mine because there is probably a transparent proxy at his end which is proxying http traffic and would fail with stratum traffic. |
|
|
|
I believe CK said Iran is blocked from the pool. That could likely be your problem  No, I'm not blocking anything at all. |
|
|
|
Of course, I think this time is 15 seconds. Not 15 minutes!
I was just checking different ports on solo.ckpool.org.
I don't know how it got connected for a moment!
But now I checked again a few times. But it doesn't work anymore!
Yes 15 seconds sorry. How long are you waiting? Maybe you need to wait longer for it to connect? The ports that work on solo.ckpool.org are 3333, 443, and 4334 |
|
|
|
Try each of the following: denode.ckpool.org:3333
denode.ckpool.org:443
denode.ckpool.org:80
All is dead!  I saw you authorise on the pool at this time: [2020-05-28 23:15:29.387] Authorised client 1085395 worker 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR as user 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR and then drop at this time: [2020-05-28 23:15:44.775] Dropped client 1085395 user 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR worker 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR So at some stage you successfully connected for 15 minutes (approximately 90 minutes ago). What did you do then? |
|
|
|
Try each of the following: denode.ckpool.org:3333
denode.ckpool.org:443
denode.ckpool.org:80
Update: Note I've disabled these since this post if anyone was trying them. |
|
|
|
|
Show Posts
