While MiningRigRentals is not outright banned like Nicehash, you can eliminate the problem you're having and get support by simply connecting directly to Prohashing. Ah, that's good to know, thanks! I actually discovered them on this ProHashing page and thought they were vetted, so decided to try i...

The best choice is to use the "i=" password argument, in addition to the others you've already selected, to allow the mining servers to determine the best settings based upon the type of mining rig. You can use the "Worker Configurator" page to select your mining rig type from t...

Looks like this might have been an issue with overall rig configuration, but leaving this thread open just in case there are other password arguments required that I didn't set.

Having trouble getting SHA-256 Asicboost to connect and hash, using: stratum+tcp://eu.prohashing.com:3335 & my password arguments are: c=bitcoin,m=pplns

Am I potentially missing anything else? Thanks!

Would also be interested in the possibility of this happening in the future. Alternatively, would ProHashing ever consider setting up an ADA stake pool to help slightly boost returns on mined/held ADA?

I often leave my Prohashing page up in a chrome tab for extended periods of time, but refreshing or moving to a new page does not fix it. The same issue appears on both the dashboard and mining pages if I move between them. Everything looks fine as of this morning. I wish I could help provide better...

The individual workers pane in my Dashboard and Mining pages consistently looks like this after logging in or refreshing. Sometimes it goes back to normal on its own, but usually it remains in this state:

Got an answer on bitcointalk that explains the problem, just in case anyone else encountered a similar issue:

You can only use two or more pools, if they are both mining the same coin. If you use multipools, use only one (no failover). This is a bfgminer known problem.

I used the configurator to get the default options for my Futurebit Apollo scrypt miner and pointed it at the pool, I am noticing that it takes a long time to start up, skipping over the first coin in fact and going directly to LTC. After a short period the hardware error rate skyrockets up to 30% a...