Hi @Patrik. Thanks for including the latest version of gminer!. I had been using 1.18 manually. Given the somewhat odd way that gminer accepts parameters, I just created a pool for Leafpool and left everything blank except us.leafpool.com. Then configured each managed miner and passed everything through command line:
--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/myname@yahoo.com
I can't seem to get a "standard config" working with the new gminer. I would think I could pull port and put that in the pool definition as standard ":3333", and put wallet address there. On each miner profile then add worker name/email.
for some reason it wont start under that configuration. It attempts to start the miner but gets a connection timeout on us.leafpool.com:3333. I can just leave it manual for now but would like to move to using the standard download.
I there anything unique to the gminer setup other than what I outlined above?
Thanks
I apologize, I did everything in a standard way, but I do not know how to post images of screenshots, please follow my links, everything is shown there. Thank.
Bump for you.... and your images looks like not supported.
Those appear to just be screenshots of the working miner. I was looking for specifics on the configuration. Thanks though.
When configuring like @baf28 suggested, Awesome Miner should produce a command line similar to what you are looking for. You can use the Diagnostics button to verify that.
What are the configuration specifics you are looking for here? If I enter your pool URL, worker and add the ssl-flag, Gminer stats mining just fine where Awesome Miner produced the following:
miner.exe --ssl 1 -a 150_5 -s beam-us.leafpool.com -n 3333 -u 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/myname@yahoo.com -p x --pers auto -w 0 --api 4041