My new node has been in syncing state for the last 2 days. Any idea what’s going on?
If you start from scratch, indeed it can take up to a few days to sync up to the latest blockchain height. It depends on your Internet connection and the processing speed of your node.
When you check your node via nstatus.org, can you see your node’s block height is increasing and how far from the latest network height?
Sir Zbruceli
I am a starting miner, but I believe that i did the installation well. Gladly i have some programming knowledge.
I have downloaded the latest node version v2.1.6. and it works when I login to http://127.0.0.1:30000/web/nodeStatus.
I have made of course the local wallet, and transfer 50 KNK for making the node (it needs only 10 NKN, I know).
I was not happy, that for 10 NKN (3,- euro) the transfer cost me over 30,- euro total. Is it not beter to give the 10 NKN first to start new miners, and take it back later?
The Node status stays on “chain db sync started”. Every time it stops and says “Remote node has stopped”, but my internet connection works perfect.
The ISP has UPnP on and have an Public IPv4 Address.
The computer firewall has except NKN nknd.exe executions.
I am already for days busy but with no realy results.
So what can I do??
Hi
Thanks for trying out NKN node.
-
10 NKN for starting node: this is introduced earlier this year, specifically to defend against a malicious attack that gains unfair advantage in gaining much more mining rewards than all other honest miners. However, if you want a low cost 10 NKN mainnet tokens to start mining, nknx.org has fast deploy service that will supply you with 10 NKN mainnet token at cost with very little fee ($1 or so).
-
Did the nkn node stopped entirely, or just printing out error messages? If the latter, this is normal since our logging service print out a lot of stuff. If the node actually stopped, then you might want to check your home router’s firewall settings to open ports for 30001-30021. Then the outside nodes can reach your home node, to enable properly syncing and operation.
If you have further questions, you can also try our Discord channel where there are more miners and community developers who could help:
It was printing some messages, also error messages. The node actually stopped indeed. What do you mean with “home router’s firewall”, the one from my computer or the ISP???
On my computer I already have insert two rules for the nknd.exe, one for TCP and one for UDP.
ON the ISP I have Port Forwarding added new manually rules, from 30001 till 30005 for TCP and for and UDP, must i do this till 30021? For the ISP firewall it is standing on low, did not put new rules overthere.
Yes please add port forwarding for 30001-30021 in the ISP side, and see how it goes.
I did add the port forwarding from 30001 till 30021 both TCP and UDP at the ISP, but the same result “Remote node has stopped”. Only it toke 5 times longer before I got this message 
What can I do more???
Must I activate the DMZ???
Hello @Sveben and welcome 
You have 2 options, if you are using a devive for mining and smth else, I would recommand you to do port forwarding to this machine as Bruce explained to you. This is one technique.
The other technique if you are using a dedicated machine such as a Pi, is to use a DMZ.
A DMZ is one IP in your networking who’s not protected at all. If your device only run a NKN node using a DMZ is easier as everything is handle by the OS of your node so you don’t have to figure out other configurations.
I hope it helped you
Hi again.
As you already can read, I have done already that, what Bruce explained to me
I use an windows 10 computer, so better not to use the DMZ, I think.
Why is it not working???
I have the same problem
Ports are forwarded, everything has been done according to the instruction. Checked five times.
Hello,
could you paste your log file? (nkn-node.log file)
This is the part of my log file:
2021/09/22 01:00:40.994825 e[0;32m[INFO ]e[m GID 12413, Pruning height: 172589, length of refCounts: 1092
2021/09/22 01:00:40.994825 e[0;32m[INFO ]e[m GID 12413, # current block height: 173613, block hash: 039fa1df0f0970e5b5081ce78610e81eb2fa3c57b53be5d22f8b1d04251af073
2021/09/22 01:00:41.151968 e[0;32m[INFO ]e[m GID 320, Receive block proposal b3568e32d2c86c306eaf1daf6e6fdc602a279bbfcd5a19d9edb530a4f1f78ce3 (3 txn, 5100 bytes) by a46af23059d4d3b779646e6dbf8ace811852442380c6efd20a49e7ab70f8af1d
2021/09/22 01:00:41.195007 e[0;32m[INFO ]e[m GID 12413, RefCount height: 173614, length of refCounts: 2249
2021/09/22 01:00:41.306109 e[0;32m[INFO ]e[m GID 273, Error handling msg: block b42bc49a251ac06b3488b50507b0ffb35bf02544ffea69765126b94c82782b7c is not finalized yet
2021/09/22 01:00:41.551331 e[0;32m[INFO ]e[m GID 12413, Pruning height: 172590, length of refCounts: 1849
2021/09/22 01:00:41.551331 e[0;32m[INFO ]e[m GID 12413, # current block height: 173614, block hash: 03ec668b1fb1478422e56c49ebbd53632e837a90069d8c83a2c045c5b8f71c93
2021/09/22 01:00:41.651422 e[0;32m[INFO ]e[m GID 12413, RefCount height: 173615, length of refCounts: 1279
2021/09/22 01:00:42.104833 e[0;32m[INFO ]e[m GID 12413, Pruning height: 172591, length of refCounts: 1989
2021/09/22 01:00:42.104833 e[0;32m[INFO ]e[m GID 12413, # current block height: 173615, block hash: 4aedaeb05252a65dad2a73a38f767bccd49bf1db6f22859ba3bd111218a566c2
2021/09/22 01:00:42.936589 e[0;32m[INFO ]e[m GID 273, Error handling msg: block b42bc49a251ac06b3488b50507b0ffb35bf02544ffea69765126b94c82782b7c is not finalized yet
2021/09/22 01:00:43.191821 e[0;32m[INFO ]e[m GID 273, Error handling msg: block b42bc49a251ac06b3488b50507b0ffb35bf02544ffea69765126b94c82782b7c is not finalized yet
2021/09/22 01:00:43.632221 e[0;32m[INFO ]e[m GID 82028, Remote node 660d6c0db0ec6cd1100ee8c421846f5e59fe30d72bfd1e1f74db9caf2bdd6c08@tcp://140.82.30.114:30001<140.82.30.114:30001> stops
2021/09/22 01:00:44.094641 e[0;32m[INFO ]e[m GID 12413, RefCount height: 173616, length of refCounts: 10188
2021/09/22 01:00:44.720209 e[0;32m[INFO ]e[m GID 279, Remote node connect from 107.191.40.248:47454 to local address 192.168.1.156:30001
2021/09/22 01:00:45.869253 e[0;32m[INFO ]e[m GID 12413, Pruning height: 172592, length of refCounts: 2010
2021/09/22 01:00:45.869253 e[0;32m[INFO ]e[m GID 12413, # current block height: 173616, block hash: a50d96d96648e1c39b9dd4e95515d91a9dd3539275455ab877ec242a3ee4a540
2021/09/22 01:00:45.870254 e[0;33m[WARN ]e[m GID 12413, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.870254 e[0;33m[WARN ]e[m GID 12413, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.870254 e[0;33m[WARN ]e[m GID 12413, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.870254 e[0;33m[WARN ]e[m GID 12413, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.870254 e[0;31m[ERROR]e[m GID 9703, Sync blocks error with batch size 4: all workers failed
2021/09/22 01:00:45.870254 e[0;33m[WARN ]e[m GID 81853, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.870254 e[0;33m[WARN ]e[m GID 81853, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.870254 e[0;33m[WARN ]e[m GID 81853, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.870254 e[0;33m[WARN ]e[m GID 81853, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.890272 e[0;33m[WARN ]e[m GID 81854, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.890272 e[0;33m[WARN ]e[m GID 81854, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.890272 e[0;33m[WARN ]e[m GID 81854, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.890272 e[0;33m[WARN ]e[m GID 81854, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.910290 e[0;33m[WARN ]e[m GID 81855, Get blocks error: Remote node has stopped
2021/09/22 01:00:45.910290 e[0;33m[WARN ]e[m GID 81855, Get blocks error: Remote node has stopped
Hello!
Good news, it doesn’t seems to be related to your configuration
So far form my personal experience it happened to me once with a node and the only solution I found was just to restart the node until it reach the correct block height. Once reached everything works fine.
So I would suggest you to download a pre-pruned chain (as your chain is far from the current block) (you can found a link in this forum), replace the chain/ folder with it and start your node again. Keep a look at it, when it stop, just restart it.
My node was running for at least two days, and then I got the same shit again I’ve been working with just one node for at least a week now, without success. Every time “Remote node has stopped”. In addition, the examples are very bad and not up to date Also at NKN they are not honest about the so-called easy installation, then I am not even talking about the costs associated with it. And you never really get an answer to your questions. In other words is it just pure scam?
Well,
I won’t totally disagree with you … The windows version seems more complicated than the Linux one and there is way more documentation for the linux version. As most of the documentation for miners is written by miners and most of it using linux … it makes sense to be less developed
Still, it’s unfortunate and, to be honest, I myself feel guilty as I said that I would try to do an install on Windows to write a documentation for the wiki but … real life you know … 
So basic documentation exists, it probably could be better but there is always space to do better
For more technical help I would suggest you to join the Discord and try to have a chat with one the dev. They are really accessible and answer well structured question. You have your issue, your log, they should come with an answer easily
So now if you achieve to make your node running perfectly it would be awesome if you could share your install experience in the Community wiki to help people like you willing to join the network
I’m sorry for your bad experience and hope you’ll enjoy being part of this community
Best !
This is outrageously bad The NKN software just won’t work. Both on my computer and on my Raspbarry Pi 4 Every time “Remote node has stopped”, after it was almost finished???
Why am I not getting a clear answer?
Hello!
I would suggest you to use the All-in-One script for the install on your pi.
You can download the Chain from nkn servers (https://nkn.org/ChainDB_pruned_latest.tar.gz) rather than build it, it would fast the process.
I also tried via (nknx.org), didn’t work So I installed it manually again, using the linux-armv7.zip and the https://nkn.org/ChainDB_pruned_latest.tar.gz to speed up the process And of course the wallet.json I created earlier After running the nknd.exe process 60 times it is finally mining.
I also found out when you have ipv6 enabled your http://nstatus.org/ and https://nknx.org/ don’t work properly because they don’t recognize the IP address.
But still have a question. What can you do with the file "
Source code (tar.gz)"? Looks like it’s special for the Raspberry Pi.