Problème de synchronisation de nœud

J’ai essayé de reinstaller mon noeud duniter de differentes façons:
Yunohost, portainer, docker.
Je laisse tourner Duniter toute la nuit et pas de synchronisation.

Je suis sur debian 11 avec yunohost et ovh comme registrar, le serveur est bancher à la fibre par cable ethernet.
Avec ce fichier compose dans portainer:

version: '3.6'

services:
  duniter:
    environment:
    - DEBUG_ENTRYPOINT=${DUNITER_DEBUG_ENTRYPOINT:-${DEBUG_ENTRYPOINT:-${DEBUG:-}}}
    - DUNITER_AUTO_SYNC=${DUNITER_AUTO_SYNC:-true}
    - DUNITER_BMA_ENABLED=${DUNITER_BMA_ENABLED:-true}
    - DUNITER_BMA_IP4=${DUNITER_BMA_IP4:-0.0.0.0}
    - DUNITER_BMA_REMOTE_HOST=${DUNITER_BMA_REMOTE_HOST:-duniter.shainajabu1.fr}
    - DUNITER_BMA_REMOTE_PORT=${DUNITER_BMA_REMOTE:-443}
    - DUNITER_GVA_ENABLED=${DUNITER_GVA_ENABLED:-true}
    - DUNITER_GVA_PATH=${DUNITER_GVA_PATH:-gva}
    - DUNITER_GVA_PORT=${DUNITER_GVA_PORT:-30901}
    - DUNITER_GVA_REMOTE_HOST=${DUNITER_GVA_REMOTE_HOST:-duniter.shainajabu1.fr}
    - DUNITER_GVA_REMOTE_PATH=${DUNITER_GVA_REMOTE_PATH:-gva}
    - DUNITER_GVA_REMOTE_PORT=${DUNITER_GVA_REMOTE_PORT:-443}
    - DUNITER_GVA_REMOTE_TLS=${DUNITER_GVA_REMOTE_TLS:-false}
    - DUNITER_GVA_WHITELIST=${DUNITER_GVA_WHITELIST:-127.0.0.1,::1}
    - DUNITER_MANUAL_CONFIG=${DUNITER_MANUAL_CONFIG:-false}
    - DUNITER_POW_PREFIX=${DUNITER_POW_PREFIX:-}
    - DUNITER_POW_CPU=${DUNITER_POW_CPU:-0.8}
    - DUNITER_POW_NBCORES=${DUNITER_POW_NBCORES:-1}
    - DUNITER_START_OPTS=${DUNITER_START_OPTS:-direct_webstart}
    - DUNITER_SYNC_HOST=${DUNITER_SYNC_HOST:-g1.duniter.org:443}
    - DUNITER_SYNC_OPTS=${DUNITER_SYNC_OPTS:-}
    - DUNITER_WS2P_HOST=${DUNITER_WS2P_HOST:-0.0.0.0}
    - DUNITER_WS2P_PORT=${DUNITER_W2SP_PORT:-20901}
    - DUNITER_WS2P_PUBLIC=${DUNITER_W2SP_PUBLIC:-true}
    - DUNITER_WS2P_REMOTE_HOST=${DUNITER_WS2P_REMOTE_HOST:-duniter.shainajabu1.fr}
    - DUNITER_WS2P_REMOTE_PATH=${DUNITER_WS2P_REMOTE_PATH:-ws2p}
    - DUNITER_WS2P_REMOTE_PORT=${DUNITER_WS2P_REMOTE_PORT:-443}
    image: duniter/duniter:dev
    networks:
    - private
    ports:
    - 0.0.0.0:10901:10901
    - 0.0.0.0:20901:20901
    - 0.0.0.0:30901:30901
    - 0.0.0.0:9220:9220
    restart: unless-stopped
    volumes:
    - data:/var/lib/duniter
    - etc:/etc/duniter

networks:
  private:
    name: ${DOCKER_NETWORK_PRIVATE:-duniter}
  public:
    name: ${DOCKER_NETWORK_PUBLIC:-host}

volumes:
  data:
  etc:

J’ai ce message d’erreur:

2024-07-13T14:03:38+00:00 - info: WS2P: Could not connect to peer BLeKdRBX using `WS2P duniter.shainajabu1.fr 443: WS2P connection timeout`

2024-07-13T14:13:23+00:00 - info: WS2P: init: bundle of peers 1/1

2024-07-13T14:13:23+00:00 - info: Block resolution: 0 potential blocks after current#289749...

2024-07-13T14:13:23+00:00 - info: Block resolution: 0 potential blocks after current#289749...

2024-07-13T14:13:23+00:00 - warn: Security trigger: proof-of-work process seems stuck

2024-07-13T14:13:23+00:00 - warn: Local node is not a member. Waiting to be a member before computing a block.

2024-07-13T14:13:38+00:00 - info: WS2P: Could not connect to peer BLeKdRBX using `WS2P duniter.shainajabu1.fr 443: WS2P connection timeout`

2024-07-13T14:22:37+00:00 - info: WS2P: Could not connect to peer q1wzQ5Kv using `WS2P duniter.shainajabu1.fr 443: WS2P connection timeout`
2024-07-13T14:22:37+00:00 - error: Unhandled rejection: WS2P connection timeout
2024-07-13T14:22:37+00:00 - error: WS2P connection timeout

connaissançant mal yunohost, je dirais juste que ça ressemble à un noeud lancé avant la fin de la synchro donc faudra peut etre effacer les fichiers data puis la reprendre du début, ce qui équivaut à une réinstallation dans duniter brut

Merci :pray:, je vais essayer.
Cela à l’air d’avoir fonctionné :slightly_smiling_face:.