Also I'm not sure now (and I can't check it), but I think name must match too.
The name can be anything, just the public key in the peers config file must match the boot key.
The name can be anything, just the public key in the peers config file must match the boot key.
4 more servers to connect to :)
43.224.35.140
43.224.35.127
45.63.123.41
45.63.121.41
I tried to enable delegated harvesting using the top server listed here. I can run the wallet using it just fine, but I keep getting an error message when I try to start delegated harvesting using that server. I'm back to delegated harvesting using my localhost. I'd like to be able to run delegated harvesting on a public node such as one of the above so that I can harvest even when my NEM community client isn't active. The only change I've made is of the server in the settings button. What am I missing?
I tried to enable delegated harvesting using the top server listed here. I can run the wallet using it just fine, but I keep getting an error message when I try to start delegated harvesting using that server. I'm back to delegated harvesting using my localhost. I'd like to be able to run delegated harvesting on a public node such as one of the above so that I can harvest even when my NEM community client isn't active. The only change I've made is of the server in the settings button. What am I missing?
Which error message?
You can try this:
"To activate "delegated harvesting", please stop local harvesting first. Then select
Please add:
ec2-54-93-217-25.eu-central-1.compute.amazonaws.com (port 7890)
I was able to set delegated harvesting to the above node and as far as I can tell it is working perfectly. The proof will be when I actually harvest a block, which should happen in the next day or so. I'm not sure why the other node I tried didn't work. Perhaps it was full.
Once I have some time I plan to try to set up a node on amazonaws. Hopefully that won't be too complicated.
4 more servers to connect to :)
43.224.35.140
43.224.35.127
45.63.123.41
45.63.121.41
I tried to enable delegated harvesting using the top server listed here. I can run the wallet using it just fine, but I keep getting an error message when I try to start delegated harvesting using that server. I'm back to delegated harvesting using my localhost. I'd like to be able to run delegated harvesting on a public node such as one of the above so that I can harvest even when my NEM community client isn't active. The only change I've made is of the server in the settings button. What am I missing?
Try other, there may be some that are not harvesting.
Is there any setting to allow more harvesters in a NIS?
Is there any setting to allow more harvesters in a NIS?
NIS -> config.properties -> nis.unlockedLimit = 1 (dont go higher than 5 or 10 for now, this stills needs some testing)
it is recommended to create a config-user.properties though and copy the settings which you want to change there, before you change them. then do your custtom settings and save the file. NIS will use your custom settings in config-user.properties then and you dont have to change the config.properties.
Anyone who connected to my nodes before about 9pm this evening will have to restart delegated harvesting I think… All my nodes got shut down cos I forgot to pay the bill lol they are back up now so it's first come first serve again 
Anyone who connected to my nodes before about 9pm this evening will have to restart delegated harvesting I think.. All my nodes got shut down cos I forgot to pay the bill lol they are back up now so it's first come first serve again :)
Ha ha, I was one of them. I just restarted delegated harvesting. So it's as simple as stopping delegated harvesting and then starting it again, entering the wallet password both times?
My wallet dashboard gave no indication of the node I was using being down. That would be a good feature to add. Otherwise you're harvesting blind and don't know for sure if you're actually harvesting. Even better would be to have it automatically check for the next available node if the one you were using went down. Maybe you can input a list of your ten favorite nodes that it works through. Food for thought for the developers :)
In any case, thanks for posting this so I knew to restart delegated harvesting on your node :)
Funny: my spouse was looking over my shoulder when I was staring at my NEM wallet, and he wanted to know what "stop delegated harvesting" meant. At first thought it was some kind of political slogan, before realizing it was a menu item 
Anyone who connected to my nodes before about 9pm this evening will have to restart delegated harvesting I think… All my nodes got shut down cos I forgot to pay the bill lol they are back up now so it's first come first serve again
Ha ha, I was one of them. I just restarted delegated harvesting. So it's as simple as stopping delegated harvesting and then starting it again, entering the wallet password both times?
My wallet dashboard gave no indication of the node I was using being down. That would be a good feature to add. Otherwise you're harvesting blind and don't know for sure if you're actually harvesting. Even better would be to have it automatically check for the next available node if the one you were using went down. Maybe you can input a list of your ten favorite nodes that it works through. Food for thought for the developers
In any case, thanks for posting this so I knew to restart delegated harvesting on your node
I was thinking something similar for the mobile app but for verifying that the data your getting is correct ie. The node you on is not on a fork or purposefully giving you wrong data… What you said would tie in perfectly… You could enter 3-5 IPs or there about and ncc will cross reference the data and disconnect you from a node if it isn't giving the same ddata as others… Also, like you said of one goes down you could auto switch harvesting to a good one… This would also prevent the crap cfb is on about ensuring you are always connected and harvesting on a good node. This would be quite easy with the ncc/nis combo I would think?
No bother
Should be moved here, no? ::)
Have you guys seen this thread?
https://forum.ournem.com/general-discussion/harvest-on-my-node!/
updated
Should be moved here, no? ::)
Have you guys seen this thread?
https://forum.ournem.com/general-discussion/harvest-on-my-node!/
updated
I think that's something bit different. Point of this thread should be creating community-fueled peer-config, while point of the other one is to advertise people who allow harvesting on their nodes.
harvesting is not something that will be possible on most nodes, as most owners, will keep unlockedLimit at 1.
if any of you is willing to try, you could try running a node where NONE of base nodes are included (I mean alices and yakuza).
(They probably will be included on list of peers very quickly anyway).
Hi, as with all my posts apologies for the noobiness, but anyone want to take a moment to explain:
a) how one sets up a dedicated vps node
b) what this involves in terms of + and - for the person doing so?
Much appreciated!
esc
Hi, as with all my posts apologies for the noobiness, but anyone want to take a moment to explain:
a) how one sets up a dedicated vps node
https://forum.ournem.com/tutorials/how-to-setup-a-node-in-raspberry/ - if you want it on your Rasp Pi - not a VPS but I thought it might help
https://forum.ournem.com/vps-nodes/how-to-setup-a-node-in-vps/
https://forum.ournem.com/vps-nodes/how-to-create-an-amazon-ec2-vps/
https://forum.ournem.com/vps-nodes/how-to-easily-configure-and-install-nem-on-an-amazon-ec2-vps/
b) what this involves in terms of + and - for the person doing so?
+ you properly support the network 24/7 and your effort makes NEM network more resiliant to all sorts of bad stuff :-D
+ you can reliably harvest by delegation without depending on someone else
+ if/when the rewards for running a node start coming - you'll like it even better
+ ability to choose some cool name for your node ;-)
- it takes some time and knowledge to set it up and also potentialy some money since quality VPS is not free
Hi, as with all my posts apologies for the noobiness, but anyone want to take a moment to explain:
a) how one sets up a dedicated vps node
https://forum.ournem.com/tutorials/how-to-setup-a-node-in-raspberry/ - if you want it on your Rasp Pi - not a VPS but I thought it might help
https://forum.ournem.com/vps-nodes/how-to-setup-a-node-in-vps/
https://forum.ournem.com/vps-nodes/how-to-create-an-amazon-ec2-vps/
https://forum.ournem.com/vps-nodes/how-to-easily-configure-and-install-nem-on-an-amazon-ec2-vps/
b) what this involves in terms of + and - for the person doing so?
+ you properly support the network 24/7 and your effort makes NEM network more resiliant to all sorts of bad stuff :-D
+ you can reliably harvest by delegation without depending on someone else
+ if/when the rewards for running a node start coming - you'll like it even better
+ ability to choose some cool name for your node ;-)
- it takes some time and knowledge to set it up and also potentialy some money since quality VPS is not free
I try to keep my clearly tutorials for newbies, because also am one. ;)
updated
Thanks. Please add it to first post.
Done.
Clould tell how you configured a Freenom DNS?
I tried to put a A record, it accepts, but the lookup give error.
You only have to put the public IP you got from Amazon (not this ec2-xx-xx-x-xxx.eu-central-1.compute.amazonaws.com) in both DNS A-record-fields.
So that's what I did, but it seems you have to open a ticket to configure them manually.
http://niss.ga:7890/node/info
thanks!
Thanks. Please add it to first post.