Re: ★★DigiByte|极特币★★[DGB]✔ DigiSync v6.14.2 - DigiSpeed - Segwit -DiguSign
digibyte.config
rpcauth=bycag:5drfd59a7d8a7fd953022fcfabf2121$58a7a7myauth8a7b6d203e093db8a30a3c305c9cb5
server=1
listen=1
deamon=1
rpcallowip=127.0.0.1
rpcport=14022
port=12024
maxconnections=10
txindex=1
algo=groestl
my config:
{
"pools" : [
{
"url" : "127.0.0.1:14022",
"user": "bycag",
"pass" : "GHF2qp4Pmypassb99kh1iBM="
}
I think this way. Only RPCauth in digibyte.conf and the user with generated password into your minerconfig.
rpcauth=bycag:5drfd59a7d8a7fd953022fcfabf2121$58a7a7myauth8a7b6d203e093db8a30a3c305c9cb5
server=1
listen=1
deamon=1
rpcallowip=127.0.0.1
rpcport=14022
port=12024
maxconnections=10
txindex=1
algo=groestl
my config:
{
"pools" : [
{
"url" : "127.0.0.1:14022",
"user": "bycag",
"pass" : "GHF2qp4Pmypassb99kh1iBM="
}
I think this way. Only RPCauth in digibyte.conf and the user with generated password into your minerconfig.
no work.. 127.0.0.1 slow/down or url or credentials invalid
Same problem here. The rpcauth/username/password part is correct both in digibyte.conf and the miner's config. I'm suspecting this might have something to do with the new rpcallowip format - it used to accept wildcards before so I just used rpcallowip=* (like with all other coin cores). With this version I tried both 127.0.0.1 and 192.168.0.99 (my network address), but neither worked. All ports are open etc. Going back to core version 4.0.3 until the changes introduced to solo mining by the new version are properly documented (or fixed).