search

pi-node / instructions

254 stars 154 forks source link

why there are 3 failed connections for port 31402 on https://dashboard.pi-blockchain.net/ #169

Closed jackpinode closed 3 years ago

jackpinode commented 3 years ago

My node had been running well for 5 months until July 30. On July 30, the Node can't be open normally, even after clicking Reload, it can't be back displayed normally. Then on July 31, the computer was reset via clicking recovery, but the node still can't display normally. On August 1, the computer was reset to a new device, then since August 2, the node is stuck on consensus container enabled: No On August 8 (yesterday), the number of failed connections to port 31402 is 1, today is 3 on https://dashboard.pi-blockchain.net/. I checked the ports, all ports are open (I know how to setup the ports because I have run Node for 5 months since Feb 27). Can anyone give the advice for why there are failed connections to port 31402 on https://dashboard.pi-blockchain.net/. Thanks!

jackpinode commented 3 years ago

Node running Before July 30

jackpinode commented 3 years ago

Problem 1 Problem on July 30

jackpinode commented 3 years ago

Problem 2 After computer reset on July 31

jackpinode commented 3 years ago

Node troubleshooting After computer reset to a new device on August 1 and on August 2 showed the troubleshooting results

jackpinode commented 3 years ago

Number of failed connection to port 31402 Failed connections to port 31402 today (August 9)

jackpinode commented 3 years ago

Port scan All ports from 31400 through 31409 are open from https://www.ipfingerprints.com

ihatejam commented 3 years ago

Since you started over, this node installation is new to the network - Please leave it running as it is now, and wait for it to be recognized as a node candidate - just like you did with your original node device. Once it is recognized as a viable node candidate, the consensus container will be sent down to your device. This could take a while to happen.