Next round it will have a ping.
TehSuperNode2 is not getting a ping result as well. Appears to have passed all other tests in last pass.
TehSuperNode2 will have a ping in round 802.
1 Like
have setup two supernodes. one seems to be fine and all checks are ok. now
second node uses the same private delegated key as first because there are for
3 supernodes xem in the account which delivers the priv. key.
but that seems not to work
have i to setup a new computer with another account or could i use the delegated private key from
a secondary account in the same wallet which I could fill with 3 mio xem?
yes, a different account is needed, both accounts may reside in the same wallet.
(copied from other thread since i posted it in wrong thread)
General Remark:
I see nodes joining the supernodes program with a balance less than the required 3M xem. Remember that you cannot get a payout with a balance not fulfilling the requirements. It therefore does not make sense to have such a node enroll for the supernodes.
If people keep adding nodes that do not meet the balance requirement, we might have to change our strategy and reject any enrollment for which the balance of the supplied delegated key does not meet the requirement.
(copied from other thread since i posted it in wrong thread)
The following nodes do not meet the balance requirement of 3M xem. Please either fix this or tell me to temporarily deactivate the node in the db. It can be reactivated at a later point so there is no harm in deactivating it for some time.
supernode2.elhanan.nl
nem.servehttp.com
Xnode (deactivated)
EU1.gondor
supernode1.elhanan.nl
EU2.rohan
greatlakes
nemph
NIS1338
㊃
㊅
⓬
⓭
⓮
Fund3
Fund4
Fund5
Hotel-California
ex86
Bungakubu2
MsUs
If the node keep failing the balance test for another week they will be deactivated.
Can you temporarily deactivate Xnode as I no longer have the required balance. tks
done.
thanks for the answer. as i experienced, the hostus.us node from honkong is by far not reliable (it has failed completely the 4th time in 4 days…hardware failure of network or server). thats unacceptable. so i would like to change the IP of the himmelsfaller supernode from 103.192.177.252 to 138.201.159.103. the new server seems from a much more reliable provider. i only can say stay away from hostus.us honkong. i’ll look for another provider for a second supernode.
What? I got 3 HostUs HongKong nodes running:
http://supernodes.nem.io/history/search/HongKong1
http://supernodes.nem.io/history/search/HongKong2
http://supernodes.nem.io/history/search/HongKong3
All of them are 2GB nodes and they are doing extremely well 
What provider are you using now?
Edit: HK-node also is a HostUs node in HongKong (not mine) and it is doing well too:
http://supernodes.nem.io/history/search/HK-node
Maybe you had something misconfigured?
no misconfiguration. first I was told that there was a network problerm, then it was a server problem and they told me then that it was fixed and now i can’t again connect to my server. the configuration was ok and since yesterday it passes 4 times the test. but now i can’t reach my server (ip: 103.192.177.252), couldn’t even ping it. it is a 2 Gb node. i have now a 1 Gb server from hetzner and changed the name to himmelsfaller. maybe i should demand another server from hostus, because mine seems broken (hardware failure…).
Ok. I asked the hostus support to change to a new server. Don’t know if I’ve to do a fresh setup as soon as I get a new server. I’ll let you know as soon as the new one is ready. I’ve sent an IP change request from my NEM wallet but if hostus can provide me with a new server with maybe the same IP it wouldn’t be neccessary to change the IP. I’ll let you know. Thanks!
Hey,
In had to re-enroll my supernode because I had to switch hosting services.
But I saw that there is a switch IP message I should have used instead of sending a completely new enroll message. Is that a problem?
Excuse me. Please tell me. Meet the conditions of the super node , it issued the request , but becomes a " Responses / Requests 0/10 " , not as the applicant . In addition , all the other data will become a " No results to show ."
What is the cause here ?
This environment is Windows server2012.
Well you have to tell me the alias of your supernode so i can check in the logs
Do you have NIS and servant running?
Thank you for the reply .
My alias is " 27.134.243.236 DRAGON " .
You supplied the wrong public key. Please check if you really were supplying the delegated public key in your enroll message. If not, please send the correct delegated public key to the account
NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3
from the account you used for the enroll message.
The first to like key was wrong that was sent , but we are sending the right one for the second time , or was useless ?
What can I send once again correct things ?
Here ? ↓
NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3
It has been sent earlier .
Verification please .