Current block late for certain nodes

Created by: M5oul

I can see that Galuel and Inso nodes have frequently they current block one or two blocks late than the pool of other nodes.

That's may be why Inso node get sometime corrupted.

That's an issue because, this is an open door to blockchain forks and their are generating already generated blocks for nothing.

Where could come that problem? When nodes have a new block, they spread it to all nodes they know. May be this two nodes don't receive new blocks. They get new blocks only when they search by themselves. It could come from their network configuration which don't allow entering connections.

I tried to forward them blocks and they get same current block than the pool of nodes.

Created by: M5oul

May be https://github.com/duniter/duniter/issues/476 could solve it.

Created by: M5oul

• It's may be due to network latency. Close nodes are get directly last block.
• Or, it's could be due to peer sheet wrongly spread at re-sync process.

Created by: M5oul

It's seems to be better nowadays. May be with https://github.com/duniter/duniter/commit/b00ef4b9ce5cbc69397bd24f00c7b6aecf4a4236.

Yes it is better for @Insoleet because of a new configuration of Nginx reverse proxy for WebSockets.

By the way, I should add this configuration example in #615 (closed).