[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [translation/support-connecting_completed] Update translations for support-connecting_completed
commit 08cc4a314ce6f5c5f77ce77a3209df31d47d5cb3
Author: Translation commit bot <translation@xxxxxxxxxxxxxx>
Date: Thu Apr 12 00:21:09 2018 +0000
Update translations for support-connecting_completed
---
ga.json | 2 +-
support-connecting.json | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/ga.json b/ga.json
index 26d45c2d5..a2c0e5eca 100644
--- a/ga.json
+++ b/ga.json
@@ -9,7 +9,7 @@
"id": "#connecting-2",
"control": "connecting-2",
"title": "Nà féidir liom ceangal le lÃonra Tor, agus nà thuigim cad é an fhadhb.",
- "description": "<p class=\"mb-3\">Má tá fadhb agat ag ceangal le lÃonra Tor, úsáid an rogha â??cóipeáil logchomhad Tor go dtà an ghearrthaisce.â?? Ansin, greamaigh an logchomhad i dtéacschomhad nó cáipéis eile. Is dócha go bhfeicfidh tú ceann de na hearráidà coitianta seo (cuardaigh na lÃnte seo a leanas sa logchomhad):</p><h5>Earráid choitianta #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 co
nnect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Má fheiceann tú na lÃnte seo i do logchomhad Tor, ciallaÃonn siad gur theip ort ceangal a bhunú le seachfhreastalaà SOCKS. Má theastaÃonn seachfhreastalaà SOCKS uait ar do lÃonra, deimhnigh gur chuir tú mionsonraà an fhreastalaà isteach go ceart. Mura dteastaÃonn seachfhreastalaà SOCKS uair, nó mura bhfuil tú cinnte, déan iarracht ceangal a bhunú le lÃonra Tor gan seachfhreastalaà SOCKS.<p><h5>Earráid choitianta #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] F
ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Má fheiceann tú na lÃnte seo i do logchomhad Tor, ciallaÃonn sé gur theip ort ceangal a bhunú leis an chéad nód sa gciorcad Tor. Uaireanta, ciallaÃonn seo go bhfuil do lÃonra faoi chinsireacht. Bain triail as ceangal trà dhroichead; is dócha go réiteoidh sin an fhadhb.</p><h5>Earráid choitianta #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 co
nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Má fheiceann tú na lÃnte seo i do logchomhad Tor, ciallaÃonn sé gur theip ar Tor croitheadh láimhe TLS leis na húdaráis a chur i gcrÃch. Is dócha go réiteoidh droichead an fhadhb seo.</p><h5>Earráid choitianta #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\">Má fheiceann tú na lÃnte seo i do logchomhad Tor, c
iallaÃonn sé go bhfuil an clog i do rÃomhaire mÃcheart. Ba chóir duit socruithe an chloig a dheimhniú, an t-am, dáta, agus crios ama san áireamh. Ansin, atosaigh Tor. </p>"
+ "description": "<p class=\"mb-3\">Má tá fadhb agat ag ceangal le lÃonra Tor, úsáid an rogha â??cóipeáil logchomhad Tor go dtà an ghearrthaisce.â?? Ansin, greamaigh an logchomhad i dtéacschomhad nó cáipéis eile. Is dócha go bhfeicfidh tú ceann de na hearráidà coitianta seo (cuardaigh na lÃnte seo a leanas sa logchomhad):</p><h5>Earráid choitianta #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 co
nnect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Má fheiceann tú na lÃnte seo i do logchomhad Tor, ciallaÃonn siad gur theip ort ceangal a bhunú le seachfhreastalaà SOCKS. Má theastaÃonn seachfhreastalaà SOCKS uait ar do lÃonra, deimhnigh gur chuir tú mionsonraà an fhreastalaà isteach go ceart. Mura dteastaÃonn seachfhreastalaà SOCKS uait, nó mura bhfuil tú cinnte, déan iarracht ceangal a bhunú le lÃonra Tor gan seachfhreastalaà SOCKS.<p><h5>Earráid choitianta #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] F
ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Má fheiceann tú na lÃnte seo i do logchomhad Tor, ciallaÃonn sé gur theip ort ceangal a bhunú leis an chéad nód sa gciorcad Tor. Uaireanta, ciallaÃonn seo go bhfuil do lÃonra faoi chinsireacht. Bain triail as ceangal trà dhroichead; is dócha go réiteoidh sin an fhadhb.</p><h5>Earráid choitianta #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 co
nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Má fheiceann tú na lÃnte seo i do logchomhad Tor, ciallaÃonn sé gur theip ar Tor croitheadh láimhe TLS leis na húdaráis a chur i gcrÃch. Is dócha go réiteoidh droichead an fhadhb seo.</p><h5>Earráid choitianta #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\">Má fheiceann tú na lÃnte seo i do logchomhad Tor, c
iallaÃonn sé go bhfuil an clog i do rÃomhaire mÃcheart. Ba chóir duit socruithe an chloig a dheimhniú, an t-am, dáta, agus crios ama san áireamh. Ansin, atosaigh Tor. </p>"
},
"connecting-3": {
"id": "#connecting-3",
diff --git a/support-connecting.json b/support-connecting.json
index cac143183..4d3e7f911 100644
--- a/support-connecting.json
+++ b/support-connecting.json
@@ -9,7 +9,7 @@
"id": "#connecting-2",
"control": "connecting-2",
"title": "I am having trouble connecting to Tor, and I canâ??t figure out whatâ??s wrong.",
- "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
failure\")</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 the
se 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 To
r 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": "<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>"
},
"connecting-3": {
"id": "#connecting-3",
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits