NEM Supernode Rewards Program

http://46.252.24.18:7890/node/info
http://46.252.24.18:7880/nr/metaData

Seems either the software is not running or the ports are not open.

And the node name is?

As far as I can tell we have gone through the entire debian 8.4 tutorial without skipping anything. How do I test if the software isnt running and if so, how to execute it? Same for the ports. Thanks

to check if the port is open use

https://portchecker.co/check

to check if NIS is running, use the “top” command in a command window and look for java processes.

Hi there! Do you have instructions how to set up supernode on VPS like hostus (they have pretty nice price). I see that instructions for set up supernode on Azure and AWS are done and thanks for that. But when I tried to calculate price for VPS it seems it will has much higher price than it is e.g. at hostus. Thank you.

Here is a tutorial:

1 Like

we started the script manually. Seems to be running now. We still get error messages: http://46.252.24.18:7890/node/info

something is wrong with the starting script. Any idea on how to locate the problem an fix? Currently we have to manually start the script after every reboot. Thx.

what error messages?

no error messages currently. so now we await the tests. Thanks.

Hi BloodyRookie.
For my supernode NEMczech please change ip 213.192.24.194 to 40.68.162.237
I also sent message to your NEM account. Thanks.

Node didnt pass the test again. Nodes name is nemster. Any clues?

it will pass the tests next round except for the balance test. The balance is 0!

Already done.

1 Like

Thanks. Does it mean that for round 2648 responsiveness of my node NEMczech (VPS on Microsoft Azure) will fail? On tab responsiveness for actual round I can see 0/10 and total time 171 ms. Or Am I wrong and it still can pass that round?

Failing all tests but since the ip was changed not long ago, that is ok. Just give it 24 hours.

OK i let it settle for 24 hours. But round 2647 passed all tests and that round run on the new IP (at least I think).

vested balance on account is sufficient. I double checked delegated pr. key is saved in supernode-servant/config-user.properties + nis-ncc/config-user.properties. Enrollement message has been sent correctly. Am I mixing something up?

vested balance not of importance, the overall balance is.
what is the main account for the supernode?

this is the public key: 8f59f6cff89f71d8358828f4343373e5d3093066a86a6a51507e2d6f3cee1a35

was asking for the main acount’s address.