Well I’d tried working through your suggestions, and I did get further ahead, but it is still showing as dead.
When I log into my router, and check the dhcp client table, both the l3+ and computer I am wanting to use as a server show up there. The ip’s of both of them havent changed in days/weeks, so I’m not sure if I need to set them as static ip’s…if you think that is necessary, I will work on that for a while tomorrow and see if that doesn’t solve the problem.
Initially, I did have the .conf wrong, because I failed to set the save as to all files, so it was saving it as .conf.txt which of course won’t work.
When I first tried starting the wallet with -server, windows wouldn’t allow it claiming that I needed a stronger password (I only had the X), so Windows gave me a big string to use as password, and I inputted that into the .conf file and also the l3+ password area. rpcuser and rpcpassword are the user and password sections in the .conf file.
You mention to “one other thing to make sure of (since you are trying to mine solo) is make sure that your router is allowing incoming connections to your external ip address” not sure on the reasoning behind this as both the l3+ and computer I am using to mine on are on the same home network. 192.168.1.136 (miner) and 192.168.1.138 (computer/server).
When I did run netsat -a | find “LISTENING” on the computer/server it did show the 0.0.0.0:9333 and 192.168.1.138:139 as being listened to…although it did not show any sign of the 192.168.1.136 (miner local ip) as being listened to…perhaps this would be resolved if I set them both up as static ip addresses?
I was able to start the altcoin qt with altcoin-qt.exe -server -disablewallet -addnode 192.168.1.138 without any problems other than the miner showing that ip as dead ie not mining
Hi I have always been able to solo mine before, there is nothing wrong with my config. It is something abot l3 miner stopping it. The one solution is a a stratum proxy on a spare pc
Create a receiving address in the wallet and make sure the wallet is synced…this will use DNS to register that address to your external ip address…
now… there should be a solo configuration on the l3 but if not then you’ll have to set it up as a proxy…if there is a solo configuration on the l3 then you don’t need to run the wallet on a separate machine and just need to set the l3 pointing to your wallet address instead of an ip address…
then when you run you wallet on the separate machine…DNS will connect to the ip address of the receiving address
I do know that you will need to set your miner to -listen somehow…when using cgminer I know you can use the -listen flag so running bfgminer as a proxy server should do the trick if there is no way to set the l3 to listen in the gui that you ssh to on the l3…this is usually how a pool is configured though
mining solo with a miner that is connected using Ethernet is either a proxy connection or a longpolling connection that setup like a “personal pool” or the miner will have a solo configuration on its GUI…so…
if there is no solo configuration on the miner
try using bfgminer as a proxy server and pointing that to your wallet server and then pointing the l3 at bfgminer…you would have to run bfgminer on a separate device or you will need dhcp on your machine that is running both altcoin and the proxy server at the same time…
with dchp on your machine that is running the wallet and bfgminer it should give the first server that connects the address of 127.0.0.1 and the second one as 127.0.1.1 or 127.0.0.2
if it is running on 0.0.0.0:93333 you do need to set it to 127.0.0.1 in order for local intranet address(programs running on the same machine) to be able to connect to it…probably need it that way for local network connections to longpolling / proxy as well…
sorry for the edits but anyway I do know that every-time you click the “Request payment button” and your wallet creates a new address that DNS registers that address with the external ip address…this is why I said you need to make sure your router is allowing incoming connections to the external ip…
otherwise you have to set it up like a personal pool using a proxy server for the node that is running the solo miner
Thanks for your response, I have tried different stratum proxy software. I can get it running, it is the configuration I cannot get my head around enough to get it working. I have solo mined before direct to many different wallets using orher equipment, these l3’s are stubborn
its because your miner’s software has no solo configuration…like bfgminer does
if you download bfgminer and run it as solo and then point your miner towards bfgminer as a proxy it will work…
if your mining software does not support solo then this may be your only option
stratum software isn’t setup for solo mining…but bfgminer is…stratum is used for pools and accepts connections to the exterior ip address…you are trying to mine locally…which is why stratum software wont work for you
are you sure your running the script right?..you do know that for solo you cant point the miner to an ip address right? you have to point the miner towards the “coinbase payout address” and this is true for all solo mining configurations
the command is -o (receiving Litecoin address you are mining to) (then arguments such as chip options and so on)
if you point a miner towards an ip address that is pool mining whether you setup your own personal pool or connect to one externally…
look like to me here that you best bet is to run bfgminer with a solo configuration and make sure you start it using command prompt with the -http-port 3333 flag…this will make bfgminer your proxy server for your wallet…then point your miner at the static ip of the device you are running bfgminer on
so the command would be bfgminer.exe -scrypt -o http://(static ip of the machine running bfgminer:9333) -http-port 3333
do not set chip counts or devices in bfgminer then ssh to your miner and point it at bfgminer at the same static ip pointing it at 3333
you cannot use the same port to call out as you do to listen
here’s an example I know works every time…say I have a litecoin wallet on my desktop here and I want o mine solo to it using a miner that has an Ethernet connection going to it and a GUI on that controller…(such as your l3)
like I said the starting scripts for solo and pool mining configurations are different…
from command prompt in windows (for linux change .exe to ./ before program name)
I start my wallet…litecoin.exe --server --addnode 192.168.1.110
then I start bfgminer from the same machine like this:
bfgminer.exe --scrypt -coinbase-addr (litecoinaddress) -http-port 3333
now say I set my static ip for the machine that is running both of these programs to 192.168.1.110
I ssh to the miner and point the miner using http not stratum because stratum is not used for local connections to :
-scrypt http://192.168.1.110:3333 -u (user name in your config file) -p (password in the config file) (chips count and frequency options)
done
Ok, I understand the other instructions, but I’m not sure about the above instructions related to bfgminer.exe, as I used primarily cgminer a few years ago, and am now using the L3+.
“bfgminer.exe --scrypt” I get
“-coinbase-addr (litecoinaddress)” not sure about, do I need to actually use “-coinbase-addr (my altcoin address)”
“-http-port 3333” is that the actual command? or am I to put an ip address in there somewhere? And if that is the port, what am I using in the conf file of the altcoin I’m wanting to mine rpcport=3334
port=3333?
you can use cgminer the same way…
you can use any pot you want your proxy server to listen on (except 9333 because you are listening to your wallet using that port) as long as it is no 443 or 80 along with a few others that are low numbers and used for things like email servers and such…most pool choose 3333 so that’s why I chose that
…litecoin listens on 9333 to the network so you just need a different port for your miner to connect to the node…
http-port is the command for bfgminer…
cgminer users has a -listen flag…
start cgminer with --help flag to get the options for it…I recommend bfgminer because it does proxy…I dont think cgminer will do that but it does have a -listen flag option
here is the command for solo cgminer using dmaxl version:
cgminer.exe --scrypt -btc-address (litecoinaddress) --listen 3333
bfgminer supports solo and not all cgminer versions have a solo option…I know dmaxl’s version of cgminer does solo…
make sure the version of cgminer you are using has solo support
then ssh to your miner and point it at the static ip that is running cgminer
one more thing…make sure your .conf file matches the settings you are using…keep api-port at 9333 for litecoin and since we used 3333 above then make sure you have port -3333 in there…should look like this:
server=1
rpcallowip=127.0.0.1
rpcport=9333
port=3333
gen=1
one more thing delete rpc user and password so it looks like above…unless you are using vpn or a stats web page this is not needed and make sure that your .conf file is saved as litecoin.conf …otherwise you have to specify thename of the .conf file with the -conf flag when starting form command prompt
then start the wallet with flags to: -server and -add-node (static-ip of machine running wallet)
form command prompt start litecoin-qt.exe --help and cgminer.exe --help and make sure you are using all your options correctly
remember that you will not see and “accepted shares” when mining solo…
you will only get a result if you find a block…as long as you see the stats at the top of cgminer/bfgminer showing connected and hashing with the current difficulty of 1.2 million then you are solo mining
I really do appreciate you taking the time to help however, i cant help but feel like you are working on theory alone and ill be honest. it just dosnt always work like that.
Have you used a l3+ to solo mine to a litecoin wallet?
scrypt asics are stratum. stratum does not require servers to rember what work they gave the miner thus reducing overhead on serverside. the problem with that is that litecoin cleints still use the getwork proto. There really does not seem to be a way to convert stratum into getwork.
Im not sure how accurate stankonia story is that they used to solo mine using their knc titan. it is the exact same issue as the l3+ has.
stankonia could you help me understand how you solo mined using your knc titan?
i have emailed bitmain quite a few times trying to get them to tell me how i can use their miner to solo mine and they refuse to help in any way saying its impossible and that i should mine to a pool. i find it a bit rediculous. i really would like to find a working solution too. One that i can use on a windows box and not have to setup a pool on a linux box. I am however, sick of people giving advice on therory. it just dosnt work like that.
I am not giving advice on theory…I know way too damn much about networking for that…
I may not have an L3 but I do know how to connect a miner to a wallet solo using ethernet and usb and both are two different methods…your l3 should have a way to run solo without a proxy server anyway…most all antminer products do…
If you haven’t used a l3+ miner and solo mined to a client with it then yes, you are working on theory only.
I just saying its not so straight forward as you would hope these days given my points about stratum being a completely different protocol to what the client understands.
You advice on using the “-coinbase-addr” for example is a copy paste of instructions used that are now completely redundant in the mining world, in regards to solo mining.
Personally i only give advice on something i have actually specifically used or done using the hardware and software the op is using. You just cant guarantee these days that its universal because now a days, it just isnt. Years ago, bitcoin software and hardware and the techniques to get it going were all pretty well the same!
Can i just say I have posted requests for help in lots of different places we have a good topic going, I had 5 titan miners mining the most profitable and lowest difficulty local wallets (gamecredits, verge to name a few) and made a lot of money. Titans used bfg miner which suppots stratum. Have a look at your address input on you l3+ if you have one? You will see the miner works on getworks it relys on a pool stratum to convert it. We have a working progess on this forum at the moment thanks to positive responses. Its a shame some people find the need to ruffle feathers. My interest in this subject is in the stratum issue. The only way is to experiment with config on a stratum server this is abit beyond me but even someone giving any constructive input will help me. I can use the error log to see me getting closer to a goal no body has achieved yet.! Just getting back to bitcoin mining back in the day, I remember using a local stratum server configured by slush and I pointed four blades at it, it then converted getwork to stratum. This is what i want to achieve. With l3+ to a local wallet not necessarily a ltc wallet, although with 7x l3 miners it probably would not be a bad idea.
Ok so ive ruffled feathers, i believe that giving you advice on theory is not helping. I 100% don’t believe you have used a knc titan to mine to a wallet. I asked you how you did it and you still haven’t answered fully. I encourage you to correct that so i can eat my hat and we can move on.
The Titan and l3+ miner on the software side is as you said, stratum only and the wallets are all getwork, not stratum. If you found a solution for that and mine on the titan then what was that solution?! Because if it wasn’t to do with modifying the software on the pi, the computer titan controller comes with then i 100% dont trust that you mined to a altcoin wallet that hasnt been modified to allow stratum protocol to directly communicate with it to solo on them.
I’m trying to tell the person who is trying to help you to rethink what is helping. A quick search of the Internet gives results where everyone is saying the same old crap. It does not work in this case, it is old directions furthermore, most of it is the wrong way around. We are trying to send stratum protocol to a node that dosnt understand it and the only tech out there so far converts getwork into stratum (slush stratum PROXY), not the other way around because its basically impossible to do unless you run a stratum server (you called what slush made a stratum server and that is incorrect. he made a stratum proxy that turned what the blades you had (sending getwork) into stratum so pools would understand them. Pools use stratum because they don’t need to remember what work they gave the miner, thus reducing overhead and they can take many more miners at once. Pools removed the ability to receive getwork and thus we needed slushs stratum PROXY not server.
Stratum server, Its what pools use as their back-end. Its what miners connect to and it feeds info to the brain which calculates the website ect ect. Basically its the engine that we need ported to work on windows, i can get it work on linux just fine. I can get one to run on its own to act like a proxy that you need on linux just fine. If thats all you need and you have a nix box then let me know ill help you through the process. What we need is one that accepts stratum from miners and converts it to getwork so the node can understand the work given to it. Personally i want a solution i can use on a windows box. So far i have to use a p2pool node to solo mine which isn’t terrible but i really would like a solution more direct.
If you want info on how to port a new coin to work on p2pool software to work on windows let me know and ill happily help as i know it 100% it works because its what i currently do to solo mine on a windows box using a asic that sends data in stratum.
I installed bfgminer, set miner and computer to keep same ip on network.
started my wallet…altcoin.exe --server --addnode 192.168.1.138 (the computer running the altcoin wallet)
I had to keep the rpcuser and rpc password, otherwise windows refuses to start the altcoin wallet with the above instructions.
next I tried the bfgminer.exe --scrypt -coinbase-addr (altcoin address) -http-port 3333
failed, unrecognized command
it accepted bfgminer --scrypt -coinbase-addr (altcoin address) -http-port 3333
but borked on -http-port 3333 as unrecognized command
did bfgminer --help
should be --http-port 3333
didn’t see any -coinbase-addr in the help file nor --coinbase-addr for that matter, so looks like that command has been depricated. Did see a note for command --coinbase-check-addr which refers to addresses included after pool seperated by ,
however since I am not inputing a pool with bfgminer, not sure how to include addresses after , [suppose I could do it at next stage when inputting “pool url” of 192.168.1.138]
tried starting it without wallet address, just bfgminer --scrypt --http-port 3333
bfgminer starts and asks for url, I input http://192.168.1.138
asks for user, I include the user from altcoin.conf that windows requires as noted above
asks for password, again, include from altcoin.conf
tells me no valid pool
tried again with inputting http://192.168.1.138:3333, followed by user, and password…same result no pool found
