[ANN] LeaseRig.net Rent & Hire Scrypt(Jane/Nfactor)/SHA3/SHA256/X11 HashPower!

[miaviator]

To everyone below.  "We apologize for any inconvenience"  Blah Blah Blah, when you hear it thousands of times from everyone in the world it sounds insincere.

We are reading your messages and testing, coding, responding.

Prior to swapping the site XMK3 rented a rig from me as a test on LRP and direct.  After swapping the site XMK3 rented another rig from me (I raised my prices for this test) in order to test the live site.  Pool changes are working.  And the site is working.  I will work with each of you as much as possible just know that I am primarily on Gtalk/Skype because that covers the majority of clients here and for the UH service. 

I'm currently allowing my miners to allow both the old and new ip and my miners are offline. This is frustrating me.

Skype/Gtalk? 

Paste your API line for me.

--api-groups P:switchpool:addpool:removepool:restart:save:* --api-listen --api-allow P:23.236.58.114 --api-port ****

I have ventrilo

The API line looks correct.  Is there a firewall between you and the internet which is blocking based on IP?

Pools managment not working... Got propper ip

Restarted and ok, extended lease time

Same thing, please paste the config line.  Is there a firewall which may be blocking?  Have you restarted the mining software?

I decided to switch to LRP, which deleted my customers pools since I got no response. Insanely frustrated with this whole switch.

Ignore my above above response and the one before.

cgminer.exe --api-groups P:switchpool:addpool:removepool:restart:save:* --api-listen --api-allow P:23.236.58.114 --api-port 2***

this is my code. but it says still "OFF" how i can fix it?

You are also using a 2**** port?   IE can you paste your actual line minus any private IP blocks and the port used to connect?

Is there a firewall that could be restricting by IP/hostname?

Have you restarted the miner?

[P2Pooler]

Sorry to butt in, I just love troubleshooting....

You might want to check on your rig's configuration page "Mining rig address (including port)*:" ?

I have a cron job on my rig that runs that "updateip.py" script every 5 minutes to keep my IP/Port up to date in case it changes. But you can just update in manually too on that page.

BTW miaviator, do you still support that script?

It calls the following page which seems to error currently:
http://leaserig.net/updateip.jsp?rigid=........

There might be a lot of people using that method.

[miaviator]

Sorry to butt in, I just love troubleshooting....

You might want to check on your rig's configuration page "Mining rig address (including port)*:" ?

I have a cron job on my rig that runs that "updateip.py" script every 5 minutes to keep my IP/Port up to date in case it changes. But you can just update in manually too on that page.

BTW miaviator, do you still support that script?

It calls the following page which seems to error currently:
http://leaserig.net/updateip.jsp?rigid=........

There might be a lot of people using that method.

Honestly.  I've never heard of it....  Great idea though.   Give me a bit and I'll see what is going on there.  Anyone else having issues who is using that script?

I wonder if both ends can support cnames vs dealing with all this hardcoded crap?  IE if you put your own dyndns cname in the admin panel and allow-ip of miner.leaserig.net (which doesn't exist currently)  then everything could run dynamically?  I'll test this out in the AM.

[P2Pooler]

Under B. Advanced Method

Solution B (Windows&Linux)
Install Python 2.7. Download this simple small python script (right click and save as). When you run it, you will need to provide parameters:
name - your nick name on this forum (if it contains spaces, encapsulate it with "")
password - your admin login password (you will receive that from me when you request to become provider)
rigid - is visible in admin panel for each rig (you get access when you request to become provider)
API-port - you choose this one next step

Then you simply run this script and you do not have to worry about IP changes - the script will auto update your IP on LeaseRig.net when your IP changes. You will have to run instance of this script for every rig you offer.

https://bitcointalk.org/index.php?topic=417092.0

[Fattox]

I have added the new IP to the API allow part of my config, but when people rent from me i get a mail telling me their pool could not be changed.

When i log in to the rig, it seems they DID manage to change their pool the first couple of times this happened, but now a customer emailed me telling me he couldn't change pools and wanted a refund. Here's my API settings:

--api-groups P:switchpool:addpool:removepool:restart:save:* --api-listen --api-allow W:89.212.242.33,23.236.58.114,127.0.0.1 --api-port 7777

Any idea what the problem could be? It can't be a firewall or anything i'm sure, as i never had to allow anything extra for the previous LeaseRigs address.

Do you have a solution, or should i just switch to using LeaseRigProxy?

Cheers.

[P2Pooler]

I have added the new IP to the API allow part of my config, but when people rent from me i get a mail telling me their pool could not be changed.

When i log in to the rig, it seems they DID manage to change their pool the first couple of times this happened, but now a customer emailed me telling me he couldn't change pools and wanted a refund. Here's my API settings:

--api-groups P:switchpool:addpool:removepool:restart:save:* --api-listen --api-allow W:89.212.242.33,23.236.58.114,127.0.0.1 --api-port 7777

Any idea what the problem could be? It can't be a firewall or anything i'm sure, as i never had to allow anything extra for the previous LeaseRigs address.

Do you have a solution, or should i just switch to using LeaseRigProxy?

Cheers.

I think you need the "W" before each IP address?
W:127.0.0.1,W:23.236.58.114

[Gamer67]

It should be P:89.212.242.33,23.236.58.114,W:127.0.0.1

My example:

"api-allow" : "P:23.236.58.114,89.212.242.33,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*",

[Fattox]

It should be P:89.212.242.33,23.236.58.114,W:127.0.0.1

My example:

"api-allow" : "P:23.236.58.114,89.212.242.33,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*",

Before i just had it as "W:89.212.242.33,127.0.0.1" and it worked without issue. I'm not sure whether to try this and risk another complaint, or just use LRP. D:

Edit - Actually maybe it worked this way because the LR IP was the first after the "W:". I will give your suggestion a try after all.

Cheers.

[P2Pooler]

It should be P:89.212.242.33,23.236.58.114,W:127.0.0.1

My example:

"api-allow" : "P:23.236.58.114,89.212.242.33,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*",

Thanks, I use a conf file too (not command line) and never could get that right. I just added it this way, restarted the miner, and tested switching pools from leaserig and it works great!

[Gamer67]

It should be P:89.212.242.33,23.236.58.114,W:127.0.0.1

My example:

"api-allow" : "P:23.236.58.114,89.212.242.33,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*",

Before i just had it as "W:89.212.242.33,127.0.0.1" and it worked without issue. I'm not sure whether to try this and risk another complaint, or just use LRP. D:

Edit - Actually maybe it worked this way because the LR IP was the first after the "W:". I will give your suggestion a try after all.

Cheers.

You are using this:

-api-groups P:switchpool:addpool:removepool:restart:save:* --api-listen --api-allow W:89.212.242.33,23.236.58.114,127.0.0.1 --api-port 7777


Either change them both to P or W.

W gives full api access

P just gives you whatever commands you denoted after it.

P is the safe bet. Not sure why it worked fine for you before but it is most likely your issue now.

[miaviator]

It should be P:89.212.242.33,23.236.58.114,W:127.0.0.1

My example:

"api-allow" : "P:23.236.58.114,89.212.242.33,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*",

Thanks, I use a conf file too (not command line) and never could get that right. I just added it this way, restarted the miner, and tested switching pools from leaserig and it works great!

Let me know what to add to the OP!

[P2Pooler]

It should be P:89.212.242.33,23.236.58.114,W:127.0.0.1

My example:

"api-allow" : "P:23.236.58.114,89.212.242.33,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*",

Thanks, I use a conf file too (not command line) and never could get that right. I just added it this way, restarted the miner, and tested switching pools from leaserig and it works great!

Let me know what to add to the OP!

I wasn't actually having the problem that others are currently. I just meant that before I had used "W" for everything, but now I got the "P" group to work using the cgminer.conf file vs command line thanks to Gamer67's tip. Maybe people aren't restarting the miner after updating their conf? I was under the impression that the conf file is parsed on miner start up, and that it doesn't recognize changes unless it is restarted.

[Fattox]

It should be P:89.212.242.33,23.236.58.114,W:127.0.0.1

My example:

"api-allow" : "P:23.236.58.114,89.212.242.33,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*",

Before i just had it as "W:89.212.242.33,127.0.0.1" and it worked without issue. I'm not sure whether to try this and risk another complaint, or just use LRP. D:

Edit - Actually maybe it worked this way because the LR IP was the first after the "W:". I will give your suggestion a try after all.

Cheers.

You are using this:

-api-groups P:switchpool:addpool:removepool:restart:save:* --api-listen --api-allow W:89.212.242.33,23.236.58.114,127.0.0.1 --api-port 7777


Either change them both to P or W.

W gives full api access

P just gives you whatever commands you denoted after it.

P is the safe bet. Not sure why it worked fine for you before but it is most likely your issue now.

I've now tested:
"P:switchpool:addpool:removepool:restart:save:* --api-allow P:89.212.242.33,23.236.58.114,W:127.0.0.1"
""P:switchpool:addpool:removepool:restart:save:* --api-allow P:89.212.242.33,23.236.58.114,127.0.0.1"

... and it fails to switch pools with either config. I restart my miner after each change.

Any more ideas? If not i will just configure LRP sometime this week i guess.

[Gamer67]

Sorry. I should have said you can just remove the 89.212.242.33.

Try it once more without that maybe.

[Fattox]

Sorry. I should have said you can just remove the 89.212.242.33.

Try it once more without that maybe.

D'oh, in my mind the 89. IP was the new one, that's why i left it at the front.

This worked, thanks for your help buddy.

[miaviator]

It should be P:89.212.242.33,23.236.58.114,W:127.0.0.1

My example:

"api-allow" : "P:23.236.58.114,89.212.242.33,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*",

Thanks, I use a conf file too (not command line) and never could get that right. I just added it this way, restarted the miner, and tested switching pools from leaserig and it works great!

Let me know what to add to the OP!

I wasn't actually having the problem that others are currently. I just meant that before I had used "W" for everything, but now I got the "P" group to work using the cgminer.conf file vs command line thanks to Gamer67's tip. Maybe people aren't restarting the miner after updating their conf? I was under the impression that the conf file is parsed on miner start up, and that it doesn't recognize changes unless it is restarted.

API changes SHOULD require a restart.

[miaviator]

This is a fantastic community! 

[miaviator]

Did anyone else notice:

Providers can only set two pools?  (I usually set four)

There is no option to set pools for all rigs?  (That is a lot of manual pool settings for me)

There is no B/Mh/Day for all rigs setting? (IE I want to price at ~6mBtC/Mhs/Day across the board)

Sorry xmk3...

[suchmoon]

Did anyone else notice:

Providers can only set two pools?  (I usually set four)

There is no option to set pools for all rigs?  (That is a lot of manual pool settings for me)

There is no B/Mh/Day for all rigs setting? (IE I want to price at ~6mBtC/Mhs/Day across the board)

Sorry xmk3...

I certainly miss the ability to set BTC for all rigs at once. Pools would be nice too, although I don't change those often.

[railzand]

Yes these will be very nice features; set 4 pools for all my sha rigs, adjust prices for all my keccak rigs...
Also, a lot of good suggestions from @kenshirothefist in #79.
Hey, how about accepting LTC?


and this:

READ THESE NOTICES!

All deposit addresses will be changed and current addresses will become invalid!  Any coins deposited to the old addresses after the change will be stuck in purgatory.

Those not on LeaseRigProxy: CHANGE YOUR ALLOW-IP TO INCLUDE 23.236.58.114 YOUR MINERS WILL SHOW OFFLINE UNTIL YOU DO!

ALL PROVIDERS THAT HAVE SECURITY DEPOSIT WITH DJEZO CAN REQUEST IT TO BE RELEASED BY CONTACTING HIM; PROVIDE YOUR BTC ADDRESS AND REPUTATION THREAD. YOU HAVE UNTIL 30.4.2014 TO DO SO.