NEM Supernode Rewards Program

The NIS version has nothing to do with the java version.
If your NIS still reports 0.6.91 after the upgrade, you probably did not remove the old NIS jars.

Your NIS reports the correct version:

http://185.166.239.27:7890/node/info

Ok, I’ll look at the next performance results.
Thanks for help!

http://85.172.55.221:7890

Where is my mistake?
All done on the FAQ help. The ports are open.

Obviously the node cannot be reached.
First try:

http://127.0.0.1:7890/node/info

and

http://127.0.0.1:7880/nr/metaData

on the computer to see if it works locally.
If that works, there must either be a misconfiguration of the router / windows firewall or your provider does something to prevent incoming calls.

Also, does the port checker tool

http://www.yougetsignal.com/tools/open-ports/

indicate an open port for ports 7880 and 7890?

Port 7880 is open on 85.172.55.221.
Port 7890 is open on 85.172.55.221.

http://127.0.0.1:7890/node/info

{“metaData”:{“features”:1,“application”:null,“networkId”:104,“version”:“0.6.93-BETA”,“platform”:“Oracle Corporation (1.8.0_144) on Windows 10”},“endpoint”:{“protocol”:“http”,“port”:7890,“host”:“85.172.55.221”},“identity”:{“name”:“Super.node.Krr”,“public-key”:“f08e6e99f5347844ce49ed3f3a37db4fd55d761260e57f3307e16691b223201f”}}

I need to change the external IP 85.172.55.221 in this file “config.properties”? On 127.0.0.1 ??

P / S. If I succeed, I will write the instructions in my language. Especially not clear with the keys, which one is closed which is public with a password. It is not better to name one for Harvesting another simply public key. I’m talking about NanoWallet. It is difficult to configure NIS. =))

NDAAZK-HTERGU-DE257Q-FD5B4O-XR7RJX-RGDGBS-6EC6
So I poyan completely by accident that there must be a request to send? Where the host is specified, the name, the key that is hidden under the password. Sended two letters did not know which key is correct =) I’ve been trying to set everything up for a week … Help people good.

I still don’t see a reply to e.g.

http://85.172.55.221:7890/node/info

So there still is something wrong.

1 Like

I disabled all supernodes running a NIS version prior to 0.6.93. I can easily enable them again once the owner upgrades NIS. There is no need to enroll again after the upgrade. Just leave a message here.

Hi Denis, as noted by BR, required ports (7890, 7880) are still closed to external connections, the information @ this link may help to resolve issue.

1 Like

My mistake was that I did not run runservant.bat because of which port 7880 was closed. Right now, it seems like everything works and everything is open. Frankly, without you I would not have configured … The instructions do not help at all and only confuses =)))

What does this program do?

Should it be updated?

servant check node status of other nodes
and let other nodes check ur node status

this checks/results are the base if ur supernode get rewards or not

the servant need no update since a long time
they way he work is not affected by small nis changes

i want to say a great thx to BloodyRookie
who do a awsome job here at support supernode owners!

1 Like

supernodes.nem.io

chain.nem.ninja

Thank you, you understand. And how to see that everything is working fine? My site does not appear, it means that something is wrong again? Or you just have to wait 1 hour?

http://85.172.55.221:7890/node/info

and

http://85.172.55.221:7880/nr/metaData

I see the local address. There is no page on the outside. That is how it should be?

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

both work, so the node is correctly configured.

1 Like

{“metaData”:{“features”:1,“application”:null,“networkId”:104,“version”:“0.6.93-BETA”,“platform”:“Oracle Corporation (1.8.0_144) on Windows 10”},“endpoint”:{“protocol”:“http”,“port”:7890,“host”:“85.172.55.221”},“identity”:{“name”:“Super.node.Krr”,“public-key”:“f08e6e99f5347844ce49ed3f3a37db4fd55d761260e57f3307e16691b223201f”}}

shows name: Super.node.Krr

but the supernode browser dont know such a node

so maybe the name u did enroll ur supernode and the name u configured at ur supernode ar not the same?

1 Like

As the full node, it is displayed with up time of 8 hours, so is not enroll processing done?

And when will it appear? Here
supernodes.nem.io

this is normal ?
2017-08-21 03:15:39.749:WARN:oejh.HttpParser:qtp26722308-16: badMessage: 400 Unknown Version for HttpChannelOverHttp@9b998{r=0,c=false,a=IDLE,uri=-}
2017-08-21 03:16:16.722:WARN:oejh.HttpParser:qtp26722308-15: badMessage: 400 Unknown Version for HttpChannelOverHttp@a7552a{r=0,c=false,a=IDLE,uri=-}
2017-08-21 04:20:24.715:WARN:oejh.HttpParser:qtp26722308-16: badMessage: 400 Unknown Version for HttpChannelOverHttp@ce5d29{r=0,c=false,a=IDLE,uri=-}
2017-08-21 04:24:01.157:WARN:oejh.HttpParser:qtp26722308-15: badMessage: 400 Unknown Version for HttpChannelOverHttp@184b1a9{r=0,c=false,a=IDLE,uri=-}
2017-08-21 04:24:06.633:WARN:oejh.HttpParser:qtp26722308-16: badMessage: 400 Unknown Version for HttpChannelOverHttp@f1d2e8{r=0,c=false,a=IDLE,uri=-}
2017-08-21 04:25:12.927:WARN:oejh.HttpParser:qtp26722308-11: badMessage: 400 Unknown Version for HttpChannelOverHttp@7550d7{r=0,c=false,a=IDLE,uri=-}

Did not quite understand you, where shows ?? At 127,0,0,1 yes there everything is visible. Just the first time I do not understand how it should be. =))

Thank you, the help has helped.

that is strange