Topic: Can't connect to Bitcoin Core 0.10.0 to solo mine (Read 4269 times)

If you're using Windows 7 or 8, you also need to go into the Windows Firewall and click on Advanced then allow the ports you want to use for Bitcoin Core.

you need a stratum proxy to convert the getwork (old mining software protocol) to stratum (new mining software protocol) new wallets only support stratum and odds are your old mining software is trying to send getwork. its a bit more complex to setup.

You could test too Latest stable version of Bitcoin Core: 0.11.0  to see if you are able of only mining with this. By the way you dont have mentioned about your hashrate, Guy upside have mentioned that you could are receiving orphaned blocks if your hashrate is very low. Anyway must be fun are
waiting on  found a block yourself but the probability is very very low almost impossible. You could are looking for a block with only mining for years and years and never found one. You must better consider join to a pool.

My post explained that you CAN mine to core. Just make sure you have it set up correctly. Though mining solo with regular network and bitcoind setup would be crazy with the current bitcoin network requirements with high transaction counts, bandwidth requirements and the potential to be working on stale work so that even if you did find a block it would likely be orphaned. Using a service like my solo pool is a much safer option if you wish to solo mine.

Yeah, I just updated to core 10... and can't solo mine either.  So game over?  I'm just trying to win the lottery every 10 minutes.

The getwork protocol was removed from bitcoin core since it was a pointless way to mine and didn't scale to modern hardware. You need modern mining software to be able to solo mine to it now. Try with the current cgminer pointed at bitcoind (even if you don't have any mining hardware), but you have to specify a mine-to address with --btc-address as extra to solo mine.

So every time a new official version of Bitcoin Core is released I try to connect to it to check if solo mining is working with a GPU like in the old days. For that I use the latest version of CGMiner which supported GPU's (v3.7.2) and GUIMiner. This worked fine with all versions up to 0.9.3 with the bitcoin.conf below:

rpcuser=XXX
rpcpassword=XXX
rpcallowip=*
rpcport=8332
daemon=1

From a command prompt, I run Bitcoin-Qt.exe with the -server parameter or bitcoind.exe and can connect and solo mine with no problems.

After upgrading to Core 0.10.0 and reading that it had changed the rpcallowip behavior and wildcards won't work anymore, I made these changes to bitcoin.conf (one at a time) to accept connections from ANY IP (I'm not concerned about security in this particular case):

rpcallowip=::/0

rpcallowip=0.0.0.0/0

I tried those on my local machine and also on a VPS, and neither CGMiner nor GUIMiner could connect to the server. For the local machine I also tried rpcallowip=127.0.0.1, and on the VPS I tried rpcallowip=mycurrentIP with no success either.

CGMiner says "Pool 0 slow/down or URL or credentials invalid" and GUIMiner says "[Errno 10061] No connection could be made because the target machine actively refused it".

Reverting to Core 0.9.3 with rpcallowip=* I can connect to the server and solo mine with no problems. I'm connected to the internet via ADSL with the modem on bridge mode, so port forwarding is not the issue. It would seem that I'm setting rpcallowip wrong, so any help would be appreciated.