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...

Improve this question

2 Answers 2

Reset to default
2

One possible reason may that with Bitcoin Core 0.13.1, it was mandatory to use SegWit-compatible mining software. When SegWit transactions are included in a block, a coinbase commitment to the witnesses is required by consensus rules. As the eventual selection of transaction in the block is done by the mining software, old mining software cannot be used to construct a SegWit block. On testnet, SegWit (BIP141) has been active since May 2016.

In Bitcoin Core 0.14, a change was made that permits old mining software to continue to operate. When such software is detected, Bitcoin Core will simply return a block template that excludes any SegWit transactions, alleviating the need for a coinbase commitment.

Improve this answer
0

I think your subnet definition in rpcallowip is wonky. You are only allowing connections 0.0.0.1 - 0.0.0.254 to connect to your client. This excludes your localhost and probably your LAN.

http://jodies.de/ipcalc?host=0.0.0.0&mask1=24&mask2=

What you are probably after is 127.0.0.1/32, or use your LAN subnet (192.168.0.1/24 ?).

rpcallowip=127.0.0.1
rpcbind=127.0.0.1:18332
Improve this answer
7
  • 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
    May 30, 2017 at 19:46
  • I would check the bitcoind debug.log file, it may hold a clue. Are you connecting cgminer directly or using a stratum layer?
    – lavajumper
    May 30, 2017 at 19:51
  • 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``` it said that it receive the request but in other hand cgminer gives the same error --- Edit: I'm connecting cgminer directly with cgminer --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
    – max-lt
    May 30, 2017 at 19:54
  • 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
    May 30, 2017 at 20:00
  • 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
    May 30, 2017 at 20:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.