# Beta-test Duniter 1.6 WS2P - mirror node

**URL:** <https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p-mirror-node/3282>\
**Category:** WS2P\
**Tags:** mirror, ws2p, node\
**Created:** [25 September 2017 13:02 UTC](https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p-mirror-node/3282 "2017-09-25T13:02:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Max](https://forum.duniter.org/user_avatar/forum.duniter.org/max/32/2424_2.png) [@Max](https://forum.duniter.org/u/Max)\
**Post date:** [25 September 2017 13:02 UTC](https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p-mirror-node/3282/1 "2017-09-25T13:02:55Z")

</div>

yop,

j’ai install duniter a partir de la branche dev, commit c3e86be

> uname -a  
> Linux 3.13.0-106-generic #153-Ubuntu SMP x86\_64 GNU/Linux

> node -v  
> v7.10.0

j’ai changé le fichier de conf manuellement, en l’état c’est le suivant:

> “nobma”: true,  
> “upnp”: false,  
> “ws2p”: {  
> “uuid”: “78e409b5”,  
> “privateAccess”: false,  
> “publicAccess”: true,  
> “upnp”: false  
> },  
> “endpoints”: ,  
> “rmEndpoints”: ,  
> j’ai ouvert un numero de port pour la clé “port” et “remoteport”
> 
> > est-ce que la conf est ok ?

j’ai fait la sync sur G1

je reporte une partie du log :

> 2017-09-24T17:05:06+02:00 - info: Node version: 1.6.4  
> 2017-09-24T17:05:06+02:00 - info: Node pubkey: E9g8eaKEeTf7omuT3qwHrRPxvYvTwUTfGnYcYhPY9yuX  
> 2017-09-24T17:05:06+02:00 - info: \>\> Server ready!  
> 2017-09-24T17:05:06+02:00 - warn: Local node is not a member. Waiting to be a member before computing a block.  
> 2017-09-24T17:05:06+02:00 - info: Sibling endpoints:  
> 2017-09-24T17:05:06+02:00 - info: ⬇ PEER E9g8eaKE  
> 2017-09-24T17:05:06+02:00 - info: ✘ PEER E9g8eaKE  
> 2017-09-24T17:05:06+02:00 - error: Peer with zero endpoints that is not already known  
> 2017-09-25T13:35:06+02:00 - info: Next peering signal in 10 min  
> 2017-09-25T13:45:06+02:00 - info: Sibling endpoints:  
> 2017-09-25T13:45:06+02:00 - info: ⬇ PEER E9g8eaKE  
> 2017-09-25T13:45:06+02:00 - warn: Security trigger: proof-of-work process seems stuck  
> 2017-09-25T13:45:06+02:00 - warn: Local node is not a member. Waiting to be a member before computing a block.  
> 2017-09-25T13:45:06+02:00 - info: ✘ PEER E9g8eaKE  
> 2017-09-25T13:45:06+02:00 - error: Peer with zero endpoints that is not already known  
> 2017-09-25T13:45:06+02:00 - info: Next peering signal in 10 min  
> 2017-09-25T13:55:06+02:00 - info: Sibling endpoints:  
> 2017-09-25T13:55:06+02:00 - info: ⬇ PEER E9g8eaKE  
> 2017-09-25T13:55:06+02:00 - warn: Security trigger: proof-of-work process seems stuck  
> 2017-09-25T13:55:06+02:00 - warn: Local node is not a member. Waiting to be a member before computing a block.  
> 2017-09-25T13:55:06+02:00 - info: ✘ PEER E9g8eaKE  
> 2017-09-25T13:55:06+02:00 - error: Peer with zero endpoints that is not already known  
> 2017-09-25T13:55:06+02:00 - info: Next peering signal in 10 min  
> 2017-09-25T14:05:06+02:00 - info: Sibling endpoints:  
> 2017-09-25T14:05:06+02:00 - info: ⬇ PEER E9g8eaKE  
> 2017-09-25T14:05:06+02:00 - warn: Security trigger: proof-of-work process seems stuck  
> 2017-09-25T14:05:06+02:00 - warn: Local node is not a member. Waiting to be a member before computing a block.  
> 2017-09-25T14:05:06+02:00 - info: ✘ PEER E9g8eaKE  
> 2017-09-25T14:05:06+02:00 - error: Peer with zero endpoints that is not already known  
> 2017-09-25T14:05:06+02:00 - info: Next peering signal in 10 min  
> 2017-09-25T14:15:06+02:00 - info: Sibling endpoints:  
> 2017-09-25T14:15:06+02:00 - info: ⬇ PEER E9g8eaKE  
> 2017-09-25T14:15:06+02:00 - info: ✘ PEER E9g8eaKE  
> 2017-09-25T14:15:06+02:00 - error: Peer with zero endpoints that is not already known  
> 2017-09-25T14:15:06+02:00 - warn: Security trigger: proof-of-work process seems stuck  
> 2017-09-25T14:15:06+02:00 - info: Next peering signal in 10 min

---

<div class="post-metadata">

**Author:** ![cgeek](https://forum.duniter.org/user_avatar/forum.duniter.org/cgeek/32/279_2.png) [@cgeek](https://forum.duniter.org/u/cgeek)\
**Post date:** [25 September 2017 15:02 UTC](https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p-mirror-node/3282/2 "2017-09-25T15:02:18Z")

</div>

Essaies plutôt le réseau Ğ1-Test, où WS2P est plus déployé: [Beta-test Duniter 1.6 WS2P](https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p/3247/71)

---

<div class="post-metadata">

**Author:** ![Moul](https://forum.duniter.org/user_avatar/forum.duniter.org/moul/32/9145_2.png) [@Moul](https://forum.duniter.org/u/Moul)\
**Post date:** [26 September 2017 15:08 UTC](https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p-mirror-node/3282/3 "2017-09-26T15:08:12Z")

</div>

> [@Max](#):
>
> node -v
> 
> v7.10.0

Wow, t’es bien le seul à avoir ressayé avec cette version de Node.js depuis la migration TypeScript.

Ça fonctionne ?  
Ça a l’air. On pourra facilement [passer à Node.js version 8 courant octobre](https://github.com/duniter/duniter/issues/689).

---

<div class="post-metadata">

**Author:** ![Max](https://forum.duniter.org/user_avatar/forum.duniter.org/max/32/2424_2.png) [@Max](https://forum.duniter.org/u/Max)\
**Post date:** [26 September 2017 19:23 UTC](https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p-mirror-node/3282/4 "2017-09-26T19:23:53Z")

</div>

j’ai test la synchro cette aprem et impossible de contacter les hotes sur g1-test, ca bloque a un certain moment et tourne dans le vent…

du coup j’ai dl la v1.6.6 a partir des sources et sync sur G1, ca semble tourner, j’ai la key suivante DT2a5kZprbx5fbs7caxb6d3VmYcuqy4UHHmVq6rjRGWi  
outre les derniers log:

> 2017-09-26T21:18:13+02:00 - warn: httpCode=400, ucode=2023, message=Peer document already known  
> 2017-09-26T21:18:13+02:00 - info: ⬇ PEER 2ny7YAdm  
> 2017-09-26T21:18:13+02:00 - info: ✘ PEER 2ny7YAdm  
> 2017-09-26T21:18:13+02:00 - warn: httpCode=400, ucode=2023, message=Peer document already known  
> 2017-09-26T21:18:44+02:00 - info: ⬇ PEER 2t6NP6Fv  
> 2017-09-26T21:18:44+02:00 - info: ⬇ PEER 2t6NP6Fv  
> 2017-09-26T21:18:44+02:00 - warn: httpCode=400, ucode=1015, message=Document already under treatment  
> 2017-09-26T21:18:44+02:00 - info: ✔ PEER 2t6NP6Fv  
> 2017-09-26T21:18:45+02:00 - info: ⬇ PEER 2t6NP6Fv  
> 2017-09-26T21:18:45+02:00 - info: ✘ PEER 2t6NP6Fv  
> 2017-09-26T21:18:45+02:00 - warn: httpCode=400, ucode=2023, message=Peer document already known  
> 2017-09-26T21:19:12+02:00 - info: ⬇ PEER 48SLtTLL  
> 2017-09-26T21:19:12+02:00 - info: ⬇ PEER 48SLtTLL  
> 2017-09-26T21:19:12+02:00 - warn: httpCode=400, ucode=1015, message=Document already under treatment  
> 2017-09-26T21:19:12+02:00 - info: ⬇ PEER 48SLtTLL  
> 2017-09-26T21:19:12+02:00 - warn: httpCode=400, ucode=1015, message=Document already under treatment  
> 2017-09-26T21:19:12+02:00 - info: ✔ PEER 48SLtTLL  
> 2017-09-26T21:19:13+02:00 - info: ⬇ PEER 48SLtTLL  
> 2017-09-26T21:19:13+02:00 - info: ✘ PEER 48SLtTLL  
> 2017-09-26T21:19:13+02:00 - warn: httpCode=400, ucode=2023, message=Peer document already known

* * *

au passage duniter (web\_start / webstart) ↔ commande non implementé…

---

<div class="post-metadata">

**Author:** ![cgeek](https://forum.duniter.org/user_avatar/forum.duniter.org/cgeek/32/279_2.png) [@cgeek](https://forum.duniter.org/u/cgeek)\
**Post date:** [26 September 2017 19:35 UTC](https://forum.duniter.org/t/beta-test-duniter-1-6-ws2p-mirror-node/3282/5 "2017-09-26T19:35:42Z")

</div>

Oui je confirme tu es bien connecté en P2P via WS2P.

Pour ce qui est de `webstart`, et sous couvert d’être en 1.6.6, la commande `yarn add duniter-ui` devrait te la fournir. Si ce n’est toujours pas le cas, un `yarn upgrade` devrait mettre à jour duniter-ui en dernière version disponible.
