Topic: [ANN] LeaseRig.net Rent & Hire Scrypt(Jane/Nfactor)/SHA3/SHA256/X11 HashPower! - page 59. (Read 125841 times)

good luck man! djezo runned it great, hope you will be as good - or even better

Prices go up as well as down...

I'm worried too, but we've seen dips like this before.

I don't know if the price will stay at this value. Until anything happens I can't afford keeping the rig up. Its not about faith. I won't have money to feed my child if I keep it running at this price. And I am sure there are many more in my situation.

Oh ye of little faith in bitcoin.. you think the price will stay like this...

The problem is I wanted to shutdown my rig tonight. BTC got to the point where mining doesn't even pay for power...

Be patient, I'm sure they'll work it out soon...

I am having problems with the helpdesk page. I tried signing up today but never received the email with the password.
And at the same time I don't seem to have any luck talking to an agent online.
Also miaviator responded to my pm with a predefined message pointing me to helpdesk...
So... All I wanted to ask is when I will get my deposit back. I got over 100 hours of rent on my rig...

The problem with cgminer is (if you're using gridseeds) is you have to turn off your USB hubs before running it, and then switch the hubs on again once cgminer is running - which makes it very difficult to manage if you're trying to manage remotely. That's the main reason why I'm using bfgminer, since it auto-detects the gridseeds. In case of a power cut or other unforseen problem, it restarts with no hassle.

Maybe I'll try cgminer again. Last time I used cgminer, it showed very low WU, so I'm wary of using it to be honest.

I've only ever used cgminer so don't know what difference there is between that and bgminer with regards the api.

The --api-allow needs to be set to the proxy machine not the leaserig server.

So for my machines I just have --api-allow W:192.168.1.200

The clever thing is that if you have multiple machines, leaserig proxy adds all the hashrates up and reports the grand total.

Try --api-allow W:23.236.58.114

bfgminer won't even start with --api-allow

I get:

WARNING: cgminer API (127.0.0.1:4028) Failed to connect

What is the proxy saying, is it trying to connect to 4028? Is the proxy running on the same machine as bfgminer? Perhaps you need to use --api-allow.

cudaminer does not have an API.

Great - now it says speed 0.0

:sigh:

Maybe it's because I'm using bfgminer not cgminer. I set up --api-listen and --api-port 4028 in the bfgminer bat file and changed the proxy startup from 0 to 4028. Reported speed shows constantly as zero.

i am also experiencing this throughout the day. on the providers page sometimes my other rig shows off in the status and when checking the physical machine it self it runs consistently.

the fluctuation of speed hashes was quite low or quite higher than what i can see from my rigs that supposed to be running and is really running at 1.3mhash indicated on my miner. however leaserig.net displays as low as 0.1 up to 1.8 which is really not as it is.
its my first lease and good thing is nobody is complaining too.
please fix this as it can put on a bad reputation on me as a starter.

btw i am using 750 ti's on cudaminer. a little help for api calling is what i really need?

So you can use the proxy + the API to fetch the hashrate?
I didn't know that. Thanks lol.

Not strictly true, the hashrate from the proxy can be done that way but can also get the actual hashrate from cgminer via api, it's in the readme file.

The default api port is 4028 so if you havent changed it

Been using the proxy since day 1 and speeds have always been accurate.

That's a quick fix.  Can someone put in the ticket?

It's because you are using LeaseRigProxy.
That thing reports hashrates based on accepted shares. If the pool has a high share difficulty (512, 1024 or so on) your hashrate will be shown much lower than it should be.
If the pool has a high share difficulty (16, 32, etc.) your hashrate will be shown higher than it should be.

The fix to this is:
Don't be lazy, set up "Method B", which is the API.
Instructions here: >>>CLICK HERE<<<

I myself used the proxy since I was lazy, but the hashrate was highly incorrect, so I took some time and setup method B.

I have a question about the reported hash speeds on LeaseRig.

I have two rigs that are mostly hired out all the time. The reported speeds they are running at when being hired are NOWHERE NEAR the speed of the rig itself. For example, I'm running at a constant speed of 7.2Mh/s, and on the site its telling me 0.89Mh/s. Sometimes it's higher, perhaps fluctuating between 1 and 5 Mh/s. When it's not being hired, I'm mining at clevermining.com or perhaps multicoin.us and the reported speed is about right at 7.2mh/s. So what's going on?

I'm thinking that perhaps the pools my hirers are choosing aren't so good, and therefore the share rate is down because of it. However this destroys my reputation - because people can see a graph of my rig's reported speed, and if they see it hovering between 1-5Mh/s when I'm saying it's 7.2Mh/s, they are going to go elsewhere. It's not my fault my hirers are choosing bad pools.

I also suspect the reported speed on Leaserig.net is completely different to that shown at a pool for some reason. If my rigs really were mining at only 1Mh/s then people would have complained - but none have yet, so I can only assume all is well. I just wish the hash rate on the site could be a true figure of my rig's performance.

Anyone else noticed anything or has any comments?