Mon noeud duniter v1 (g1v1.coinduf.eu) est désynchronisé et semble avoir des soucis avec les connexions ws2p :
2025-10-17T13:02:36+02:00 - info: WS2P 6mRSTCZ1JBQLt2e7AG6pNFCH4e9NejmyhPUqQAL6PZFw: new incoming connection from 127.0.0.1:34656!
2025-10-17T13:02:36+02:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:6mRSTCZ1JBQLt2e7AG6pNFCH4e9NejmyhPUqQAL6PZFw:bba6eb6c-cacd-45e8-bb1d-82ee7eb5ed2ddd923a0c-d0fc-4f6d-8287-3ec2141c4309
2025-10-17T13:02:36+02:00 - info: WS2P 6mRSTCZ1JBQLt2e7AG6pNFCH4e9NejmyhPUqQAL6PZFw: new incoming connection from 127.0.0.1:34672!
2025-10-17T13:02:36+02:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:6mRSTCZ1JBQLt2e7AG6pNFCH4e9NejmyhPUqQAL6PZFw:cbbb1c33-7d62-4031-9b7e-140643b8b297d7589512-d5f3-43fc-a879-6023f5f1799b
2025-10-17T13:02:36+02:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:6DrGg8cftpkgffv4Y4Lse9HSjgc8coEQor3yvMPHAnVH:be01a987-b5e3-4f6c-ba3b-8fcb08005b7fe7d7893c-bd71-4ba3-a16a-c18bcfe2aefd
2025-10-17T13:02:36+02:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:6mRSTCZ1JBQLt2e7AG6pNFCH4e9NejmyhPUqQAL6PZFw:be01a987-b5e3-4f6c-ba3b-8fcb08005b7fe7d7893c-bd71-4ba3-a16a-c18bcfe2aefd
2025-10-17T13:02:36+02:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:6DrGg8cftpkgffv4Y4Lse9HSjgc8coEQor3yvMPHAnVH:5bddff25-4f79-44f1-9af2-8b8b8b6374e866acb815-2161-416e-a952-abcf015501d8
2025-10-17T13:02:36+02:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:6mRSTCZ1JBQLt2e7AG6pNFCH4e9NejmyhPUqQAL6PZFw:5bddff25-4f79-44f1-9af2-8b8b8b6374e866acb815-2161-416e-a952-abcf015501d8
2025-10-17T13:02:39+02:00 - warn: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-10-17T13:02:51+02:00 - warn: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-10-17T13:02:51+02:00 - warn: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
Je sais pas tellement ce qu’il a, mais pour l’instant j’ai pas trop le temps de regarder ça.