# Configuration WS2P correcte ? (Duniter 1.7.9)
**URL:** https://forum.duniter.org/t/configuration-ws2p-correcte-duniter-1-7-9/5600
**Category:** Duniter-v1
**Tags:** ws2p
**Created:** [11 January 2019 18:32 UTC](https://forum.duniter.org/t/configuration-ws2p-correcte-duniter-1-7-9/5600 "2019-01-11T18:32:22Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@1000i100](https://forum.duniter.org/u/1000i100)
#### Post date: [11 January 2019 18:32 UTC](https://forum.duniter.org/t/configuration-ws2p-correcte-duniter-1-7-9/5600/1 "2019-01-11T18:32:22Z")
Me voici en 1.7.9 ceci dit, j’ai l’impression que j’ai un souci dans ma config réseau pour le ws2p public.
[https://duniter.g1.1000i100.fr/ws2p/](https://duniter.g1.1000i100.fr/ws2p/)
Voila ma config vhost nginx
```auto
server {
listen 443 ssl http2;
server_name duniter.g1.1000i100.fr;
root /nowhere;
location '/ws2p' {
proxy_pass http://localhost:20801/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
}
location '/' {
proxy_pass http://localhost:10900/;
}
ssl_certificate /etc/nginx/ssl/g1.1000i100.fr.cert;
ssl_certificate_key /etc/nginx/ssl/g1.1000i100.fr.key;
}
```
et ma config duniter :
```auto
{
"currency": "g1",
"endpoints": [],
"rmEndpoints": [],
"upInterval": 3600000,
"c": 0.0488,
"dt": 86400,
"dtReeval": 15778800,
"ud0": 1000,
"stepMax": 5,
"sigPeriod": 432000,
"sigReplay": 5259600,
"sigValidity": 63115200,
"msValidity": 31557600,
"sigQty": 5,
"xpercent": 0.8,
"percentRot": 0.67,
"powDelay": 0,
"avgGenTime": 300,
"dtDiffEval": 12,
"medianTimeBlocks": 24,
"httplogs": false,
"udid2": false,
"timeout": 3000,
"isolate": false,
"forksize": 100,
"switchOnHeadAdvance": 3,
"nonWoTPeersLimit": 100,
"msPeriod": 5259600,
"loglevel": "info",
"cpu": 0.5,
"nbCores": 4,
"prefix": 1,
"nobma": false,
"bmaWithCrawler": false,
"upnp": true,
"dos": {
"whitelist": [
"127.0.0.1",
"192.168.1.75",
"fd6f:245f:28ec:0:4a5b:39ff:fe3e:1a46"
],
"maxcount": 80,
"burst": 20,
"limit": 40,
"maxexpiry": 10,
"checkinterval": 1,
"trustProxy": true,
"includeUserAgent": true,
"errormessage": "Error",
"testmode": false,
"silent": false,
"silentStart": true,
"responseStatus": 429
},
"ws2p": {
"uuid": "90xxxxx",
"privateAccess": true,
"publicAccess": true,
"preferedOnly": false,
"privilegedOnly": false,
"upnp": false,
"maxPublic": 30,
"host": "127.0.0.1",
"maxPrivate": 4,
"remotepath": "/ws2p",
"remoteport": 443,
"port": 20801,
"remotehost": "duniter.g1.1000i100.fr"
},
"proxiesConf": {
"reachingClearEp": "clear",
"forceTor": false
},
"remoteipv6": "fd6f:245f:28ec:0:4a5b:39ff:fe3e:1a46",
"remoteport": 443,
"sigStock": 100,
"sigWindow": 5259600,
"idtyWindow": 5259600,
"msWindow": 5259600,
"rootoffset": 0,
"ipv4": "127.0.0.1",
"ipv6": "fd6f:245f:28ec:0:4a5b:39ff:fe3e:1a46",
"port": 10900,
"storage": {
"transactions": false
},
"udTime0": 1488970800,
"udReevalTime0": 1490094000,
"remotehost": "duniter.g1.1000i100.fr",
"remoteipv4": "82.64.0.18"
}
```
Et voici à quoi ressemblent mes connexions :
```auto
WS2P Connections
Pubkey WS2PID Member Type Connection
8t6Di3pLxxoTEfjXHjF4 dff60418 Scott76 OUTCOMING 82.64.35.65:443
38MEAZN68Pz1DTvT3tqg fb17fcd4 BenoitLavenier OUTCOMING 88.189.14.141:443
D9D2zaJoWYWveii1JRYL c1c39a0a elois OUTCOMING 5.135.188.170:443
FSAPnBZidfUaiURd1qxw 9d845e0b Melua OUTCOMING 163.172.169.239:20901
5oGdiLzs1mmqh9m95pYd - INCOMING 127.0.0.1:20801
BFjZBLmdZC63tyF9a3Ac - INCOMING 127.0.0.1:20801
```
Qu’en pensez-vous ? tout va bien ou j’ai bien quelque-chose à changer ?
---
### Author:  [@cgeek](https://forum.duniter.org/u/cgeek)
#### Post date: [12 January 2019 13:05 UTC](https://forum.duniter.org/t/configuration-ws2p-correcte-duniter-1-7-9/5600/2 "2019-01-12T13:05:03Z")
> [@Sortie de Duniter 1.7](https://forum.duniter.org/t/sortie-de-duniter-1-7/5573/16):
>
> Me voici en 1.7.9 ceci dit, j’ai l’impression que j’ai un souci dans ma config réseau pour le ws2p public.
> [https://duniter.g1.1000i100.fr/ws2p/](https://duniter.g1.1000i100.fr/ws2p/)
Qu’est-ce qui te fait penser cela ?
---
### Author:  [@1000i100](https://forum.duniter.org/u/1000i100)
#### Post date: [12 January 2019 16:06 UTC](https://forum.duniter.org/t/configuration-ws2p-correcte-duniter-1-7-9/5600/3 "2019-01-12T16:06:44Z")
- Le fait de n’avoir peu ou pas de connexion incoming (0 après 24h online).
- Le fait de voir mon noeud sur cesium comme SSL (BMA en https si j’ai bien suivi), comme WS2P uniquement en Accès privé, et de voir d’autre noeud avec SSL et WS2P comme je m’attendrait à avoir pour mon noeud.
PS : un moyen de tester, via l’url [https://duniter.g1.1000i100.fr/ws2p/](https://duniter.g1.1000i100.fr/ws2p/) si tout va bien ou non ?
---
### Author:  [@cgeek](https://forum.duniter.org/u/cgeek)
#### Post date: [12 January 2019 16:34 UTC](https://forum.duniter.org/t/configuration-ws2p-correcte-duniter-1-7-9/5600/4 "2019-01-12T16:34:49Z")
Je viens d’essayer d’ouvrir l’URL wss://duniter.g1.1000i100.fr/ws2p/ avec Simple Web Socket client, et je reçois bien une trame :
```json
{
"auth":"CONNECT",
"pub":"2sZF6j2PkxBDNAqUde7Dgo5x3crkerZpQ4rBqqJGn8QT",
"challenge":"78acb30f-369f-455f-804c-409165158c75eca0fa56-7576-4a54-a6dd-fa6758a36687",
"sig":"eyKJ+39WeAY4RtKIAjEDv9RnKp7n8NjfhcJjFAmZcnEG4t3dr8gai7iptsn+qG4UdpN19/wVXfzdVC3PZ7l+Bw==",
"currency":"g1"
}
```
Donc je dirais que ce point là est correct. J’essaye d’investiguer un peu plus.
edit : déjà j’arrive bien à requêter ton nœud en WS2P. Ce test a permis de révéler un bug pour la synchro sur les nœuds comme le tiens avec un chemin ([ticket#1329](https://git.duniter.org/nodes/typescript/duniter/issues/1329)), Duniter échoue à s’y connecter. Mais ce bug ne concerne _a priori_ que la synchro.