I agree with you, and that puts his post as a borderline shitcoin fork troll, unintentional or not.

Thanks. Looks like IPV6 was a DNS problem so it was worth fixing.



https://www.ssllabs.com/ssltest/analyze.html?d=solo.ckpool.org

Oh well, as good a time as any to drop the 444 then. I'll just disable it entirely.

It looks like bedla's poolstats grafana site doesn't like the change. Perhaps it needs to be revamped slightly. It could also show a decimal place for the pool diff% now as well.

Web server reloaded and https now working on the regular port 443. It's still enabled on port 444 in case people have sites linking there.

Pool's now been restarted as planned. Port 443 has been relinquished for the web server, a minor bugfix was committed for bitcoin daemon failover, and the diff% for the pool now shows 4 significant digits so we can get a decimal place even after 100% diff.

Next is the web server reconfiguration.

Spent the day unwell, nothing happened.

I'll switch over the pool tomorrow so the https server can finally rest on the correct port, and with it restart the pool for minor updates. As always downtime will be negligible. Is there any demand at all for port 80/443 mining? I'm not planning on trying to support it unless anyone says they want or need it.

Thanks for the feedback.
That will be because the proxy is mining at the pool diff, 10k, so your hashrate is too small to show up.

Thanks.

So has anyone actually tried it? I haven't had any feedback about whether it works yet...

Absolutely not.

There is no hashpower, they briefly connect, then the pool throws them off and they do it all over again. The pool is good for probably 100,000 users with its current hardware, I wouldn't worry...

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.

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:

It will not be directly executable, so execute it with

And follow the prompts. Tell me how you go.

Sure thing. I'll make installing it as simple as possible and will probably have something shortly.

I could probably create a simple package for people to use if there's demand for one.