So, looks like some key in the config is wrong. Please check all config entries.
NEM Supernode Rewards Program
it seems to work now according to the extended info. Still the node is failing all but the balance test. Was it enrolled with the new ip?
thanks again for your help
You don’t need to enroll again, you need to change the ip. So send a transaction with the message
change ip 46.252.27.237 to 45.76.38.124
to the noderewards account.
Hello, BloodyRookie.
I have a question.
Yesterday I tried to register the node.
My node is registered on this website (https://nemnodes.org/nodes/)
But my node is not registered on this website (https://supernodes.nem.io/).
Why is this?
The transaction hash is http://explorer.nemtool.com/#/s_tx?hash=2d44eb95ef285402cf74d2e358ae15857b0bb811af8d24cbc5a3fac9520a25e6.
The name is TEST01.
Your main account has only ~500 xem in it. To take part in the supernode program it needs to have at least 3M xem.
1 Like
Thank you!! @BloodyRookie . I did it!
And please change IP of these supernodes.
change ip 45.32.134.182 to 212.24.107.224
change ip 144.202.98.59 to 89.40.13.144
change ip 63.209.33.164 to 89.40.14.152
change ip 149.28.196.255 to 212.24.102.126
change ip 149.28.197.154 to 176.223.136.243
change ip 45.77.219.43 to 94.176.239.23
change ip 149.28.198.184 to 89.47.164.173
change ip 64.154.38.251 to 195.181.243.57
change ip 45.63.89.12 to 109.235.65.200
change ip 149.28.197.243 to 94.176.237.211
I already sent enroll message to NAFUND address,
the tx hash:
http://explorer.nemtool.com/#/s_tx?hash=aa2077aea6c4613760358a695561249eb0add1788cabde4c65c4f6da4f666276
http://explorer.nemtool.com/#/s_tx?hash=02b61e0b3880032af1219943e7bcc3eead4ec25c10e62fe6f45a0e0c3591f1f2
http://explorer.nemtool.com/#/s_tx?hash=05ede5710004e9290654f174f0d57772dc3e1cacc85f208ea24fd0c2a4e47016
http://explorer.nemtool.com/#/s_tx?hash=7157da82ccff7ad4c67cdadf5ae738fafd0c133e2066d331225dab0e19ab273d
http://explorer.nemtool.com/#/s_tx?hash=c88a44e435a1b56222ea5f5ead94ec7f43f3f3da9314125de36da3050b29bda4
http://explorer.nemtool.com/#/s_tx?hash=f6d14e71f99b3ec0b37fc32b777aaa30af1b60ca0ce5b57e0f305b7b963a8049
http://explorer.nemtool.com/#/s_tx?hash=cc7072f5b0e192e3eab61c7e917d57f0481fd4c668e075a2c18de8890bb5eedf
http://explorer.nemtool.com/#/s_tx?hash=8c67579caa8eefee07f1a73b2e61c635617530cab5a466e51e089e12784c2464
http://explorer.nemtool.com/#/s_tx?hash=493767cccfe969d443678f0e3fe7cd172cdd9d9c7829fd179463a677815e9e13
http://explorer.nemtool.com/#/s_tx?hash=77efe443f24155e9bfbdc627e51846490d2796cf9e619aaa6318437ee589d684
Thanks a lot!
How many time for getting the change ip effective ? since 2 days now and the ip at supernodes.nem.io is not updated. Thank you
The test right now is at 10MBit/s. It is very possible it will become lower later. Right now we are stressing the network.
https://appsync.biz/dafont/ , https://showbox.bio/ , https://www.oovoo.onl/adam4adam/
Hi, i noticed that my enrollment public key harvesting is not the same as my public key harvesting because is changing in different version of wallet and since i have switched to a new ip and new installation i don’t have my enrollement prive key harversting… why different wallet version change the harvesting key ? so i have to process a new enrollement ? @BloodyRookie thank you
I had this problem in the beginning. Your delegated private key is not linked to your normal private key in the wallet. The wallet will generate a delegated public key upon loading or making the account private key. You then send a transaction making the delegated private key the harvester for the account private key. Every time you reload the private key into a new wallet you will generate a new delegated private key.
The original delegated private is however linked into the blockchain with the transaction you have made.
If you lost your original delegated private key only solution is disable delegated harvesting and send a new transaction linking the new delegated private key to the private key.
Thank you for your explanation, good i have found the original delegate key and private so now it would be ok i have sent a msg to change the ip with the new ip and same public key would be ok i hope
@BloodyRookie Hi BloodyRookie. I need some help on supernode https://supernodes.nem.io/details/787 . The supernode is failing for quite some time. From the logs, there are no memory/connection issues. Is there any other ways I can check for possible failure issues? Thank you in advance 
Ok, which supernode is yours?
Can you paste the tx hash of the enroll message for the new entry?
Looks like it is not failing any test in round 5525. Did you restart NIS?
Why is so slow to get support on this channel?node https://supernodes.nem.io/details/621
The tx of my new ip http://explorer.nemtool.com/#/s_tx?hash=d0ba0e3010525178d3c50170e73409dca60dd3c4a9daeba155f7ba0baa4b959f
Thank you
Changed your ip manually in the db.
1 Like
Thank you!