Mining issues with v2.1.2

I’m relatively new to mining, but I was without any issues up until 2.0.9. I updated to 2.1.2 and I’m now seeing the following. Port forwarding/firewall is configured correctly afaik and hasn’t changed.

2021/05/03 09:02:36.549610 ←[0;31m[ERROR]←[m GID 28, failed to parsePEMBundle: no certificates were found while parsing the bundle
2021/05/03 09:02:42.299373 ←[0;31m[ERROR]←[m GID 1, POST request: Post "http://mainnet-seed-0007.nkn.org:30003": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2021/05/03 09:02:42.299373 ←[0;33m[WARN ]←[m GID 1, Can't get successor address from [http://mainnet-seed-0007.nkn.org:30003]
2021/05/03 09:02:47.307901 ←[0;31m[ERROR]←[m GID 1, POST request: Post "http://mainnet-seed-0025.nkn.org:30003": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2021/05/03 09:02:47.307901 ←[0;33m[WARN ]←[m GID 1, Can't get successor address from [http://mainnet-seed-0025.nkn.org:30003]
2021/05/03 08:31:55.119218 ←[0;33m[WARN ]←[m GID 126, Remote node 0[email protected]tcp://18.222.96.197:30001<18.222.96.197:30001> stops because of error: remote node id should be c8a12321eea3940f263fb7ccd91e3f2f12236d353d34ee38696852dc2f9b1519 instead of 0138b4254804a68d6298744e33423e87860ee196ecdf892622eb19b7901d051e
2021/05/03 08:32:04.083446 ←[0;33m[WARN ]←[m GID 198, Handle proposal error: wait for proposal timeout
2021/05/03 08:32:13.101273 ←[0;32m[INFO ]←[m GID 104, DropTxns: 0 txns (0 bytes) in txpool, no need to drop
2021/05/03 08:32:14.247521 ←[0;33m[WARN ]←[m GID 198, Handle proposal error: wait for neighbor vote timeout
2021/05/03 08:32:24.340581 ←[0;33m[WARN ]←[m GID 198, Handle proposal error: wait for neighbor vote timeout
2021/05/03 08:32:33.101755 ←[0;32m[INFO ]←[m GID 104, DropTxns: 0 txns (0 bytes) in txpool, no need to drop
2021/05/03 08:32:34.399503 ←[0;33m[WARN ]←[m GID 198, Handle proposal error: wait for neighbor vote timeout
2021/05/03 08:32:54.080326 ←[0;35m[FATAL]←[m GID 127, [nknd.go:L325 func6()] Node has lost connections to all neighbors. This is typically caused by loss of Internet or firewall.

Any ideas how to fix these errors would be appreciated. Thanks

You have only given a piece of the puzzle here. It would be advantageous to anyone wanting to help you to explain what the situation is here.

I will assume you are operating on your home network.

If your router has uPnP, you do not need to set up manual port forwarding. This can cause issues with connection. I gave my machine running the node a static local ip address on my network and this seems to have alleviated the random connection issues. ISP providers will also change your external ip from time to time, for home service there isn’t much you can do about that. My suggestion is to power cycle your modem and router, see what happens. Also check your security software to be sure the node isn’t having it’s capabilities limited.

Honestly it looks like a connection issue, and if it was working fine before then it stands to reason something has changed on your system or network, causing the link to be broken.

The more information available to us, the easier it is to troubleshoot. Is your node local or cloud based? That sort of thing.
There are a lot of people who can help if you give us the ability to.

I had similar problems. Neighbours wouldn’t connect anymore after upgrading from 2.0.9 to 2.1.2. I seem to have fixed it by deleting my ChainDB folder.

HTH

Hello, this problem is caused by random disconnection of your internet. Run the command to restart it a few times, it will work again.