It´s maybe the algo that´s the problem. You could test Solo Mining using Scrypt Algo with your GPU - or install Wallet 4.0.3 on another Computer and sync this Wallet using "addnode=ip adress of your 6.14.2" for a real fast sync and test this. One problem could be Segwit as the the old wallet dosn´t support Segwit.
Thanks for the input, hallo_frosch. I was using skein when I tried it, and it seems weird that the server wouldn't work with all algos, but it's worth a try anyways. Gonna test it when I have the time. I had to go back to 4.0.3 to solo mine, no issues with that version.
I've run tests with all algos with no success. In all cases, the local server appears as dead for all miners. Now, this would normally indicate incorrect IP/port configurations, but I'm using the exact same digibyte.conf file I use with version 4.0.3 of the wallet, the only changes being rpcauth replacing rpcuser and rpcpassword. With version 4.0.3 everything works fine.
Looking at the debug.log file generated by the 6.14.2 qt running as a server, right at the start I found these lines which seem to indicate that something IS wrong somewhere:
2017-06-19 23:07:40 Binding RPC on address :: port 14022 failed.
2017-06-19 23:07:40 HTTP: creating work queue of depth 16
2017-06-19 23:07:40 No rpcpassword set - using random cookie authentication
2017-06-19 23:07:40 Generated RPC authentication cookie C:\Users\Pedro\AppData\Roaming\DigiByte\.cookieFor the sake of clarity, here are the relevant lines of my digibyte.conf file:
rpcauth=MYUSERNAME:SALTSTRING$HASHSTRING
rpcallowip=192.168.0.99
rpcport=14022
port=12024
txindex=1
listen=1
debug=0
maxconnections=15
algo=groestl
(plus the addnode lines)
If you've noticed the absence of a server=1 line, that's because I prefer running qt with -server as a parameter instead of including that line in digibye.conf, but I've tried both ways just to rule this out.
Again, solo mining with this same config (and the previous rpc authentication method) works perfectly with qt 4.0.3. Any suggestions are welcome.