[ANN][GRE] GreenCoin | On Bittrex now!

[IMJim]

No luck so far.......does this look correct for my config?  Not sure on the rpcallwip line if I have that right.

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1,192.168.1.122
rpcport=21036
server=1
daemon=1
listen=1
addnode=107.178.113.62

rpcallowip should just be 127.0.0.1 (or localhost)

So where do I then put in the IP address for the PI controller?  Just tried the following as well and did not work for me.......the 192.168.1.122 is my PI controller's ip addy.

[Freenhult]

No luck so far.......does this look correct for my config?  Not sure on the rpcallwip line if I have that right.

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1,192.168.1.122
rpcport=21036
server=1
daemon=1
listen=1
addnode=107.178.113.62

make another line of rpcallowip=192.168.1.122
Your wallet on your computer has to be allowed through the firewall on the computer as WELL as the router. I use DMZ on the router to my computer IP to facilitate this.

[IMJim]

No luck so far.......does this look correct for my config?  Not sure on the rpcallwip line if I have that right.

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1,192.168.1.122
rpcport=21036
server=1
daemon=1
listen=1
addnode=107.178.113.62

make another line of rpcallowip=192.168.1.122
Your wallet on your computer has to be allowed through the firewall on the computer as WELL as the router. I use DMZ on the router to my computer IP to facilitate this.

Hey thanks again very much for trying to help with this bud, really do appreciate it!  My config file now reads.......

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.1.122
rpcport=21036
server=1
daemon=1
listen=1
addnode=107.178.113.62

In Hashra Controlla I have the following settings.......

http://127.0.0.1:21036
username
password

Pretty sure I allowed the wallet through my Firewall when it started, not sure how to do the other but will see if I can figure it out:-)

[Freenhult]

You have the same problem I did! The Pi's need to be set to the COMPUTER IP. Not 127.0.0.1!

[ncsupanda]

You have the same problem I did! The Pi's need to be set to the COMPUTER IP. Not 127.0.0.1!

For the record, 127.0.0.1 refers to your localhost. Think of it as a computers internal IP - you need the external.

[IMJim]

You have the same problem I did! The Pi's need to be set to the COMPUTER IP. Not 127.0.0.1!

This would be the IP address I get when I go to Google and type in "whats my ip" then correct.......the IP assigned to us by our Internet provider correct, not one for my actual computer right?  Or is it the IP my router assigned to the PC the wallet is on?

[ncsupanda]

GreenCoin on Coinader Exhange :

https://www.coinader.com/?cur=GRE&ccur=BTC

Awesome! Pools are being fixed Info on the way.

[Freenhult]

You have the same problem I did! The Pi's need to be set to the COMPUTER IP. Not 127.0.0.1!

This would be the IP address I get when I go to Google and type in "whats my ip" then correct.......the IP assigned to us by our Internet provider correct, not one for my actual computer right?  Or is it the IP my router assigned to the PC the wallet is on?

The Pi's have to be connected to the router assigned IP on your wallet computer.

For example my Pi's are 192.168.1.106 and my computer is 1.102. So the rpcallowip on my computer is 192.168.1.106 because I want the Pi to talk tot he wallet. IN the Pi config for mining the IP is 192.168.1.102 because I want the Pi to talk to the wallet.

Edit: Also just be slow in adding all of your hash. You're likly to 51% the network if you dump it all...

[IMJim]

You have the same problem I did! The Pi's need to be set to the COMPUTER IP. Not 127.0.0.1!

This would be the IP address I get when I go to Google and type in "whats my ip" then correct.......the IP assigned to us by our Internet provider correct, not one for my actual computer right?  Or is it the IP my router assigned to the PC the wallet is on?

The Pi's have to be connected to the router assigned IP on your wallet computer.

For example my Pi's are 192.168.1.106 and my computer is 1.102. So the rpcallowip on my computer is 192.168.1.106 because I want the Pi to talk tot he wallet. IN the Pi config for mining the IP is 192.168.1.102 because I want the Pi to talk to the wallet.

Edit: Also just be slow in adding all of your hash. You're likly to 51% the network if you dump it all...

Once again.......THANK YOU.  Had something working with 1 of my sets of 10 (3.5 mh/s approximate), I know something worked cause I had a dose of coins roll in, looking at the pools list in Hashra, it looks like it worked for s few seconds then kicked over to another pool.  Will keep playing with it, am determined to learn this now:-)

Thanks for the warning on the hash, the dev warned me about that as well......thankfully you guys did as I would not have known any better and I would have HATED to be the one to screw something up here for others!

[IMJim]

Oh, I can't let this go.....am getting somewhere just not sure where yet.  When I save the info in Hashra and save and re-boot, it seems it mines through the wallet just long enough to clear a block and then moves to a different pool.  One would think everything is setup correctly being that is can mine for a few seconds or more......scratching my head on this one!

[Freenhult]

Check the pool management strategy. IT might be on round robin or something; CGMiner and BFGMiner all had something. I'm unfamiliar with your setup but that might be in. Also you could just delete out your current list of pools if you want to hash.

Since I have 5mh on the network I think you can put 5-6 out there safely and that would keep me from getting all the blocks (Or most). Until the pool picks up more steam we'll have to solo-mine for safety. If you see a lot of rejects then we know the chain is getting forked so throw more at it in a pool.

[Freenhult]

Heading to bed, I hope you work it out friend! I should be up in 8-10 hours...

[IMJim]

Check the pool management strategy. IT might be on round robin or something; CGMiner and BFGMiner all had something. I'm unfamiliar with your setup but that might be in. Also you could just delete out your current list of pools if you want to hash.

Since I have 5mh on the network I think you can put 5-6 out there safely and that would keep me from getting all the blocks (Or most). Until the pool picks up more steam we'll have to solo-mine for safety. If you see a lot of rejects then we know the chain is getting forked so throw more at it in a pool.

You know, I am thinking I can only run one set of 10.....I think every time I tried to connect a second set to solo mine, it kicked em both off.  It seems to me that although Hashra Controlla says it is hashing one of the pools, it looks like it is in fact solo mining as coins are trickling in.  I did think to add the second controller's IP to the config file, so not sure yet what is going on.

How do I check for rejects and what the wallet is actually doing or mining?

Listen man, I VERY much appreciate your help......would not mind at all kicking ya some of me new coins if you want to shoot me your addy!!  With all the jerks you run into on this forum, it is very nice to run into some cool peeps here and there:-)

[ncsupanda]

Check the pool management strategy. IT might be on round robin or something; CGMiner and BFGMiner all had something. I'm unfamiliar with your setup but that might be in. Also you could just delete out your current list of pools if you want to hash.

Since I have 5mh on the network I think you can put 5-6 out there safely and that would keep me from getting all the blocks (Or most). Until the pool picks up more steam we'll have to solo-mine for safety. If you see a lot of rejects then we know the chain is getting forked so throw more at it in a pool.

You know, I am thinking I can only run one set of 10.....I think every time I tried to connect a second set to solo mine, it kicked em both off.  It seems to me that although Hashra Controlla says it is hashing one of the pools, it looks like it is in fact solo mining as coins are trickling in.  I did think to add the second controller's IP to the config file, so not sure yet what is going on.

How do I check for rejects and what the wallet is actually doing or mining?

Listen man, I VERY much appreciate your help......would not mind at all kicking ya some of me new coins if you want to shoot me your addy!!  With all the jerks you run into on this forum, it is very nice to run into some cool peeps here and there:-)

What OS are you using? You should have a debug.log if you're using Windows QT.

[ncsupanda]

Headed to sleep now - I'll wake up every 30ish minutes to check and make sure all is going well.

Pool operators are being contacted, and all seems good for now.

[Freenhult]

Check the pool management strategy. IT might be on round robin or something; CGMiner and BFGMiner all had something. I'm unfamiliar with your setup but that might be in. Also you could just delete out your current list of pools if you want to hash.

Since I have 5mh on the network I think you can put 5-6 out there safely and that would keep me from getting all the blocks (Or most). Until the pool picks up more steam we'll have to solo-mine for safety. If you see a lot of rejects then we know the chain is getting forked so throw more at it in a pool.

You know, I am thinking I can only run one set of 10.....I think every time I tried to connect a second set to solo mine, it kicked em both off.  It seems to me that although Hashra Controlla says it is hashing one of the pools, it looks like it is in fact solo mining as coins are trickling in.  I did think to add the second controller's IP to the config file, so not sure yet what is going on.

How do I check for rejects and what the wallet is actually doing or mining?

Listen man, I VERY much appreciate your help......would not mind at all kicking ya some of me new coins if you want to shoot me your addy!!  With all the jerks you run into on this forum, it is very nice to run into some cool peeps here and there:-)

You need to have a new line to the .conf file for every controller, didnt realize you had more than one. You really cant check hashrate in solo mining unless the mining program shows you. You only submit shares that are blocks so its really quiet. If your wallet is generating coins then you are good. 10mh s should block at least once per minute...

[IMJim]

Check the pool management strategy. IT might be on round robin or something; CGMiner and BFGMiner all had something. I'm unfamiliar with your setup but that might be in. Also you could just delete out your current list of pools if you want to hash.

Since I have 5mh on the network I think you can put 5-6 out there safely and that would keep me from getting all the blocks (Or most). Until the pool picks up more steam we'll have to solo-mine for safety. If you see a lot of rejects then we know the chain is getting forked so throw more at it in a pool.

You know, I am thinking I can only run one set of 10.....I think every time I tried to connect a second set to solo mine, it kicked em both off.  It seems to me that although Hashra Controlla says it is hashing one of the pools, it looks like it is in fact solo mining as coins are trickling in.  I did think to add the second controller's IP to the config file, so not sure yet what is going on.

How do I check for rejects and what the wallet is actually doing or mining?

Listen man, I VERY much appreciate your help......would not mind at all kicking ya some of me new coins if you want to shoot me your addy!!  With all the jerks you run into on this forum, it is very nice to run into some cool peeps here and there:-)

You need to have a new line to the .conf file for every controller, didnt realize you had more than one. You really cant check hashrate in solo mining unless the mining program shows you. You only submit shares that are blocks so its really quiet. If your wallet is generating coins then you are good. 10mh s should block at least once per minute...

Cool man, am still playing around with things.  Is hard as my software is showing it not working the wallet but another pool, when I know it is working.  Only looking to run 3-6 mh/s on solo and 3 on the pool for now, being a bit new to this and hearing the concerns of forking, I don't want to hurt anything or cause probs for everyone so playing it safe till I can spread me hashes around.  Not like my miners don't have other work they can be doing in the mean time:-)

I did try to get a second one working for the experience but was unsuccessful as it seems, I did think to add the extra line for that controller's IP in the config though.

Learned something new tonight thanks to you!

[ncsupanda]

Added:

http://explorer.cryptoblox.com/chain/GreenCoin
http://www.cryptoblox.com/faucets/GreenCoin/

Both are up and functioning

[FalconCrypto]

No luck so far.......does this look correct for my config?  Not sure on the rpcallwip line if I have that right.

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1,192.168.1.122
rpcport=21036
server=1
daemon=1
listen=1
addnode=107.178.113.62

make another line of rpcallowip=192.168.1.122
Your wallet on your computer has to be allowed through the firewall on the computer as WELL as the router. I use DMZ on the router to my computer IP to facilitate this.

Hey thanks again very much for trying to help with this bud, really do appreciate it!  My config file now reads.......

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.1.122
rpcport=21036
server=1
daemon=1
listen=1
addnode=107.178.113.62

In Hashra Controlla I have the following settings.......

http://127.0.0.1:21036
username
password

Pretty sure I allowed the wallet through my Firewall when it started, not sure how to do the other but will see if I can figure it out:-)

The conf file should be coin.conf and not greencoin.conf

[Freenhult]

Were you able to get more than 1 controller connecting IMJim?