Is your NIS synced ?
Please check your system time and see if it's way off.

You are probably already harvesting locally on that node. Since 1 harvester is the default maximum you can't also delegate harvest on that node.

You don't necessarily need a remote hose to use delegated harvesting so localhost is fine.

System time is correct and NIS says: "NIS is synchronized! (at block 3691)" at 21:13

current block 3704
Try to restart NIS, maybe that helps.

I had same problem earlier today. It seems one of the accounts are set to "unlocked" which means "harvesting" and now the GUI is not showing you any option to stop the account from harvesting "as you probably started harvesting with this account as LOCAL harvesting".

Now once your account turned active for delegate harvesting, you now have the option to start delicate harvesting but you don't have the option to stop local harvesting "as the GUI harvesting button been replace/switched to delegate".

If you wanna confirm that you indeed have one of your accounts unlocked/harvesting locally where you can't see that in the GUI, you can simply confirm that by performing the following steps:

- Open your browser
- Open this url: http://127.0.0.1:7890/account/status?address=PASTE_YOUR_ACCOUNT_ADDRESS_HERE
- Replace "PASTE_YOUR_ACCOUNT_ADDRESS_HERE" above with your account address
- You should receive a text/json response. Check the Status field. If it is set to locked the account is not harvesting, and if the status is set to unlocked so the account is harvesting.
- Do the same with all your accounts, you should find at least one account set to unlocked.

In my case I found one of my accounts status set to unlocked "though the GUI/client is not informing me about that nor allowing me an option to lock/stop local harvesting". So I wrote a python script around the lock api call, to lock the account. I can send you the script if you need it.

On the other hand an easy fast solution would be setting the maximum allowed number of harvesting accounts. You can set that in the configuration file:nis/config.properties  the default value is 1, change it to 2 and restart NIS. That should fix your problem.

Feel free to PM me if you need more help.

Thank you very much, very helpful answer

When you replace "PASTE_YOUR_ACCOUNT_ADDRESS_HERE" with your account's address make sure to remove the dashes "-" from the address. No dashes No spaces.

Thanks! I sort of figured, but was a bit unsure..

But I have another issue that might turn out as an embarrassement for me:

When using the testNEM account, I genertaed a real  NEM account and tooke great care to store the privkey and the pubkey.

Now the privkey opens another account, but the original account (I have listed right above my privkey) does exist and have the XEM in it.

Can this have gone wrong somehow?
 [I am not quite panicking yet, but would really like to find out]

what I have as privkey is a 64digit hex string with the e-f in small letters- this doesnt look like a passphrase to me.. 

was there any step involved that yields a 64 digit hex string with small letters?

Look at where under your "Current Balance" says something like "Vested Balance"

If your Vested Balance is less than 1000 NEM then you have to wait a day (where 10% of your total will be vested) to start harvesting.

From whenever you had the XEM sent to your account was when the "Vesting" period started. So that time minus 24 hours is the amount of time you have to wait for the 10% of total to show up.