Mining Rig Rentals can't connect

[dysan819]

I am trying to connect to the pool and my miner is being rejected.
I am able to connect with my local miners, but the miner I rented at Mining Rig Rentals will not connect. The error claims to not be able to authenticate.

I am trying to connect using the following:
Address: stratum+tcp://Prohashing.com:3333
User: dysan819
Pass: x

Can you help me resolve this? I would like to get this resolved quickly since I am paying for a rental now. Thank you!

[Chris Sokolowski]

I think I know the issue. Try using just prohashing.com:3333 as the address and let me know what happens.

[dysan819]

I attempted to re-enter the server address but the still problem exists.
There is no option to remove the stratum+tcp part.

[Steve Sokolowski]

Chris, I can't do this right now, but try connecting as dysan using our miners. If you can connect using our miners, then this is probably a problem with the company renting the miners. If that's the case, then we need to perform further investigation to determine what the incompatibility is with their service.

[dysan819]

I don't know if this helps at all, but here is a screen shot from trying to add the pool.

[Chris Sokolowski]

I tried using dysan's name for our miners at "prohashing.com:3333" and it worked properly. I then tried connecting on my GPUs both with and without the prefix (our Zeusminer interface doesn't allow you to add the prefix) and either way it took about 30 seconds to connect and occasionally fails to connect. I am investigating this further at the moment.

[dysan819]

The rental did connect for a short time, but unfortunately it is offline again. Additionally, and possibly just as troubling, I am getting a huge amount of rejects. Even before I connected the rental, I was getting 20% rejects. With the rental connected I got 35% rejects.

[Steve Sokolowski]

Ah, I think I know the answer then.

There is a version of cgminer that, for some reason, doesn't work well with this pool because of a bug. Someone tried to connect a while ago with it and Kristof was able to help him figure out that he should use a different fork of cgminer. This other version of cgminer causes huge numbers of rejected shares. I'm guessing that that version of cgminer can't handle so many work restarts, but we don't know why it doesn't work.

The rental company probably uses this other version of cgminer. Chris or Kristof can confirm this hypothesis, but if that is the case, I don't think there's much that can be done in a short period of time. The rental company probably won't allow you to use a different version. Is there a way to determine if they are using cgminer and which fork is being used?

[cryptorific]

Well as far as I can tell mining rig rentals actually have a variety of individuals running a variety of hardware and software and then renting out their hardware. Unless dysan can give more info about the particular persons rig he is using I'm not sure how much help we can offer. Just for reference, the offending fork was Darkwinde's (https://github.com/Darkwinde?tab=activity) bfg fork for zeus. When the user updated to the latest cgminer release from zeusminer his rejects went to a normal level.

[jimlite]

I have had mixed luck with MRR. Some rigs don't even start, some hash with 20% rejects, some hash 100%. Asics are finicky, and so is the cgminer or sgminer versions. I think what would help is if the pool would accept passwords of diff=512, that works great for my asics.