Notes on updating to v1.1.2

Nodes & Mining
#1

Some notes from updating 17 of my own nodes to v1.1.2 over 4 platforms (DO, Linode, GCP, AWS):

  1. If your node was launched via NKN official 1-click on DO, there is nothing you need to do. It will automatically update and just work.

  2. If your node was launched via NKN Official 1-click on GCP and AWS, the NKN software itself will be updated automatically.

    BUT you need to add firewall rules in admin console to allow opening port 30004 and 30005. In AWS, it can be configured in Security Group that is associated with your VM. In GCP, it can be configured in Firewall Inbound Rules in Network configuration.

    We are in the process of updating the 1-clicks, so once those are approved any new node launched via 1-click should already include the latest firewall rules.

  3. If your node was launched via NKNx “Fast Deploy”, you need to log into your VM, and run these two commands as root user. You only need to do this ONCE.

    ufw allow 30004
    ufw allow 30005

    In addition, if your “Fast Deploy” nodes were on GCP or AWS, you need to do the same firewall setting in admin console as above point 2.

  4. I forgot if my node was launched via NKN official 1-click or NKNx Fast Deploy, how can I find out?

    If you log into your VM, and run command “ls /home”. If you find folder nkn then it is 1-click; if you find nknx then it is Fast Deploy.

  5. If you do need to log into your VM or droplet, it is advisable to use this opportunity to update the operations system so all security patches are applied. You can run the following as root user:

    apt-get update
    apt-get upgrade

  6. To check if your node is updated properly, you can use

Happy updating!

#2

Add Firewall rules in Google Cloud admin console (allow TCP ports 30004 and 30005 for all inbound traffic)

13 PM

52 PM

19 PM

25 PM

48 PM

#3

Add Firewall rules in AWS (allow TCP ports 30004 and 30005 for all inbound traffic)

31 PM

04 PM

38 PM

#4

The following works for my Raspberry Pi 3 at home as well. But please do remember to configure your router’s port forwarding to add TCP port number 30004 and 30005.

#5

All my nodes were interrupted when I upgrade to 1.1.2, I allowed these ports like that, but It does not works

2019/12/21 04:12:20.635469 [INFO ] GID 90, Received stop message from remote node <45.32.164.150:30001>
2019/12/21 04:12:24.403116 [WARN ] GID 141, Ping <159.65.146.118:30001> error: Wait for reply timeout
2019/12/21 04:12:24.519266 [WARN ] GID 203, Ping <104.248.114.52:30001> error: Wait for reply timeout
2019/12/21 04:12:24.607428 [WARN ] GID 250, Ping <54.224.255.4:30001> error: Wait for reply timeout
2019/12/21 04:12:24.785955 [WARN ] GID 277, Ping <45.32.164.150:30001> error: Wait for reply timeout
2019/12/21 04:12:25.727133 [ERROR] GID 310, Update successors error: neighbor list is empty
2019/12/21 04:12:28.193557 [ERROR] GID 310, Update successors error: neighbor list is empty
2019/12/21 04:12:29.315587 [ERROR] GID 311, Update predecessor error: neighbor list is empty
2019/12/21 04:12:29.785855 [WARN ] GID 285, Handle proposal error: Wait for proposal timeout
2019/12/21 04:12:30.666958 [ERROR] GID 310, Update successors error: neighbor list is empty
2019/12/21 04:12:32.457140 [ERROR] GID 310, Update successors error: neighbor list is empty
2019/12/21 04:12:33.504019 [WARN ] GID 312, Local node has no inbound neighbor, it’s possible that local node is unreachable from outside, e.g. behind firewall or NAT.
2019/12/21 04:12:34.089214 [ERROR] GID 311, Update predecessor error: neighbor list is empty
2019/12/21 04:12:34.841597 [ERROR] GID 310, Update successors error: neighbor list is empty

#6

it might be that you need to enable port 30004 and 30005 both at operating system level, as well as home wifi router (or GCP/AWS network level).

#7

I turned off firewall, but It still does not works