Just an elaboration to @baf28's report of not seeing "View Details" -> "Profit switching" tab not being populated in 6.1.1 (he removed the post, and I had that with 6.1.0 as well), I just had that happening to myself and found that it was due to the following:
-> NBMiner (no algos enabled by default anymore)
-> NBMiner is (was) enabled in all affected miners' profit profiles
to resolve, I either had to
disable NBMiner from the profile
OR
enable an algo (Tensority for example) and add "tensority" to custom command line in Options -> Managed Software
I assume this might've happen with any managed software in similar to above circumstances.
Cheers,
Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 225. (Read 703148 times)
January 14, 2019, 08:09:21 PM
January 14, 2019, 08:10:58 AM
I have a problem.
I created 2 pools with the same settings: mininghub and mrr
When I select the mrr pool in the switch profile, an error occurs that the pool is not suitable.
And if you choose not mrr, then everything works.
What can be wrong?
https://i.ibb.co/0X3zhn5/2019-01-14-19-03-35.png
https://i.ibb.co/1z3qKtv/2019-01-14-19-04-04.png
https://i.ibb.co/frpn39Z/2019-01-14-19-08-11.png
I created 2 pools with the same settings: mininghub and mrr
When I select the mrr pool in the switch profile, an error occurs that the pool is not suitable.
And if you choose not mrr, then everything works.
What can be wrong?
https://i.ibb.co/0X3zhn5/2019-01-14-19-03-35.png
https://i.ibb.co/1z3qKtv/2019-01-14-19-04-04.png
https://i.ibb.co/frpn39Z/2019-01-14-19-08-11.png
January 14, 2019, 07:16:53 AM
Awesome Miner version 6.1.1
- Adjust the algorithm Equihash 144,5 to show up as ZHash to be consistent across all coin statistics providers
- Adjust the algorithm Equihash 144,5 to show up as ZHash to be consistent across all coin statistics providers
This is a bad decision. it was better to make calculators stick to the same algorithm or rewrite through the settings to the required algorithm.
Maybe another way would be to have Awesome Miner automatically change this on a per-coin level instead. The drawback would be that as soon as a new coin shows up on any of these algorithms, the mapping would be outdated. Doing it on an algorithm level is easier from that point of view.
It's however not a good idea to force all users to manually go to the settings and change the algorithms for a number of coins just because they are reported differently from the coin statistics sources. The goal must always be that things should work as good as possible out-of-the-box.
January 14, 2019, 07:11:35 AM
i mean in awesome miner settings cant see ...
http://prntscr.com/m6yd43
http://prntscr.com/m6ydkr
nbminer dual mining is not integrated?
Thanks for sharing the details. Awesome Miner doesn't support dual mining for NBminer yet. It's on the ToDo-list. http://prntscr.com/m6yd43
http://prntscr.com/m6ydkr
nbminer dual mining is not integrated?
January 14, 2019, 06:59:03 AM
Awesome Miner version 6.1.1
- Adjust the algorithm Equihash 144,5 to show up as ZHash to be consistent across all coin statistics providers
- Adjust the algorithm Equihash 144,5 to show up as ZHash to be consistent across all coin statistics providers
This is a bad decision. it was better to make calculators stick to the same algorithm or rewrite through the settings to the required algorithm.
January 14, 2019, 06:32:19 AM
i mean in awesome miner settings cant see ...
http://prntscr.com/m6yd43
http://prntscr.com/m6ydkr
nbminer dual mining is not integrated?
http://prntscr.com/m6yd43
http://prntscr.com/m6ydkr
nbminer dual mining is not integrated?
January 14, 2019, 05:48:04 AM
Awesome Miner version 6.1.1
Mining software
- BMiner 11.4.1
- SRBMiner 1.7.6
Corrections
- Make the settings for CUDA device order and power usage configurable in all editions of the software
- Adjust the algorithm Equihash 144,5 to show up as ZHash to be consistent across all coin statistics providers
Mining software
- BMiner 11.4.1
- SRBMiner 1.7.6
Corrections
- Make the settings for CUDA device order and power usage configurable in all editions of the software
- Adjust the algorithm Equihash 144,5 to show up as ZHash to be consistent across all coin statistics providers
January 14, 2019, 05:42:18 AM
hi patrike, for tensority cant see dual mining hashrate... how i can setup dual mining eth-btm?
For Bminer I've noticed that I get 0 for both hashrates every now and then for both the primary and dual hashrate. But I do get two readings most of the time.Can you send a screenshot and an API report (toolbar: Tools -> API Report) when you see this issue? Thanks!
January 14, 2019, 05:31:29 AM
Barely visible. Watch the capture, arrina are ZEL and BTZ de cointomine, and just below you can see a little ZAL of coinscalcutor
What I do not know if it is the cointomine api problem that calls the coins in another way internally, or some change in this latest version of today.
I have updated and just after it has happened. I have the 4 aggregators activated at the same time, Cointomine with premium API due to my donation.
I'll tell you if it can be fixed in some way.
This is basically the same issue and the same workaround can be applied. As the same coin can exists multiple times with different algorithms (for example Digibyte and a few more), Awesome Miner can list each combination of unique coin and algorithm.What I do not know if it is the cointomine api problem that calls the coins in another way internally, or some change in this latest version of today.
I have updated and just after it has happened. I have the 4 aggregators activated at the same time, Cointomine with premium API due to my donation.
I'll tell you if it can be fixed in some way.
In this case we have a few coins that are listed with both Equihash 144.5 (from CoinToMine) and ZHash (from WhatToMine/CoinCalculators?). Both will show up as Awesome Miner see they have different algorithms.
I will try to re-map some of these coins to the correct algorithms in Awesome Miner itself.
Edit: It looks like WhatToMine and CoinCalculators lists a few coins differently as well. XSG is one example - making it show up twice - one for each algorithm. Right now I'm a bit unsure which one is correct and this goes for a few coins.
There is a solution.
Options - Statistics Providers and Overridd coin algoritm Configure
Set ZEL to Zhash
Set BTCZ to Zhash
Then apply the changes and click the update button on the coins tab
perfect thank you very much, sometimes we do not remember all the options. I fixed it, so I'm grateful.
January 14, 2019, 03:53:10 AM
hi patrike, for tensority cant see dual mining hashrate... how i can setup dual mining eth-btm?
January 14, 2019, 03:46:04 AM
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/[email protected]
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
--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]
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.
https://yadi.sk/i/F2NsXSwb4PSgqA
https://yadi.sk/i/t3SwW5soDaC1AA
https://yadi.sk/i/us4ZpKaNXeseqA
Those appear to just be screenshots of the working miner. I was looking for specifics on the configuration. Thanks though.
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/[email protected] -p x --pers auto -w 0 --api 4041
January 14, 2019, 03:37:10 AM
Patrike,
Bit of a problem with exchange/volume filtering (sorry been away for the past few weeks, so didn't go through the posts thoroughly if it's been mentioned already).
Coins are grayed out in the following scenario when
-> Coin meets the minimum volume set in Options -> Statistics Providers
-> Exchange list in API is empty
in the below example is Espers (ESP), Statistics Providers Ordering (CC > WTM > CTM).
Use all exchanges (check), minimum exchange volume (0.002 BTC)
CMC's 24h volume matches the API of approx $196 USD
I know where the problem is, it's similar to previous scenario where price is set to 0 if no exchange is available in the API, except this time it affects the volume, is it something you could add to use global value even if calculator returns no supported exchanges?
Within a statistics provider, for example CC or WTM, Awesome Miner handle the concept of no exchange.Bit of a problem with exchange/volume filtering (sorry been away for the past few weeks, so didn't go through the posts thoroughly if it's been mentioned already).
Coins are grayed out in the following scenario when
-> Coin meets the minimum volume set in Options -> Statistics Providers
-> Exchange list in API is empty
in the below example is Espers (ESP), Statistics Providers Ordering (CC > WTM > CTM).
Use all exchanges (check), minimum exchange volume (0.002 BTC)
CMC's 24h volume matches the API of approx $196 USD
I know where the problem is, it's similar to previous scenario where price is set to 0 if no exchange is available in the API, except this time it affects the volume, is it something you could add to use global value even if calculator returns no supported exchanges?
Awesome Miner do find the coin on CC in this case, and CC has highest priority, it will currently not even look at the same coin if provided by WTM or CTM. The result is that even if what CC provides doesn't match the volume filter, Awesome Miner will not look at the additional exchanges at CTM. Each provider is processed individually and coins already found will be ignored if found again.
I understand you point here, but I will have to redesign a few concepts before the scenario you describe can be supported. Thanks for the feedback on this!
January 14, 2019, 03:32:14 AM
On wtm we treat all 144,5 coins as zhash.
Just makes more sense from miner perspective to aggregate them under single name, as all of them use same miner and hashrate values.
Many thanks for your comment on this.Just makes more sense from miner perspective to aggregate them under single name, as all of them use same miner and hashrate values.
What you do here makes sense so I will use the same concept in Awesome Miner - make it ZHash all the time to avoid confusion.
January 14, 2019, 02:08:40 AM
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/[email protected]
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
--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]
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.
https://yadi.sk/i/F2NsXSwb4PSgqA
https://yadi.sk/i/t3SwW5soDaC1AA
https://yadi.sk/i/us4ZpKaNXeseqA
Those appear to just be screenshots of the working miner. I was looking for specifics on the configuration. Thanks though.
January 14, 2019, 12:48:44 AM
Patrike,
Bit of a problem with exchange/volume filtering (sorry been away for the past few weeks, so didn't go through the posts thoroughly if it's been mentioned already).
Coins are grayed out in the following scenario when
-> Coin meets the minimum volume set in Options -> Statistics Providers
-> Exchange list in API is empty
in the below example is Espers (ESP), Statistics Providers Ordering (CC > WTM > CTM).
Use all exchanges (check), minimum exchange volume (0.002 BTC)
CMC's 24h volume matches the API of approx $196 USD
I know where the problem is, it's similar to previous scenario where price is set to 0 if no exchange is available in the API, except this time it affects the volume, is it something you could add to use global value even if calculator returns no supported exchanges?
Bit of a problem with exchange/volume filtering (sorry been away for the past few weeks, so didn't go through the posts thoroughly if it's been mentioned already).
Coins are grayed out in the following scenario when
-> Coin meets the minimum volume set in Options -> Statistics Providers
-> Exchange list in API is empty
in the below example is Espers (ESP), Statistics Providers Ordering (CC > WTM > CTM).
Use all exchanges (check), minimum exchange volume (0.002 BTC)
CMC's 24h volume matches the API of approx $196 USD
I know where the problem is, it's similar to previous scenario where price is set to 0 if no exchange is available in the API, except this time it affects the volume, is it something you could add to use global value even if calculator returns no supported exchanges?
January 13, 2019, 11:20:16 PM
Barely visible. Watch the capture, arrina are ZEL and BTZ de cointomine, and just below you can see a little ZAL of coinscalcutor
What I do not know if it is the cointomine api problem that calls the coins in another way internally, or some change in this latest version of today.
I have updated and just after it has happened. I have the 4 aggregators activated at the same time, Cointomine with premium API due to my donation.
I'll tell you if it can be fixed in some way.
This is basically the same issue and the same workaround can be applied. As the same coin can exists multiple times with different algorithms (for example Digibyte and a few more), Awesome Miner can list each combination of unique coin and algorithm.What I do not know if it is the cointomine api problem that calls the coins in another way internally, or some change in this latest version of today.
I have updated and just after it has happened. I have the 4 aggregators activated at the same time, Cointomine with premium API due to my donation.
I'll tell you if it can be fixed in some way.
In this case we have a few coins that are listed with both Equihash 144.5 (from CoinToMine) and ZHash (from WhatToMine/CoinCalculators?). Both will show up as Awesome Miner see they have different algorithms.
I will try to re-map some of these coins to the correct algorithms in Awesome Miner itself.
Edit: It looks like WhatToMine and CoinCalculators lists a few coins differently as well. XSG is one example - making it show up twice - one for each algorithm. Right now I'm a bit unsure which one is correct and this goes for a few coins.
There is a solution.
Options - Statistics Providers and Overridd coin algoritm Configure
Set ZEL to Zhash
Set BTCZ to Zhash
Then apply the changes and click the update button on the coins tab
January 13, 2019, 10:52:22 PM
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/[email protected]
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
--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]
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.
https://4.downloader.disk.yandex.ru/preview/9c45a443adbb8a03e0c755519b1221b5937cd16ed6852b4210cfe09b7f52d52a/inf/TAgBtPohBL13YBP3LaWDgSoF70rIklXMnCBi4fGEvpQiIWhiK0fC8JFMQQUZmQVrwNQyf09wIM8De5_blhVnZw%3D%3D?uid=159202907&filename=2019-01-14_08-57-09.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664
https://2.downloader.disk.yandex.ru/preview/fd23deb23bf3f9d40a13525d23ad28ce5b2c47330c349270ddd4aae12a82e572/inf/ndRxsj49Ua_ZkIWPj-5jgAqGeCYz1sL_RiYb4SECOiOFVBmQNqt1DnZkbWl1_47u1zakCqMFikUNvkqY3ZPgPQ%3D%3D?uid=159202907&filename=2019-01-14_08-57-18.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664
https://4.downloader.disk.yandex.ru/preview/d38037e9090a0aafb05c07790b2d2c23ab1b56168970bae711ef04c657ef93b7/inf/V6I8mr-AW0GAMaz7I_GgQLRBGvac8SbBwuYxD50QKgXsQ--MgSy9-rZvDBecnx2G9ztzu2bUZtWE2vqVBeFMNg%3D%3D?uid=159202907&filename=2019-01-14_08-57-40.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664
Bump for you.... and your images looks like not supported.
https://yadi.sk/i/F2NsXSwb4PSgqA
https://yadi.sk/i/t3SwW5soDaC1AA
https://yadi.sk/i/us4ZpKaNXeseqA
January 13, 2019, 10:47:58 PM
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/[email protected]
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
--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]
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.
January 13, 2019, 10:05:10 PM
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/[email protected]
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
--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]
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.
https://4.downloader.disk.yandex.ru/preview/9c45a443adbb8a03e0c755519b1221b5937cd16ed6852b4210cfe09b7f52d52a/inf/TAgBtPohBL13YBP3LaWDgSoF70rIklXMnCBi4fGEvpQiIWhiK0fC8JFMQQUZmQVrwNQyf09wIM8De5_blhVnZw%3D%3D?uid=159202907&filename=2019-01-14_08-57-09.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664
https://2.downloader.disk.yandex.ru/preview/fd23deb23bf3f9d40a13525d23ad28ce5b2c47330c349270ddd4aae12a82e572/inf/ndRxsj49Ua_ZkIWPj-5jgAqGeCYz1sL_RiYb4SECOiOFVBmQNqt1DnZkbWl1_47u1zakCqMFikUNvkqY3ZPgPQ%3D%3D?uid=159202907&filename=2019-01-14_08-57-18.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664
https://4.downloader.disk.yandex.ru/preview/d38037e9090a0aafb05c07790b2d2c23ab1b56168970bae711ef04c657ef93b7/inf/V6I8mr-AW0GAMaz7I_GgQLRBGvac8SbBwuYxD50QKgXsQ--MgSy9-rZvDBecnx2G9ztzu2bUZtWE2vqVBeFMNg%3D%3D?uid=159202907&filename=2019-01-14_08-57-40.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664
January 13, 2019, 06:16:13 PM
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/[email protected]
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
--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]
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
Jump to: