0
I want to try mining on testnet, I'm using cgminer and I got it working on the main network but when i'm runnig it on testnet I got (in debug mode):
] Testing pool http://127.0.0.1:18332
] Probing for GBT support
] HTTP request failed: The requested URL returned error: 500 Internal Server Error
] Failed to connect in json_rpc_call
] No GBT coinbase + append support found, pool unusable if it has no stratum
] HTTP request failed: The requested URL returned error: 500 Internal Server Error
] Failed to connect in json_rpc_call
] No Stratum, GBT or Solo support in pool 0 http://127.0.0.1:18332 unable to use
I've tried with the generate=0 and gen=0 options but it seems to have no effect.
Currently my .conf file looks like:
testnet=1
server=1
txindex=1
rpcallowip=0.0.0.0/24
rpcbind=0.0.0.0:18332
printtoconsole=-1
debug=1
I'am running bitcoind version 130100.
It seems that many tuturials are outdated and that some options/features changed (like bitcoin core Removal of internal miner)
Is there something that I've missed ?
EDIT: @lavajumper: actually you where right about rpcallowip, but in my case there were others rpcallowip definition and it wasn't the cause of my problem (0.0.0.0/24 leads to a 403 (unauthorized) error).
After upgrading the version of bitcoind (version 140100, protocolversion 70015), I was able to run it, (but during the blockchain verifcation, there were 500 errors too).
For now i'm stil not able to run it with bitcoind 130100, and i don't know why...
Well allowip=0.0.0.0 allows everything (the current config is quite the same as the one that I use on the real network, witch works). I tried your solution but it wasn't the problem, still have the same error :/ – max-lt – 2017-05-30T19:46:00.130
I would check the bitcoind debug.log file, it may hold a clue. Are you connecting cgminer directly or using a stratum layer? – lavajumper – 2017-05-30T19:51:50.670
Tried too from the local network, but I've got the same results in the bitcoind debug console: > Received a POST request for / from 192.168.0.15:44976 > Received a POST request for / from 192.168.0.15:44978
– max-lt – 2017-05-30T19:54:59.683`` it said that it receive the request but in other hand cgminer gives the same error --- Edit: I'm connecting cgminer directly withcgminer --anu-freq 250 -o http://192.168.0.15:18332 -u $BITCOIN_CORE_USER -p $BITCOIN_CORE_PASS --btc-address $ADDRESS --btc-sig $SIG -D`https://en.bitcoin.it/wiki/Running_Bitcoin ; rpcbind uses host:port notation for ipv6, otherwise I set the 'rpcport' option. Also, I usually set rpcuser and rpcpassword. The 500 error suggests there is something on the bitcoind side that is not right. – lavajumper – 2017-05-30T20:00:47.447
rpcuser and rpcpassword are set, I just did not posted it, tried with or without rpcbind, the bitcoind log doens't report any error at this stage, it doesn't at all actually ... – max-lt – 2017-05-30T20:12:03.540
I'm a little stumped at that point myself. Things I would check first: Are you connected to testnet? Have you checked connecting with bitcoin-cli to confirm its synced? Can you get 'getpeerinfo' ? Can you get 'getmininginfo'? Maybe try to set up a stratum proxy and see if that can connect. ? Like I said, the 500 errors suggests that cgminer is talking to bitcoind, but bitcoind ( at least the json-rpc server part ) is choking. I don't believe cgminer would report 500 if it wasn't getting it from bitcoind. – lavajumper – 2017-05-30T20:31:16.043
Let us continue this discussion in chat.
– lavajumper – 2017-05-30T20:36:23.727