Question

Handshake address lost connect permissions because of the computer was shutdown without the previously stop of the node. I saw the problem sometimes.

Answer 1

Generally speaking this is because the node did not store which address in its wallet it should use to make these connections. The handshakelocal runtime parameter can be used to tell it to use a particular address.

Comments

Address phisicaly lost the permission: was connect in its list permissions and this is dissapeared

---

In that case it's likely the permission never entered the blockchain. Is it possible mining stopped because the "mining requires peers" setting was true (this is the default) and the setup phase ended?

---

It worked some weeks before the case, on 3 nodes. Blockcount was much more than 10000. The address got its permissions in the time of node creation. And it was not changed after it.

---

OK, that is weird. Was the address shown with connect permissions on other nodes, using the listpermissions API?

---

Sure. It was the first address that was created with the node. The permission was taked on 1st node (admin) during process of the node creation.