Topic: [ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin. - page 63. (Read 487870 times)

help please

is there any way to set the verge-scrypt difficulty?

hi all

I have created several mining pool hub workers to logically group some mining rigs.
I want to assign each mining pool hub worker it own payment/wallet.
can this be done?

TIA

Hello,
I've this problem, each 6 hours the miner stops but doesn't crash, it stops running and doesn't restart. The miner is mkx miner.

https://ibb.co/bYz0uR">https://preview.ibb.co/j0Wr16/IMG_2108.jpg" alt="IMG_2108" border="0">
upload">https://it.imgbb.com/'>upload image

Hi guys, anyone have idea to solve this cloudflare problem?

"
WARNING: Coinbase is down.
WARNING: Pool API (MiningPoolHub) has failed.
WARNING: Pool API (MiningPoolHubCoins) has failed.
WARNING: Pool API (Zpool) has failed.
"

I have this ultil last week, follow log:

**********************
PowerShell transcript start
Start time: 20180201153356
Username: DESKTOP-GESUNUK\Mick Love
RunAs User: DESKTOP-GESUNUK\Mick Love
Configuration Name:
Machine: DESKTOP-GESUNUK (Microsoft Windows NT 6.2.9200.0)
Host Application: C:\Program Files\PowerShell\6.0.0-rc.2\pwsh.dll -noexit -executionpolicy bypass -windowstyle maximized -command & .\multipoolminer.ps1 -wallet 1EJJDXdjau1sxTysE9s1fSbzXLc1ryhV8u -username michaelps100 -workername GPU -region us -currency btc,usd -type nvidia, cpu -poolname miningpoolhub,miningpoolhubcoins,zpool,ahashpool -algorithm Bitcore, Blakecoin, Blake2s, blakevanilla, C11, CryptoNight, Ethash, Decred, Equihash, Groestl, HMQ1725, hsr, jha, Keccak, Lbry, Lyra2RE2, Lyra2z, M7M, MyriadGroestl, NeoScrypt, Nist5, PHI, Polytimos, Quark, Qubit, scrypt, SHA256, Sia, Sib, Skunk, Skein, Timetravel, Tribus, Veltor, X11, X11evo, X11gost, x13, x14, X17, Xevan, Yescrypt, siaclaymore -donate 0 -watchdog -switchingprevention 2
Process ID: 1908
PSVersion: 6.0.0-rc.2
PSEdition: Core
GitCommitId: v6.0.0-rc.2
OS: Microsoft Windows 10.0.16299
Platform: Win32NT
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.10032.0, 6.0.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
WSManStackVersion: 3.0
**********************
Transcript started, output file is .\Logs\2018-02-01_15-33-56.txt
PS>TerminatingError(Invoke-RestMethod): "    
  

Attention Required! | Cloudflare

Thank you MPH for the very quick resolution here !!

The support on this pool is really great and never dissappoints me...

Remove "ssl://" and "use_tls":true





Not sure at this moment. BTCZ wallet is not ready and I don't know much about it in detail.
I think I'll open BTCZ but cannot guarantee it at this moment.





You will get Zcash after few hours. It's normal. Auto exchange needs time.





I'll add pool features first and add coins one by one after that.







Sorry for inconvenience.

There was weird error on some servers. Some pool servers created wrong DAG file for that period.
After flushing DAG file and restart, it is solved and working well.

I'm investigating the issue that how come this issue can happen.

It seems like the error migrated to the US server too after a while...so it doesn't help much if you switch servers unfortunately

Also this error doesn't seem to be caused by OC, it happened simultaneously on 2/2 rigs that i have. And as i noticed, the same thing happened to other people as well at about the same time.

BTCZ ?? BTCP maybe ?

I have this problem if I overclock too much, but now I'm not sure if it is due to overclock.

I'm seeing this too.

That works for one of my miners but not for the others  
Nevermind, it works fine.  It was just a dumb mistake on my part.

I think it has to do with the europe.ethash-hub.miningpoolhub.com server.
When i tried to switch to the us-east.ethash-hub.miningpoolhub.com , the error vanished and the miners re-appeared in the MPH Dashboard.
Unfortunately the ping times are also higher in the US server but at least it is working for now.

Same problem here.

Both of my miners (ETH), about 1-2 hours ago, stopped appearing in the MPH Dashboard.

So i've logged in to check them out and both they were getting this error in CMD:

ETH: Received error: {"id":11,"result":null,"error":[23,"lowdifficultyshareof2"]}

but also they kept on digging.

Can someone inform us, if the pool is having any issues today Thanks!

yes, you will, it is a bad implementation of multipool.

for xmr-stak:

nicehash_nonce : false
use_tls : true
tls_secure_algo : true
pool_address : europe.cryptonight-hub.multi...com:17024
wallet_address : username.1
pool_password : x

where 1 is created hub worker with default job and password x

With the BTCZ fork off of ZClassic. Can we expect BTCZ to be added?? both dedicated and profit mining?

I wouldn't mind be able to single mine BTCZ for a few days on the pool. well at least until the ASICs bomb the fluff out of the difficulty.
Be nice to get in on something at the start for a change. =)

with those multi-miners you can switch your altcoins to any coins of your choosing, i am currently switching my mined coins to ethereum. your answer does not really answer my question though, have you used any of these multiminers?

I don't know how smart xmr-stak is, but I don't use the ssl:// in front in my config file for pool_address. Just hostname:port. 

Hi.  Thank you for sharing.  I actually spent a few hours TODAY just scanning this FORUM for key words "xmr-stak" combined with an array of things "cryptonight" "miningpoolhub" "getaddrinfo" and did not find very many results.  I also wasted some more time scanning google for answers, no resolve there.

I believe I also tried to switch to AEON and try to mine that with xmr, and also got the same results. 

So, as a matter of troubleshooting - my next step will be to try and use other software.  My version of xmr-stak was modified by myself and I customized my own routines, that work perfectly for the other monero pools I have tried so far.  Hopefully I overlooked something in my account setup that is rejecting my worker from attaching.

I dont use XMR-STAK but I do use Xmrig and it connects to 20580 (Monero) without issue (tested a minute ago). So youre likely configuring XMR-Stak incorrectly or something else is wrong on your end.