Le screenshot montre une erreur sur mon noeud wss://gtest.asycn.io/ws.
Je m’annonce avec DUNITER_PUBLIC_RPC: wss://gtest.asycn.io/ws/ et le / final est bien publié dans la table de peering :
$ curl -sX POST https://g1v2.duniter.org -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0","id":1,"method":"duniter_peerings","params":{}}' |jq |grep address
"address": "wss://g1v2.duniter.org"
"address": "wss://ws.ansac.sleoconnect.fr/ws"
"address": "wss://ws.nontron.sleoconnect.fr/ws"
"address": "ws://144.24.199.65:9955/"
"address": "wss://gtest.asycn.io/ws/"
"address": "wss://ws.vaire.sleoconnect.fr/ws"
"address": "wss://ws.gtest.bulma.sleoconnect.fr/ws"
"address": "wss://gt.p2p.legal/ws"
"address": "https://gt-squid.axiom-team.fr"
"address": "wss://gtest.coinduf.eu"
"address": "https://squid.gtest.coinduf.eu/v1/graphql"
"address": "wss://archive-rpc.gtest.fr.brussels.ovh/"
"address": "https://squid.gtest.fr.brussels.ovh/v1/graphql"
"address": "wss://gtest.trentesaux.fr"
"address": "https://squid.gtest.trentesaux.fr/v1/graphql"
"address": "wss://gtest.1000i100.fr/"
@cgeek tu strip le ‘/’ final dans les url ?