Author

Topic: Problems when solomine with home rigs and remote rigs together.Need help! (Read 661 times)

legendary
Activity: 1904
Merit: 1003
If there is a lot of rigs you have to set: rpcthreads=150 or more in config file.
member
Activity: 117
Merit: 10
Who knows the quickest  way to set up a pool with windows wallet.Because solo only works several minutes right after launching.
Example for vertcoin here:
http://coingolem.com/how-to-setup-your-own-p2pool-node-windows-212/
sr. member
Activity: 392
Merit: 250
Look here: https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File
This option:
 # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 #rpcallowip=10.1.1.34
 #rpcallowip=192.168.1.*
And check other options, maybe they will help you.
Here is the config what I am using for months.Works perfectly on local network
rpcuser=user
rpcpassword=pass
daemon=1
server=1
listen=1
gen=0
connection=100
rpcport=17516
maxconnections=100
rpcallowip=*

But it is not working for remote solo...

And here is the info when I press P I


Maybe the final solution is to set up a private pool?

Who knows the quickest  way to set up a pool with windows wallet.Because solo only works several minutes right after launching.

member
Activity: 117
Merit: 10
Look here: https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File
This option:
 # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character).
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 #rpcallowip=10.1.1.34
 #rpcallowip=192.168.1.*
And check other options, maybe they will help you.
sr. member
Activity: 392
Merit: 250
Can you show your pool stats via P button in sgminer? I think they are dead. Is it works fine when server on 127.0.0.1(local machine in other words)?
Does he have white static IP? Looks like network configure issue. May be your friend connected to the internet with NAT, in this case he should open ports, just like for torrent.
Yes.The rigs in my friend's intranet both solomine perfectly as mining on pool.He is using a router and I have set up port forward properly.Otherwise,the sgminer of my home rig can not connect to it as soon as I started sgminer.
member
Activity: 117
Merit: 10
Can you show your pool stats via P button in sgminer? I think they are dead. Is it works fine when server on 127.0.0.1(local machine in other words)?
Does he have white static IP? Looks like network configure issue. May be your friend connected to the internet with NAT, in this case he should open ports, just like for torrent.
sr. member
Activity: 392
Merit: 250
I rented my friend's rigs.He has public ip address but I don't.I installed the wallet on one of his rig and set up the conf for solomining. There is no problem soloming in his intranet.But when my home rigs connect to his ip address,things went wrong! Sgminer is not showing the hashrate as it mines in pool nor solomine in my intranet.Judging by the tempetures,my videocards may not be fully hashing.Look at this pic.



When hashing X13,these 270xs normally give me 1.7m per card.But three of them are not showing the right number in this case! My another 280xs home rig encounter the same problem!
Code:
{
"pools" : [
{
"name" : "solo",
"url" : "http://192.192.192.192:17516",
"user" : "user",
"pass" : "pass",
"pool-priority" : "0"
}
],
I think it is kind of the network protocol problem.
Jump to: