Quote from: TryinToMine on January 31, 2018, 09:54:57 PM

Quote from: DrStein99 on January 31, 2018, 06:07:02 PM

Last night I spent a couple hours trying to connect XMR-STAK to miningpoolhub, with no success. I read the instruction thoroughly. The system appears to have it's own login, where I place my own wallets that I did do. For reasons unknown, I just can not get XMR-STAK to connect. It keeps throwing out error:

Code:

SOCKET ERROR - [us-east.cryptonight-hub.miningpoolhub.com:20580] CONNECT error: GetAddrInfo: Name or service not known

I tried connecting using SSL

Code:

"pool_list" :
[
{ "pool_address" : "ssl://us-east.cryptonight-hub.miningpoolhub.com:20580", "wallet_address" : "myusername.myworker", "pool_password" : "x", "use_nicehash" : false, "use_tls" : true, "tls_fingerprint" : "", "pool_weight" : 1 },

],

and get a different error:

Code:

[ssl://us-east.cryptonight-hub.miningpoolhub.com:20580] 140551865235040:error:2006A066:BIO routines:BIO_get_host_ip:bad hostname lookup:b_sock.c:146:host=ssl

I can ping the address. I tried "use_tls" both TRUE and FALSE. I feel like I tried every option. XMR-STAK is listed on the site's list of software to use. Does anyone else use this pool service, can I get any advice please?

Facing similar problems. See my post above.
Also XMR-Stak.
Still no answers......

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

Quote from: Whatt on February 01, 2018, 07:16:53 AM

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. =)

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.

Quote from: Lewqa87 on January 30, 2018, 06:15:23 PM

Good afternoon. Need help, said that it will help. Is the translation with Zclassic for zcash for. Mined coins are not reall in Zchash, and thus disappeared from the account Zclassic. In the transaction the following information:
https://d.radikal.ru/d05/1801/a4/fd4776a81cd6.jpg
Huh

Thank you for any help.

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

Quote from: Riptide_NVN on January 31, 2018, 03:24:06 AM

Any plan to get a LUX/phi algo pool going on MPH?

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

Quote from: Aspirinis on February 01, 2018, 02:29:04 PM

Quote from: bubbagump on February 01, 2018, 01:45:36 PM

Quote from: GeProk on February 01, 2018, 01:17:11 PM

Quote from: Aspirinis on February 01, 2018, 12:57:17 PM

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 Huh

Thanks!

Same problem here.

I'm seeing this too.

Quote from: Aspirinis on February 01, 2018, 01:41:35 PM

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.

~~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.

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 Sad

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.

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.