[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [translation/support-connecting] Update translations for support-connecting
commit 86bf8aae47f26de17d8435e8457531975cdff0a1
Author: Translation commit bot <translation@xxxxxxxxxxxxxx>
Date: Thu Apr 12 18:19:51 2018 +0000
Update translations for support-connecting
---
fr.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fr.json b/fr.json
index c691124e9..7fc09c393 100644
--- a/fr.json
+++ b/fr.json
@@ -9,7 +9,7 @@
"id": "#connexion-2",
"control": "connexion-2",
"title": "Jâ??éprouve des difficultés à me connecter à Tor et je nâ??arrive pas à comprendre ce qui ne va pas.",
- "description": "<p class=\"mb-3\">If youâ??re having trouble connecting, please select the option to \"copy Tor log to clipboard.\" Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server fa
ilure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâ??ve entered your proxy details correctly. If a SOCKS proxy is not required, or youâ??re not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canâ??t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like these
in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâ??re on a network thatâ??s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that Tor
failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+ "description": "<code><pre><code><pre><p class=\"mb-3\"><p class=\"mb-3\"><p class=\"mb-3\">Si vous éprouvez des difficultés à vous connecter, veuillez sélectionner lâ??option « Copier le journal de Tor dans le presse-papiers ». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver lâ??une de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor) :</p><h5> Erreur habituelle de journal no 1 : échec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\\\\\\\"general SOCKS server failure\\\\\\\")2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to co
nnect to xx..xxx..xxx.xx:xxxxx (\\\\\\\"general SOCKS server failure\\\\\\\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\\\\\\\"general SOCKS server failure\\\\\\\")</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâ??arrivez pas à vous connecter à un mandataire SOCKS. Si un mandataire SOCKS est nécessaire à la configuration de réseau, veuillez alors vous assurer dâ??avoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS nâ??est pas nécessaire ou si vous ne savez pas, veuillez tenter de vous connecter au réseau Tor sans mandataire SOCKS.<p><h5> Erreur habituelle de journal no 2 : impossible dâ??atteindre les relais gardes</h5> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to
find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâ??arrivez pas à vous connecter au premier nÅ?ud du circuit Tor. Cela pourrait signifier que vous êtes sur un réseau qui est censuré. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5> Erreur habituelle de journal no 3 : échec dâ??établissement dâ??une liaison</h5><p class=\"mb-3\"> TLS 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have
failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></p></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas réussi à établir une liaison TLS avec les autorités d'annuaire. Lâ??utilisation de ponts corrigera certainement cette situation.</p><h5> Erreur habituelle de journal no 4 : décalage dâ??horloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hou
rs, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge système nâ??est pas juste. Veuillez vous assurer que votre horloge est réglée avec précision, fuseau horaire inclus, puis redémarrez Tor.</p>"
},
"connecting-3": {
"id": "#connexion-3",
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits