I have a few computers in my house that I usually have no problem solo mining various coins with. But for whatever reason, this decred is really hard to tie in various PCs in my house to get them all mining together at the same time. I've only been able to get one of my rigs linked up and of course that is the one where I have the wallet. I simply don't want to manage 3 different wallets when, in the past, I didn't have to. I've played with the notls and tried various configurations of rcp.cert configurations and nothing seems to work. I get "http error. refused connection" Usually, you just rpcport rpclisten or whatever on whatever IPs and presto, you are mining. But this thing... i mean... wtf? You have to tell it "notls" and then you are restricted to only a "localhost" or 127.0.0.1 configuration. Any 0.0.0.0 and you get a nice "F-U Buddy" from the system messages. I've looked high and low for anything that makes sense. I'm baffled. Have I just been looking in the wrong place?
Just lots of this now: 2016 http: TLS handshake error from 127.0.0.1:46523: tls: oversized record received with length 21536 2016 http: TLS handshake error from 127.0.0.1:46524: tls: oversized record received with length 21536
I will do this from now on for everyone https://forum.decred.org/search/21775/?q=TLS+handshake+error+from+127.0.0.1&o=relevance&c[node]=24
@Grendel25, the no tls options were for Windows only during the first few releases of the decred software. If you are running the latest version, you don't have to disable tls on Windows. Try those files with your setup again. I'm unsure if you are trying to pool your multiple computers together just by yourself (for a joint-solo mining setup, if you will), and somebody may have to correct me if I'm wrong here, but this setup below will have each one of your computers solo mining and sending funds into a single wallet: You should only need one wallet running (dcrwallet.exe). Assuming you have your wallet setup already (and dcrwallet.exe is running), generate a new address by using the command: Code: dcrctl -u user -P password --wallet getnewaddress ...where user and password are the same credentials you used when starting dcrd. Copy this newly generated address and relaunch dcrd using the command: Code: dcrd -u user -P password --miningaddr DsYouRNewAddResSHeRe Run dcrd using the above command with the same mining address on each one of your machines that you wish to solo mine on, give them a few minutes to get started and sync to the blockchain, then start cgminer with: Code: cgminer --blake256 -o https://127.0.0.1:9109 -u user -p password Note that user and password are the same in each of the three commands. Also note that the decred utilities use a capital P for the password flag while cgminer uses a lower case p. EDIT: After you are all setup, you don't need to run dcrwallet anymore. dcrwallet only needs to be ran so you can generate a new address. To solo mine, you only need dcrd running with your mining address and cgminer running on localhost.
Yes, I searched that and many similar variants. And still, I was still unable to mine on anything but one miner. Believe me, I'm a search-a-holic and was up until 8AM trying to understand. As so many others have said... they really didn't make this easy. I'm looking at David's more helpful comment and will reply to him. But, thanks for the reply and suggesting a search. Sorry if I laugh a little to myself though.
First, thank you for your reply. I'm pretty sure I was on .5 in the end but on .4 version at first. I'll start from scratch again. Wow, you have opened my eyes (seriously, not sarcastic and thank you again) "...sending funds into a single wallet..." and "...you don't need to run dcrwallet anymore..." after setup and mining. This 'sounds' so different 'to me' but probably just because I'm so spoiled on running a GUI wallet that combines the dcrd function with the wallet and then I just tell remote nodes to send whatever they mine to a particular address. A similar thing is happening here as what I'm used to but instead of sending to a remote node as iterated in the miner config I'm now just telling the remote mining node (in the mining config) to send work completed to the localhost which has dcrd running with the configured/desired address. Your explanation is way better than the word-vomit I put forth but I just wanted to put it in other words to hopefully illustrate that I'm picking up what you're putting down, Charlie Brown. Awesome stuff and thanks again. Edit: On second-thought, I'll just run a checkversion on what I have now. But not immediately. I need to replenish my constitution before I embark again. But I think I'll get it now that you taught me this fundamental configuration difference.
@Grendel25, fantastic! It seems like you've gotten it down. And yes, the separation of the wallet from the blockchain integration was neccesary for Decred's PoA basis. To help clarify a little more, and this is basically what you said in summary of my post: dcrd is the "portal" into the Decred blockchain. By pointing your miner at the same address/port that dcrd is running on (localhost:9109), your miner has access to everything it needs to start calculating the right nonce, through dcrd. Dcrwallet is essentially the same. It connects to the Decred network through dcrd, by first going to the IP address/port that dcrd is running on (again, localhost:9109). Dcrctl is used to interface and control your wallet, stake mining, transactions, and other various decred functions. If you had to place an order of importance on the three utilities (or an order of which to launch first, it should be) 1. dcrd 2. dcrwallet 3. dcrctl functions. You cannot use #2 without using #1, and you cannot use #3 without using #2 (and #1 by nature of the dependencies each one has). You can also configure dcrd to listen on a public/private IP address instead of localhost, though I don't personally see a benefit of doing so compared to a dcrd instance on every machine. Be careful about bringing your wallet online in more than 1 place though. If you do have multiple wallets online at one time, treat one as a "main" wallet and only generate transactions from your "main" wallet. If you generate transactions from different wallets with the same seed, they will get out of sync.
David, good news. I got things up and running on my second computer. Thank you for your assistance. We'll see how it goes, I hope to send some decred your way sometime. The only thing we didn't really talk about that was interesting and a little painful was the rpc.cert stuff. Of course, that was required in the miner setup with the --cert "your-path-to-rpc.cert". That was easy to sort out on my main computer where my wallet is because I just threw the .cert file in the same location as my miner so I didn't have to put in the full path info. But for some reason it wanted the full path to the actual cert location when I did it on the remote computer. I haven't really tested or measured performance yet. I'm hoping there's something in the command line that would let me see my personal hash rate on various nodes but we'll see how that goes. For now, I'm just happy that it appears to be working and we sorted out the configuration stuff. Oh yeah, I probably should have mentioned I'm using ccminer. I'll go ahead and post my config info for others to peak at. Actually, if anyone sees anything weird in my conf stuff below please let me know. Seems to be working though. Main computer: dcrctl.conf rpcuser=izlo rpcpassword=watch_out_some_special_characters_seem_to_cause_problems dcrd.conf rpcuser=thiscoolguy rpcpass=But_Not_ALL_Secial_Characters_WATCHOUT_FOR_THAT miningaddr=DDD_C0d3_4_u_h89if9dfud2m9DDDDDDD Decred_GETWORK.bat timeout 5 :loop ccminer.exe --cert "rpc.cert" -t 2 -i 25 -a Decred -o https://127.0.0.1:9109 -u thiscoolguy -p WATCH-out-secial-chars-guyz! timeout 30 /NOBREAK >nul goto loop dcrwallet.conf username=thiscoolguy password=So_scary_of_special_chars dcrdusername=thatcoolguy dcrdpassword=o-my-goose-special-forces-characters-FTW Secondary computer (no wallet) dcrd.conf rpcuser=thiscoolguy rpcpass=But_Not_ALL_Secial_Characters_WATCHOUT_FOR_THAT miningaddr=C0d3_4_u_h89if9dfud2m9DDDDDDD Decred_GETWORK.bat timeout 5 :loop ccminer.exe --cert "c:\full-path\to\rpc.cert" -t 2 -i 25 -a Decred -o https://127.0.0.1:9109 -u thiscoolguy -p WATCH-out-secial-chars-guyz! timeout 30 /NOBREAK >nul goto loop I think that's about it. I can't actually get into the second computer right now... kids are playing on it But I think the configs are right. I'll double check later.
That's great! You are welcome. I enjoy helping where I can. PM me if you'd like to send some DCR and I'll give you an address . But if not, I'll still be here to help! I actually don't use the rpc.cert. It will help secure your connection, but if you're running all instances on localhost I don't see a point to it! (unless there's something else I don't know - and I'm totally open to being corrected). I would use the rpc.cert if I was running dcrd on a "main hub" and then having my miners connect back to the main hub for their individual connection to the blockchain... But for what you're doing, you have dcrd and a miner running on each system, so I think you should be fine. Nobody else can connect to your localhost unless they have access to your computer, which in that situation, you have even bigger problems! I want to ask you about your term "remote" computer. To be totally clear, each one of your computers can be considered a main miner. The setup I described in the last couple of posts do NOT pool their resources together. They are each mining by themselves against all others on the network, trying to get lucky and find the right solution for each block before anyone else does. In a way, they are fighting against each other. In the event that one computer finds a solution, it will direct the block reward to a single address.. that is the only thing your computers are sharing. Unless you have several hundred Gigahash/s, I would definitely recommend joining a pool so you can pool all your resources together. Since you have everything setup, it should be an easy change. (the Decred pools might have issues with ccminer, FYI) Also, can I ask why you are using ccminer instead of cgminer? Not that you're wrong - I'm just curious.
By remote computer I just mean secondary, not my main computer but some computer I setup for one of my kids. I'll give this solo thing a go for a few more days and then probably cave in to a pool. I guess it just depends on if I get lucky. I know with the last coin I was mining (Joincoin) solo mining has been really good. Depending on how this goes I may just jump back to Joincoin. I just haven't got back into using cgminer. When I used cgminer I don't think they had cuda support and I've made the change from about 10 AMD 280X's to 8 750Ti's. I'm thinking of building back up some dedicated mining rigs that aren't daily use computers but that's only if I can earn some coin to buy stuff with. New GPUs coming out could be interesting. For now, I'll see what my 750Ti's can do.
Ok, gotcha! Sounds good. I hear the 750Ti's are very power efficient.. and I too am looking forward to the new cards coming out this year. It should be interesting. Good luck!
I think i am getting lazy Many more people are now available for helping & much better than me. Its time to get back into lurk mode for me i guess.
Hi, just figured I'd update. I got ridiculously lucky in my first few hours of mining. I'm assuming it had something to do with the suprnova outages so maybe my chances were better at that time. So yeah, I mined two blocks with my little 4 Gh/s rigs... well two running at 1.5 Gh/s and one smaller rig at 1 Gh/s. After that, I gave it two more days and got nothing so I got too nervous and just switched over to pool mining. Seems to be going well on the pool. At least it's consistent. But 38 coins (which is about a week's worth of mining for me) in just about 3-days of fiddling with solo mining was pretty cool. At least I have the solo configs ready to go if the pool gets ddos'd again.
I have just the opposite (lucky but unlucky) experience. I mined 18 blocks (326 DCR) on a pool, received only 176 DCR- switched pools a few days ago and have already found 5 blocks (96 DCR) and received only 26 DCR. I am an incredibly lucky miner mining on pools. According to my hashrate of ~6.5GH/sec I think I should have found 6500/3500000 or .18% of 7700 blocks - 14 blocks (266 DCR) (nearly exactly what I have been paid!). I have found 23. I would switch but know that the laws of large numbers would start catching up with me right then! (BTW, this means dcr.POOL.MN and coinmine.PL are both fair pools.) I was just being suspicious by switching.
I am having a hard time believing my lucky/unlucky pool mining. Now, at coinmine, I have found 8 blocks (133 coins) and been paid only 50DCR (probably perfectly fair). This is the second pool at which I am finding blocks far faster than my ~6.5-7GH/sec should be. Anyone know how this can be? I am earning (for pools) roughly twice what my hashrate should for over a month now. I'd feel better if some had the same story in reverse (e.g. no black but paid 50DCR). Doesn't the law of large numbers make this wildly improbable?