I do appreciate subtlety, but a small gray font does not lend itself well to "attention", does it?  And again, localization, please, since UTC = halfway 'round the planet for some of us.

In DarkKight's defense, I'm not sure I would have checked my prices after adjusting my stated hash rate as the two have been mutually exclusive up to this point.  I happened to catch the glitch in the latest JavaScript update and saved myself from an ultra-low priced rental, but I was changing prices, not my hash rate.

And oh, did I mention that your auto-cancellation didn't even change the pools so the renter has been getting my rigs for free while I slept?

I'm leaving them there so you can see for yourself while I put in a support ticket about this.

I appreciated much of the hard work put into positive changes being made here lately, and it's my own fault for not reading the alert text quickly enough, but I generally correct issues within an hour (often within ten minutes) and provide appropriate lease extensions and refunds when necessary, so how do I disable this auto-cancellation feature?

I lost 24 hours of rental because of a 45 minute ISP issue that I could have easily compensated for by extending the lease.  Considering my rigs were rented for 0.0065 BMD and the new floor on the list is now under 0.006 BMD, I lost 24x0.0005 = 0.012 BTC, even if I had rented right away for 24 hours.

And please let us choose how we're paid.  Getting paid in DOGE is murder - by the time I'm done with a lease, especially a longer one, the DOGE is almost always worth less than what it was worth when the lease started.

One recommendation I have is for you to announce planned maintenance at the top of the web site in nice visible text.  It doesn't have to be Giant Sized, just visible.  Even knowing an hour in advance would be helpful and keep people from wondering what's going on an how long it will be unavailable.

IMHO, allowing payment by USD/credit card kind of defeats the purpose of everything we're doing here.

One way to make the port number super easy is to use whatever is entered into the username coming from the incoming rig.

For LRP, not just speed logging, but EVERYTHING logging, including timestamps, of course.  Oh, and a way to use different port numbers per mining rig so when we jump across NATs, we can hit all rigs on the other side.

To the person renting my rig:
It looks like we've been having some stability issues with one of the rigs in the Bob mining cluster, so I've added another two GPUs, so your hash rate should actually get above 6.5 MH/s in your pool, but it will not be reflected in the LeaseRig hash rate since it does not have a way to monitor this extra rig I've added to the cluster.

Thanks,
-Bitlynx

BTW, your FAQ: https://leaserig.freshdesk.com/support/solutions/articles/1000045037-local-payments-hourly-post-payments-and-lease has a line written in a way that can be left up to interpretation (which I did):

• Once there you will see a "My Account" link containing three wallets for -- DOGE, BTC, LTC -- if you do not see an address or you see a generate button you must click the generate button to create an address and accept that currency as payment.

I thought that meant that if I don't generate the address, the system would automatically disable payment to me on that currency.

Doge address generated, and don't take my complaint too hard - I love the local payments idea and think it's been a long time coming.

IMHO, clicking that Accept Local Payments button should have popped up window asking for confirmation that you are willing to accept all forms of payment and that any cryptocurrency addresses that weren't generated will automatically be generated to ensure that payments can be accepted.

Otherwise, you get a precarious situation like mine where you supposedly can accept local payments but, until you generate addresses, you really cannot.

I'm about to submit a ticket for this, but I just switched to local payments, generated addresses for BTC and LTC (but not Doge) and got a renter, who chose to send me Doge.  I take it local payments means I am roped into accepting any of the three?  Perhaps I am daft, but that was not well communicated.  I love the minimization of TX fees, but if I don't get to choose the coinage I accept, that's a bummer.

At the very least, I hope it's not a bug and the Doge he paid is lost since I didn't generate an address!

Thanks for the quick response and action.  Any feedback for adding the Forum link, too?  The one at the bottom of the home page is tiny and, IMHO, fairly well buried.

You should really add a Support link to the "main menu" area of the site that links to FreshDesk as well as a Forum link that links to this thread.  As for CAPTCHA, 2-factor auth is definitely the preferred fix, with some decently long session (like 48 hours) - I'm looking forward to it coming out in the next update.

And, because you guys know which providers don't have matching customer accounts, you should consider e-mailing them directly.

+100 for the pending press releases!

We really, really need a built-in logging output for LRP.  And localized time zones.  And yes, I know - I've already FreshDesk'd both requests.  By the way, http://leaserig.freshdesk.com/support/solutions/folders/1000108903 is supposedly the Bug and Feature Bounty section, but seems to be unused, so I submitted my suggestion as tickets.  Was that the right approach?

I tried this on Windows 7 and LRP just hung, the log file got created, but nothing was in it.  Does this work for you in Windows, and if so, does LRP still show output on the screen while it's getting logged or does it only get dumped to the log file so you have to view the log file to see what's going on?

djeZo, we really, really need logging on the LeaseRig proxy and pools.  It's currently impossible to know if there were rig issues or issues with the pools.  In the "Old Days" we could consult our own logs to see what pools were active and what kind of issues were happening with those pools.  Now, it's all hidden behind the proxy, which is great, but that lack of transparency means we cannot analyze post mortem issues.  So, when there are problems, all we can do is bite our tongues and refund our renters... even if our renters failed to set a failover pool and our cgminers choked due to no available pools.

Please let us know if there is any way to log output to a file with built-in Windows and Linux utilities (I run on both OS's.)  Also, please consider forcing one of our default pools as the secondary if the renter doesn't set one.

Thank you,
- Bitlynx

You should really post a link to this graph on your main page (if it's there, I totally failed to see it.)

Good question.  I asked and the renter said no, because he was interested in mining Hex, which is what he returned to mining once he got my messages.

Rats!  I didn't leave it active on purpose.  I had intended to but forgot to disable my incoming API ports from the old method.  Doh!

So, back to my begging - please enable logging (first) and then add (a simple) API to LRP so we can see what's happening and be able to review history.  One issue with LRP is that we have zero transparency without needing to constantly log into the LR admin interface.  When we were using the old method, we could use the miner log, cgwatcher logs, cgwatcher data logging, etc.

Just installed the new version.  Any chance you could send out an e-mail to all rig providers when you come out with updates to LRP?  Still hoping you can restore my renter's pools before his lease is up...

Also, if you have a table in your database that keeps track of pools, I'm sure my renter would appreciate it if you could put them back so my rig is mining on his pool instead of my default middlecoin pool.  If you don't have such a table, you might consider implementing one, even if it's just for the past couple of renters (to keep the data size down.)

Thanks,
- Bitlynx