subject:"\[tor\-commits\] \[translation\/support\-connecting\] Update translations for support\-connecting"

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-31 Thread translation

commit cc6bd2b86d0e0eab257ee70b23995d1cf19197f7
Author: Translation commit bot 
Date:   Tue Jul 31 16:49:04 2018 +

Update translations for support-connecting
---
 fo.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fo.json b/fo.json
index 4d3e7f911..64737e1ee 100644
--- a/fo.json
+++ b/fo.json
@@ -2,7 +2,7 @@
 "connecting-1": {
"id": "#connecting-1",
"control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
+   "title": "Tor kagarin fÃ¦r ikki samband, men taÃ° sÃ¦r ikki Ãºt til at 
vera ein trupuleiki viÃ° sensur. ",
"description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
 },
 "connecting-2": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-16 Thread translation

commit 7882649e531f77b6802e3332282d72ea541fad83
Author: Translation commit bot 
Date:   Tue Jul 17 03:22:24 2018 +

Update translations for support-connecting
---
 sq.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sq.json b/sq.json
index 0298c7174..82404bfd9 100644
--- a/sq.json
+++ b/sq.json
@@ -3,13 +3,13 @@
"id": "#po lidhet-1",
"control": "po lidhet-1",
"title": "Tor browser nuk po lidhet,por nuk duket sikur njÃ« problem me 
censurÃ«",
-   "description": "njÃ« nga problemet mÃ« tÃ« zakonshme 
qÃ« shkaktojnÃ« gabime lidhjeje nÃ« Tor Browser Ã«shtÃ« njÃ« orÃ« e gabuar e 
sistemit.Ju lutemi sigurohuni qÃ« ora juaj e sistemit dhe zona e kohÃ«s  janÃ« 
tÃ« vendosura me saktÃ«si.NÃ«se kjo nuk jua ndreq problemin,shikoni faqen e 
Troubleshooting nÃ«https://tb-manual.torproject.org/en-US/bridges.html\;> manualin e Tor 
Browser."
+   "description": "njÃ« nga problemet mÃ« tÃ« zakonshme 
qÃ« shkaktojnÃ« gabime lidhjeje nÃ« Tor Browser Ã«shtÃ« njÃ« orÃ« e gabuar e 
sistemit.Ju lutemi sigurohuni qÃ« ora juaj e sistemit dhe zona e kohÃ«s  janÃ« 
tÃ« vendosura me saktÃ«si.NÃ«se kjo nuk jua rregullon problemin,shikoni faqen e 
Troubleshooting nÃ«https://tb-manual.torproject.org/en-US/bridges.html\;> manualin e Tor 
Browser."
 },
 "connecting-2": {
"id": "#po lidhet-2",
"control": "po lidhet-2",
"title": "UnÃ« po kam probleme me lidhje nÃ« Tor.dhe unÃ« nuk mund tÃ« 
kuptoj qka Ã«shtÃ« gabim.",
-   "description": "NÃ«se ju po keni probleme me 
lidhje,ju lutemi sgjidhni opcionin \"Kopjo Tor log nÃ« clipboard.\"Pastaj 
ngjitni Tor log-in nÃ« njÃ« file teksti ose ndonjÃ« dokument tjetÃ«r.Ju duhet 
tÃ« shihni njÃ« nga kÃ«to log-at e gabimeve tÃ« zakonshme(shiko pÃ«r linjat e 
mÃ«poshtme nÃ« log-in tuaj Tor):log-i i gabimit tÃ« zakonshÃ«m #1: 
Proxy connection failure 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:x (\"general SOCKS server failure\") \n 2017-10-29 
09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:x 
(\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy 
Client: unable to connect toxx..xxx..xxx.
 xx:x (\"general SOCKS server failure\")\nNÃ«se shihni linja si kÃ«to nÃ« Tor log-in tu"
+   "description": "NÃ«se ju po keni probleme me lidhje,ju lutemi sgjidhni 
opcionin \"Kopjo Tor log nÃ« clipboard.\"Pastaj ngjitni Tor log-in nÃ« njÃ« 
file teksti ose ndonjÃ« dokument tjetÃ«r.Ju duhet tÃ« shihni njÃ« nga kÃ«to 
log-at e gabimeve tÃ« zakonshme(shiko pÃ«r linjat e mÃ«poshtme nÃ« log-in tuaj 
Tor):log-u i gabimit tÃ« zakonshÃ«m #1: Proxy connection failure 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:x (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to 
xx..xxx..xxx.xx:x (\"general SOCKS server failure\") \n 2017-10-29 
09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:x 
(\"general SOCKS server failure\"
 )\nNÃ«se shihni linja si kÃ«to nÃ« Tor log-un tuaj,kjo do tÃ« thotÃ« se lidhja 
juaj me njÃ« SOCKS proxy po dÃ«shton.NÃ«se njÃ« SOCKS proxy Ã«shtÃ« e nevojshme 
pÃ«r organizimin e rjetit tuaj,atÃ«herÃ« ju lutemi sigurohuni qÃ« keni shÃ«nuar 
detalet e proxy-yt saktÃ«sisht.NÃ«se njÃ« SOCKS proxy nuk Ã«shtÃ« e 
nevojshme,ose nuk jeni tÃ« sigurt,ju lutemi provoni tÃ« lidheni nÃ« rjetin Tor 
pa njÃ« SOCKS proxy.Log-u i njÃ« gabimit tÃ« zakonshÃ«m #2:Canât reach guard 
relays 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.NÃ«se shihni linja si kÃ«to nÃ« log-un tuaj Tor,Do tÃ« 
thotÃ« se 
 Tor-i i juaj dÃ«shtoi tÃ« lidhet nÃ« nyjen e parÃ« nÃ« qarkun Tor.Kjo mund tÃ« 
thotÃ« se ju jeni nÃ« njÃ« rjet tÃ« censuruar.ju lutemi provoni lidhjen me 
ura,dhe kjo duhet ta regullojÃ« problemin.Gabimi i zakonshÃ«m #3:Failed to 
complete TLS handshake 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

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-13 Thread translation

commit b1d8368322b56221c937554150d2f30236bf8f9d
Author: Translation commit bot 
Date:   Fri Jul 13 14:18:55 2018 +

Update translations for support-connecting
---
 sq.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sq.json b/sq.json
index 0b6215de9..0298c7174 100644
--- a/sq.json
+++ b/sq.json
@@ -9,7 +9,7 @@
"id": "#po lidhet-2",
"control": "po lidhet-2",
"title": "UnÃ« po kam probleme me lidhje nÃ« Tor.dhe unÃ« nuk mund tÃ« 
kuptoj qka Ã«shtÃ« gabim.",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "NÃ«se ju po keni probleme me 
lidhje,ju lutemi sgjidhni opcionin \"Kopjo Tor log nÃ« clipboard.\"Pastaj 
ngjitni Tor log-in nÃ« njÃ« file teksti ose ndonjÃ« dokument tjetÃ«r.Ju duhet 
tÃ« shihni njÃ« nga kÃ«to log-at e gabimeve tÃ« zakonshme(shiko pÃ«r linjat e 
mÃ«poshtme nÃ« log-in tuaj Tor):log-i i gabimit tÃ« zakonshÃ«m #1: 
Proxy connection failure 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:x (\"general SOCKS server failure\") \n 2017-10-29 
09:24:08.900 [WARN] Proxy Client: unable to

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-12 Thread translation

commit d8f3328213a5be723dc90d1dd63a24a8f1c12688
Author: Translation commit bot 
Date:   Thu Jul 12 12:19:01 2018 +

Update translations for support-connecting
---
 sq.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sq.json b/sq.json
index 0ac68210d..0b6215de9 100644
--- a/sq.json
+++ b/sq.json
@@ -3,7 +3,7 @@
"id": "#po lidhet-1",
"control": "po lidhet-1",
"title": "Tor browser nuk po lidhet,por nuk duket sikur njÃ« problem me 
censurÃ«",
-   "description": "njÃ« nga problemet mÃ« tÃ« zakonshme qÃ« shkaktojnÃ« 
gabime lidhjeje nÃ« Tor Browser Ã«shtÃ« njÃ« orÃ« e gabuar e sistemit.Ju lutemi 
sigurohuni qÃ« ora juaj e sistemit dhe zona e kohÃ«s  janÃ« tÃ« vendosura me 
saktÃ«si.NÃ«se kjo nuk jua ndreq problemin,shikoni faqen e Troubleshooting nÃ« 
manualin e Tor Browser."
+   "description": "njÃ« nga problemet mÃ« tÃ« zakonshme 
qÃ« shkaktojnÃ« gabime lidhjeje nÃ« Tor Browser Ã«shtÃ« njÃ« orÃ« e gabuar e 
sistemit.Ju lutemi sigurohuni qÃ« ora juaj e sistemit dhe zona e kohÃ«s  janÃ« 
tÃ« vendosura me saktÃ«si.NÃ«se kjo nuk jua ndreq problemin,shikoni faqen e 
Troubleshooting nÃ«https://tb-manual.torproject.org/en-US/bridges.html\;> manualin e Tor 
Browser."
 },
 "connecting-2": {
"id": "#po lidhet-2",
@@ -15,6 +15,6 @@
"id": "#po lidhet-3",
"control": "po lidhet-3",
"title": "UnÃ« nuk mund ta arrij X.onion!",
-   "description": "If you cannot reach the onion service 
you desire, make sure that you have entered the 16-character onion address 
correctly: even a small mistake will stop Tor Browser from being able to reach 
the site. If you are still unable to connect to the onion service, please try 
again later. There may be a temporary connection issue, or the site operators 
may have allowed it to go offline without warning.You can 
also ensure that you're able to access other onion services by connecting to http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo's âOnion Service."
+   "description": "NÃ«se ju nuk mund ta arrini onion 
servisin qÃ« dÃ«shironi,Sigurohuni qÃ« keni shÃ«nuar addresÃ«n 16-karakter 
onion saktÃ«sisht:madje edhe njÃ« gabim i vogÃ«l do ta ndaloj Tor Browserin ta 
arrij atÃ« faqe.NÃ«se ju ende nuk mund tÃ« lidheni nÃ« servisin onion,ju lutemi 
provoni mÃ« vonÃ«.KÃ«tu mun tÃ« ketÃ« njÃ« problem i pÃ«rkohshÃ«m lidhjeje,ose  
operatorÃ«t e faqes mund tÃ« kenÃ« pranuar ta dÃ«rgojnÃ« faqen jashtÃ« linje pa 
lajmÃ«rim.Gjithashtu,ju mund tÃ« siguroheni se keni akses 
nÃ« serviset e tjera onion duke u lidhur nÃ« onion servisine http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo-sÃ«."
 }
 }

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-12 Thread translation

commit 394ff547a44c7aec8324c1fc6e1ea7d3c6229dae
Author: Translation commit bot 
Date:   Thu Jul 12 11:19:06 2018 +

Update translations for support-connecting
---
 sq.json | 18 +-
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/sq.json b/sq.json
index ded44f62f..0ac68210d 100644
--- a/sq.json
+++ b/sq.json
@@ -1,20 +1,20 @@
 {
 "connecting-1": {
-   "id": "#connecting-1",
-   "control": "connecting-1",
+   "id": "#po lidhet-1",
+   "control": "po lidhet-1",
"title": "Tor browser nuk po lidhet,por nuk duket sikur njÃ« problem me 
censurÃ«",
-   "description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
+   "description": "njÃ« nga problemet mÃ« tÃ« zakonshme qÃ« shkaktojnÃ« 
gabime lidhjeje nÃ« Tor Browser Ã«shtÃ« njÃ« orÃ« e gabuar e sistemit.Ju lutemi 
sigurohuni qÃ« ora juaj e sistemit dhe zona e kohÃ«s  janÃ« tÃ« vendosura me 
saktÃ«si.NÃ«se kjo nuk jua ndreq problemin,shikoni faqen e Troubleshooting nÃ« 
manualin e Tor Browser."
 },
 "connecting-2": {
-   "id": "#connecting-2",
-   "control": "connecting-2",
-   "title": "I am having trouble connecting to Tor, and I canât figure 
out whatâs wrong.",
+   "id": "#po lidhet-2",
+   "control": "po lidhet-2",
+   "title": "UnÃ« po kam probleme me lidhje nÃ« Tor.dhe unÃ« nuk mund tÃ« 
kuptoj qka Ã«shtÃ« gabim.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): It seems 
that our clock is behind by 1

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-12 Thread translation

commit 3acf490371e13c8083533beca8579c05eb34b9a1
Author: Translation commit bot 
Date:   Thu Jul 12 10:49:07 2018 +

Update translations for support-connecting
---
 sq.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sq.json b/sq.json
index 4d3e7f911..ded44f62f 100644
--- a/sq.json
+++ b/sq.json
@@ -2,7 +2,7 @@
 "connecting-1": {
"id": "#connecting-1",
"control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
+   "title": "Tor browser nuk po lidhet,por nuk duket sikur njÃ« problem me 
censurÃ«",
"description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
 },
 "connecting-2": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-08 Thread translation

commit 2a7a48da358ae99a92894492fdbbf9c57f4039c3
Author: Translation commit bot 
Date:   Sun Jul 8 21:49:22 2018 +

Update translations for support-connecting
---
 hu.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hu.json b/hu.json
index 4d3e7f911..f0ae39599 100644
--- a/hu.json
+++ b/hu.json
@@ -2,7 +2,7 @@
 "connecting-1": {
"id": "#connecting-1",
"control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
+   "title": "A Tor bÃ¶ngÃ©szÅ nem tud csatlakozni, de ez nem tÅ±nik 
cenzÃºra problÃ©mÃ¡nak.",
"description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
 },
 "connecting-2": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-05 Thread translation

commit bf7d9c05d34779a3b1ad19f89b313c73e0e5d6a2
Author: Translation commit bot 
Date:   Thu Jul 5 12:49:11 2018 +

Update translations for support-connecting
---
 tr.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tr.json b/tr.json
index 393aa5c88..c1f4fc247 100644
--- a/tr.json
+++ b/tr.json
@@ -15,6 +15,6 @@
"id": "#baglanti-3",
"control": "baglanti-3",
"title": "X.onion'a ulaÅamÄ±yorum!",
-   "description": "If you cannot reach the onion service 
you desire, make sure that you have entered the 16-character onion address 
correctly: even a small mistake will stop Tor Browser from being able to reach 
the site. If you are still unable to connect to the onion service, please try 
again later. There may be a temporary connection issue, or the site operators 
may have allowed it to go offline without warning.You can 
also ensure that you're able to access other onion services by connecting to http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo's âOnion Service."
+   "description": "Ä°stediÄiniz soÄan servisine 
ulaÅamÄ±yorsanÄ±z, 16 karakterli soÄan adresini doÄru girdiÄinizden emin 
olun: KÃ¼Ã§Ã¼k bir hata bile Tor Browser'Ä±n siteye ulaÅmasÄ±nÄ± 
engelleyecektir. SoÄan servisine hala baÄlanamÄ±yorsanÄ±z, lÃ¼tfen daha sonra 
tekrar deneyin. GeÃ§ici bir baÄlantÄ± sorunu olabilir veya site operatÃ¶rleri 
uyarÄ± yapmadan sitenin Ã§evrimdÄ±ÅÄ± olmasÄ±na izin verebilir.Buraya baÄlanarak diÄer soÄan servislerine 
eriÅebildiÄinizden emin olabilirsiniz.http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo's âOnion Service."
 }
 }

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-05 Thread translation

commit b78efb961dadd8680de7d81ed3163ddbae38ad46
Author: Translation commit bot 
Date:   Thu Jul 5 09:19:17 2018 +

Update translations for support-connecting
---
 tr.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tr.json b/tr.json
index 9321608ce..393aa5c88 100644
--- a/tr.json
+++ b/tr.json
@@ -9,7 +9,7 @@
"id": "#baglanti-2",
"control": "baglanti-2",
"title": "Tor baÄlantÄ±sÄ± kurmakta sorun yaÅÄ±yorum ve sorunun ne 
olduÄunu bulamÄ±yorum.",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "BaÄlanmakta sorun yaÅÄ±yorsanÄ±z, 
lÃ¼tfen \"Tor gÃ¼nlÃ¼ÄÃ¼nÃ¼ panoya kopyala\" seÃ§eneÄini seÃ§in. Daha sonra 
Tor gÃ¼nlÃ¼ÄÃ¼nÃ¼ bir metin dosyasÄ±na veya baÅka bir belgeye yapÄ±ÅtÄ±rÄ±n. 
Bu genel gÃ¼nlÃ¼k hatalarÄ±ndan birini gÃ¶rmelisiniz (Tor log'unuzda 
aÅaÄÄ±daki satÄ±rlarÄ± arayÄ±n):Common log error #1: Proxy connection 
failure 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:x (\"general SOCKS server failure\") \n 2017-10-29 
09:24:08.900 [WARN] Proxy Client: unable to connect to

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-07-05 Thread translation

commit 9e35ec052610f28daa2910d9986ed26384a1907d
Author: Translation commit bot 
Date:   Thu Jul 5 07:19:01 2018 +

Update translations for support-connecting
---
 tr.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tr.json b/tr.json
index 9388eb3fc..9321608ce 100644
--- a/tr.json
+++ b/tr.json
@@ -14,7 +14,7 @@
 "connecting-3": {
"id": "#baglanti-3",
"control": "baglanti-3",
-   "title": "I cannot reach X.onion!",
+   "title": "X.onion'a ulaÅamÄ±yorum!",
"description": "If you cannot reach the onion service 
you desire, make sure that you have entered the 16-character onion address 
correctly: even a small mistake will stop Tor Browser from being able to reach 
the site. If you are still unable to connect to the onion service, please try 
again later. There may be a temporary connection issue, or the site operators 
may have allowed it to go offline without warning.You can 
also ensure that you're able to access other onion services by connecting to http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo's âOnion Service."
 }
 }

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-27 Thread translation

commit 8df905c5a872d52b73b6f2044ced5e8c0236bd41
Author: Translation commit bot 
Date:   Wed Jun 27 13:49:14 2018 +

Update translations for support-connecting
---
 ru.json | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/ru.json b/ru.json
index e8844d077..3cc7aa1d7 100644
--- a/ru.json
+++ b/ru.json
@@ -2,8 +2,8 @@
 "connecting-1": {
"id": "#connecting-1",
"control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
-   "description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
+   "title": "Tor Browser Ð½Ðµ Ð±ÑÐ´ÐµÑ Ð¿Ð¾Ð´ÐºÐ»ÑÑÐ°ÑÑÑÑ, Ð½Ð¾, 
Ð¿Ð¾ÑÐ¾Ð¶Ðµ, ÑÑÐ¾ Ð¿ÑÐ¾Ð±Ð»ÐµÐ¼Ð° Ð½Ðµ Ð¸Ð·-Ð·Ð° ÑÐµÐ½Ð·ÑÑÑ.",
+   "description": "ÐÐ´Ð½Ð¾Ð¹ Ð¸Ð· Ð½Ð°Ð¸Ð±Ð¾Ð»ÐµÐµ 
ÑÐ°ÑÐ¿ÑÐ¾ÑÑÑÐ°Ð½ÑÐ½Ð½ÑÑ Ð¿ÑÐ¾Ð±Ð»ÐµÐ¼, Ð²ÑÐ·ÑÐ²Ð°ÑÑÐ¸Ñ 
Ð¾ÑÐ¸Ð±ÐºÐ¸ ÑÐ¾ÐµÐ´Ð¸Ð½ÐµÐ½Ð¸Ñ Ð² Tor Browser, ÑÐ²Ð»ÑÐµÑÑÑ 
Ð½ÐµÐ¿ÑÐ°Ð²Ð¸Ð»ÑÐ½Ð¾ ÑÑÑÐ°Ð½Ð¾Ð²Ð»ÐµÐ½Ð½Ð¾Ðµ Ð²ÑÐµÐ¼Ñ Ð² 
ÑÐ¸ÑÑÐµÐ¼Ð½ÑÑ ÑÐ°ÑÐ°Ñ. Ð£Ð±ÐµÐ´Ð¸ÑÐµÑÑ, ÑÑÐ¾ ÑÐ¸ÑÑÐµÐ¼Ð½Ð¾Ðµ 
Ð²ÑÐµÐ¼Ñ Ð¸ ÑÐ°ÑÐ¾Ð²Ð¾Ð¹ Ð¿Ð¾ÑÑ ÑÑÑÐ°Ð½Ð¾Ð²Ð»ÐµÐ½Ñ ÑÐ¾ÑÐ½Ð¾. 
ÐÑÐ»Ð¸ ÑÑÐ¾ Ð½Ðµ ÑÐµÑÐ¸Ñ Ð¿ÑÐ¾Ð±Ð»ÐµÐ¼Ñ, ÑÐ¼. ÑÑÑÐ°Ð½Ð¸ÑÑ 
\"ÐÐ¾Ð¸ÑÐº Ð¸ ÑÑÑÑÐ°Ð½ÐµÐ½Ð¸Ðµ Ð½ÐµÐ¸ÑÐ¿ÑÐ°Ð²Ð½Ð¾ÑÑÐµÐ¹\" Ð² https://tb-manual.torproject.org/en-US/bridges.html\;>âÑÑÐºÐ¾Ð²Ð¾Ð´ÑÑÐ²Ðµ
 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ Tor Browser."
 },
 "connecting-2": {
"id": "#connecting-2",
@@ -14,7 +14,7 @@
 "connecting-3": {
"id": "#connecting-3",
"control": "connecting-3",
-   "title": "I cannot reach X.onion!",
+   "title": "Ð¯ Ð½Ðµ Ð¼Ð¾Ð³Ñ Ð¿Ð¾Ð´ÐºÐ»ÑÑÐ¸ÑÑÑÑ Ðº X.onion!",
"description": "If you cannot reach the onion service 
you desire, make sure that you have entered the 16-character onion address 
correctly: even a small mistake will stop Tor Browser from being able to reach 
the site. If you are still unable to connect to the onion service, please try 
again later. There may be a temporary connection issue, or the site operators 
may have allowed it to go offline without warning.You can 
also ensure that you're able to access other onion services by connecting to http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo's âOnion Service."
 }
 }

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-26 Thread translation

commit a0b5f918f52c170f26f500591245156d5e0edfde
Author: Translation commit bot 
Date:   Tue Jun 26 20:48:57 2018 +

Update translations for support-connecting
---
 sv.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sv.json b/sv.json
index 9f5a678cf..faf82a45b 100644
--- a/sv.json
+++ b/sv.json
@@ -2,8 +2,8 @@
 "connecting-1": {
"id": "#connecting-1",
"control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
-   "description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
+   "title": "Tor Browser ansluter inte men det verkar inte vara pÃ¥ grund 
av censur.",
+   "description": "En av de vanligaste problemen som orsakar 
anslutningsproblem till Tor Browser Ã¤r en felaktig system klocka. VÃ¤nligen se 
till att system klockan och tidszonen Ã¤r korrekt instÃ¤llda. Om det inte 
lÃ¶ser problemet, se Troubleshooting sidan i Tor Browser Manual .https://tb-manual.torproject.org/en-US/bridges.html\;> "
 },
 "connecting-2": {
"id": "#connecting-2",

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-22 Thread translation

commit f5865e0e821f40cee5f037602fa26a3959650780
Author: Translation commit bot 
Date:   Fri Jun 22 12:49:18 2018 +

Update translations for support-connecting
---
 pt.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pt.json b/pt.json
index f434f0d9a..9953913ea 100644
--- a/pt.json
+++ b/pt.json
@@ -3,7 +3,7 @@
"id": "#connecting-1",
"control": "connecting-1",
"title": "O Tor Browser nÃ£o liga, mas nÃ£o parece ser um problema com 
a censura.",
-   "description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
+   "description": "Um dos problemas mais comuns que 
causa erros de ligaÃ§Ã£o no Tor Browser Ã© um relÃ³gio do sistema incorreto. 
Por favor, certifique-se que o relÃ³gio do sistema e o fuso horÃ¡rio estÃ£o 
definidos com precisÃ£o. Se isto nÃ£o resolver o problema, consulte a pÃ¡gina 
de 'ResoluÃ§Ã£o de Problemas' no https://tb-manual.torproject.org/en-US/bridges.html\;>Tor Browser - 
Manual."
 },
 "connecting-2": {
"id": "#connecting-2",

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-21 Thread translation

commit 15915355178faab25d49a2c80f945ff0f07cb771
Author: Translation commit bot 
Date:   Thu Jun 21 07:19:06 2018 +

Update translations for support-connecting
---
 fi.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fi.json b/fi.json
index 4093d10aa..a498133a4 100644
--- a/fi.json
+++ b/fi.json
@@ -9,7 +9,7 @@
"id": "#connecting-2",
"control": "connecting-2",
"title": "Minulla on ongelmia yhdistÃ¤essÃ¤ Tor:iin enkÃ¤ keksi mikÃ¤ 
voisi olla vialla.",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "Jos sinulla on yhdistÃ¤misongelmia 
niin ole hyvÃ¤ ja valitse \"kopio Tor-logi leikepÃ¶ydÃ¤lle.\" TÃ¤mÃ¤n jÃ¤lkeen 
liitÃ¤ Tor-logi tyhjÃ¤Ã¤n tekstitiedostoon tai muuhun dokumenttiin. Sinun 
pitÃ¤isi nÃ¤hdÃ¤ joku nÃ¤istÃ¤ yleisistÃ¤ log-virheistÃ¤ (etsi seuraavia 
rivejÃ¤ Tor-logista):  Yleinen log-virhe #1 Proxy-yhteysvirhe  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:x (\"general SOCKS 
server failure\") \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to 
connect to xx..xxx..xxx.xx:x

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-21 Thread translation

commit c622b927750162b22b4cad85dec04e9bdaa80903
Author: Translation commit bot 
Date:   Thu Jun 21 06:49:16 2018 +

Update translations for support-connecting
---
 fi.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fi.json b/fi.json
index 4d3e7f911..4093d10aa 100644
--- a/fi.json
+++ b/fi.json
@@ -8,7 +8,7 @@
 "connecting-2": {
"id": "#connecting-2",
"control": "connecting-2",
-   "title": "I am having trouble connecting to Tor, and I canât figure 
out whatâs wrong.",
+   "title": "Minulla on ongelmia yhdistÃ¤essÃ¤ Tor:iin enkÃ¤ keksi mikÃ¤ 
voisi olla vialla.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
 },
 "connecting-3": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-19 Thread translation

commit 22726fbc96a5b52f7ea5cc306ef34fe51dd34bf5
Author: Translation commit bot 
Date:   Wed Jun 20 05:49:04 2018 +

Update translations for support-connecting
---
 tr.json | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/tr.json b/tr.json
index 19e7f3301..9388eb3fc 100644
--- a/tr.json
+++ b/tr.json
@@ -1,19 +1,19 @@
 {
 "connecting-1": {
-   "id": "#baglaniyor-1",
-   "control": "baglaniyor-1",
+   "id": "#baglanti-1",
+   "control": "baglanti-1",
"title": "Tor Browser baÄlantÄ± kuramÄ±yor ancak bu sorun sansÃ¼r ile 
ilgili gibi gÃ¶rÃ¼nmÃ¼yor.",
-   "description": "Tor Browser'Ä±n baÄlantÄ± 
hatalarÄ±na yok aÃ§an en bÃ¼yÃ¼k sorunlardan biri yanlÄ±Å sistem saati. 
LÃ¼tfen sistem saatiniz ve saat diliminizin doÄru ayarlandÄ±ÄÄ±ndan emin 
olun. EÄer bu probleminizi Ã§Ã¶zmezse, Sorun Giderme sayfasÄ±nahttps://tb-manual.torproject.org/en-US/bridges.html\;>Tor Browser 
KÄ±lavuzu sayfasÄ±ndan ulaÅÄ±n."
+   "description": "Tor Browser Ã¼zerinde baÄlantÄ± 
sorunlarÄ±na yol aÃ§an en bÃ¼yÃ¼k sorunlardan biri sistem saatinin yanlÄ±Å 
olmasÄ±dÄ±r. LÃ¼tfen sistem saati ve saat diliminin doÄru ayarlandÄ±ÄÄ±ndan 
emin olun. Sorun Ã§Ã¶zÃ¼lmezse, https://tb-manual.torproject.org/en-US/bridges.html\;>Tor Browser 
KÄ±lavuzu Ã¼zerindeki Sorun Giderme bÃ¶lÃ¼mÃ¼ne bakabilirsiniz."
 },
 "connecting-2": {
-   "id": "#connecting-2",
-   "control": "connecting-2",
-   "title": "Tor 'a baÄlanmakta sÄ±kÄ±ntÄ± Ã§ekiyorum ve ne de problem 
olduÄunu bulamÄ±yorum",
+   "id": "#baglanti-2",
+   "control": "baglanti-2",
+   "title": "Tor baÄlantÄ±sÄ± kurmakta sorun yaÅÄ±yorum ve sorunun ne 
olduÄunu bulamÄ±yorum.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-19 Thread translation

commit 6e8feb73f211f6deba45a11be36cd927a607dc82
Author: Translation commit bot 
Date:   Wed Jun 20 05:19:12 2018 +

Update translations for support-connecting
---
 tr.json | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tr.json b/tr.json
index 280aa9747..19e7f3301 100644
--- a/tr.json
+++ b/tr.json
@@ -1,8 +1,8 @@
 {
 "connecting-1": {
-   "id": "#connecting-1",
-   "control": "connecting-1",
-   "title": "Tor Browser baÄlanamayacak, fakat sansÃ¼r ile alakalÄ± bir 
sorun gibi gÃ¶rÃ¼nmÃ¼yor.",
+   "id": "#baglaniyor-1",
+   "control": "baglaniyor-1",
+   "title": "Tor Browser baÄlantÄ± kuramÄ±yor ancak bu sorun sansÃ¼r ile 
ilgili gibi gÃ¶rÃ¼nmÃ¼yor.",
"description": "Tor Browser'Ä±n baÄlantÄ± 
hatalarÄ±na yok aÃ§an en bÃ¼yÃ¼k sorunlardan biri yanlÄ±Å sistem saati. 
LÃ¼tfen sistem saatiniz ve saat diliminizin doÄru ayarlandÄ±ÄÄ±ndan emin 
olun. EÄer bu probleminizi Ã§Ã¶zmezse, Sorun Giderme sayfasÄ±nahttps://tb-manual.torproject.org/en-US/bridges.html\;>Tor Browser 
KÄ±lavuzu sayfasÄ±ndan ulaÅÄ±n."
 },
 "connecting-2": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-17 Thread translation

commit 13716605aa1ac3cbd72fa6ea1aa69229c210e484
Author: Translation commit bot 
Date:   Sun Jun 17 10:49:33 2018 +

Update translations for support-connecting
---
 ca.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ca.json b/ca.json
index af8c4aca9..68727e653 100644
--- a/ca.json
+++ b/ca.json
@@ -14,7 +14,7 @@
 "connecting-3": {
"id": "#connecting-3",
"control": "connecting-3",
-   "title": "I cannot reach X.onion!",
+   "title": "No puc accedir a X.onion!",
"description": "If you cannot reach the onion service 
you desire, make sure that you have entered the 16-character onion address 
correctly: even a small mistake will stop Tor Browser from being able to reach 
the site. If you are still unable to connect to the onion service, please try 
again later. There may be a temporary connection issue, or the site operators 
may have allowed it to go offline without warning.You can 
also ensure that you're able to access other onion services by connecting to http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo's âOnion Service."
 }
 }

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-06 Thread translation

commit 9cde5e574af4eac156109dd6d857d5c6325138cd
Author: Translation commit bot 
Date:   Wed Jun 6 13:48:54 2018 +

Update translations for support-connecting
---
 da.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/da.json b/da.json
index 4c11166f8..c85d4b341 100644
--- a/da.json
+++ b/da.json
@@ -3,12 +3,12 @@
"id": "#connecting-1",
"control": "connecting-1",
"title": "Tor Browser kan ikke oprette forbindelse, men det ser ikke ud 
til skyldes censur.",
-   "description": "En af de mest almindelige Ã¥rsager 
til at Tor Browser ikke kan fÃ¥ forbindelse, er at system tiden er sat forkert. 
Tjek at din system tid og tidszone er sat korrekt. Hvis ikke dette lÃ¸ser 
problemet, kan du lÃ¦se mere i https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manualen."
+   "description": "En af de mest almindelige Ã¥rsager 
til at Tor Browser ikke kan fÃ¥ forbindelse, er at systemets ur er indstillet 
forkert. SÃ¸rg venligst for at at dit systems klokkeslÃ¦t og tidszone er 
indstillet korrekt. Hvis ikke det lÃ¸ser problemet, kan du lÃ¦se mere i 
https://tb-manual.torproject.org/en-US/bridges.html\;>âTor 
Browser-manualen."
 },
 "connecting-2": {
"id": "#connecting-2",
"control": "connecting-2",
-   "title": "Jeg har problemer med at forbinde til Tor og kan ikke 
gennemskue hvad der er galt.",
+   "title": "Jeg har problemer med at oprette forbindelse til Tor og kan 
ikke gennemskue hvad der er galt.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-06-02 Thread translation

commit fe2b167564cfada36f939281d3eeef96e03c4fa7
Author: Translation commit bot 
Date:   Sat Jun 2 20:49:04 2018 +

Update translations for support-connecting
---
 lt.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lt.json b/lt.json
index 4d3e7f911..21bcd04d3 100644
--- a/lt.json
+++ b/lt.json
@@ -8,7 +8,7 @@
 "connecting-2": {
"id": "#connecting-2",
"control": "connecting-2",
-   "title": "I am having trouble connecting to Tor, and I canât figure 
out whatâs wrong.",
+   "title": "Man iÅ¡kilo sunkumÅ³ jungiantis prie Tor ir negaliu 
iÅ¡siaiÅ¡kinti kas nutiko.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
 },
 "connecting-3": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-31 Thread translation

commit 149fe29f91244a4cb60cad1323f4fb8b047239ef
Author: Translation commit bot 
Date:   Thu May 31 08:19:17 2018 +

Update translations for support-connecting
---
 eu.json | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/eu.json b/eu.json
index 4d3e7f911..fa47a5157 100644
--- a/eu.json
+++ b/eu.json
@@ -2,19 +2,19 @@
 "connecting-1": {
"id": "#connecting-1",
"control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
+   "title": "Tor nabigatzailea ezin da konektatu, baina ez dirudi 
zentsurarekin loturiko arazorik dagoenik.",
"description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
 },
 "connecting-2": {
"id": "#connecting-2",
"control": "connecting-2",
-   "title": "I am having trouble connecting to Tor, and I canât figure 
out whatâs wrong.",
+   "title": "Arazoak izaten n abil Tor-era konektatzen, baina ezin dut 
asmatu zein den arrazoia.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
 },
 "connecting-3":

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-25 Thread translation

commit 187e1070c2ee5634228298ab0118319685ec5ce1
Author: Translation commit bot 
Date:   Fri May 25 09:19:52 2018 +

Update translations for support-connecting
---
 pt_PT.json | 20 
 1 file changed, 20 insertions(+)

diff --git a/pt_PT.json b/pt_PT.json
new file mode 100644
index 0..4d3e7f911
--- /dev/null
+++ b/pt_PT.json
@@ -0,0 +1,20 @@
+{
+"connecting-1": {
+   "id": "#connecting-1",
+   "control": "connecting-1",
+   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
+   "description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
+},
+"connecting-2": {
+   "id": "#connecting-2",
+   "control": "connecting-2",
+   "title": "I am having trouble connecting to Tor, and I canât figure 
out whatâs wrong.",
+   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+},
+"connecting-3": {
+   "id": "#connecting-3",
+   "control": "connecting-3",
+   "title": "I cannot reach X.onion!",
+   "description": "If you cannot reach the onion

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-21 Thread translation

commit 458943fc5881dc3ff457bf93b5b5b3b275cca0dd
Author: Translation commit bot 
Date:   Mon May 21 15:48:58 2018 +

Update translations for support-connecting
---
 pt_BR.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pt_BR.json b/pt_BR.json
index 222d00ffd..cb1197435 100644
--- a/pt_BR.json
+++ b/pt_BR.json
@@ -9,7 +9,7 @@
"id": "#conectando-2",
"control": "conectando-2",
"title": "Estou tendo problemas para conectar com o Tor e nÃ£o consigo 
descobrir o que estÃ¡ acontecendo de errado.",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "Se vocÃª estiver tendo dificuldades 
para se conectar, por favor selecione a opÃ§Ã£o \"copiar o log do Tor na Ã¡rea 
de trabalho\". Em seguida, copie o log to Tor em um arquivo de texto ou outro 
documento. Normalmente vocÃª verÃ¡ um dos erros mais comuns (procure as 
seguintes linhas no seu log do Tor):Erros comuns #1: falha de conexÃ£o 
com o Proxy 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:x (\"general SOCKS server failure\")

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-19 Thread translation

commit 378ade1a2cf9ffe775b01a1af5a3c983fdc11fe3
Author: Translation commit bot 
Date:   Sat May 19 23:19:04 2018 +

Update translations for support-connecting
---
 id.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/id.json b/id.json
index 9883c41bd..16b8c9d23 100644
--- a/id.json
+++ b/id.json
@@ -9,7 +9,7 @@
"id": "#connecting-2",
"control": "connecting-2",
"title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak 
dapat mengetahui apa yang salah.",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "Jika Anda mengalami masalah dalam 
terhubung ke jaringan Tor, pilih opsi \"copy Tor log to clipboard.\" Lalu paste 
Tor log ke Notepad atau dokumen lain. Anda seharusnya melihat log error yang 
umum (lihat baris-baris berikut di Tor log): Common log error #1: 
Kegagalan koneksi proxy 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:x (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to 
xx..xxx..xxx.xx:x

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-17 Thread translation

commit 1514c7adec584c7b3cb32769114ba4421ca02036
Author: Translation commit bot 
Date:   Thu May 17 23:19:38 2018 +

Update translations for support-connecting
---
 bn_BD.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bn_BD.json b/bn_BD.json
index fc564d1bf..f31135294 100644
--- a/bn_BD.json
+++ b/bn_BD.json
@@ -9,7 +9,7 @@
"id": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-2",
"control": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-2",
"title": "à¦à¦®à¦¾à¦° à¦à¦° à¦à¦° à¦¸à¦¾à¦¥à§ à¦¸à¦à¦¯à§à¦à§ 
à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¹à¦à§à¦à§, à¦à¦¬à¦ à¦à¦®à¦¿ à¦à¦¿ à¦à§à¦² 
à¦¬à§à¦à¦¤à§ à¦ªà¦¾à¦°à¦à¦¿ à¦¨à¦¾à¥¤",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "à¦¯à¦¦à¦¿ à¦à¦ªà¦¨à¦¾à¦° 
à¦¸à¦à¦¯à§à¦à§à¦° à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¹à¦¯à¦¼, à¦¦à¦¯à¦¼à¦¾ à¦à¦°à§ 
\"à¦à¦° à¦²à¦ à¦à§à¦²à¦¿à¦ªà¦¬à§à¦°à§à¦¡à§ à¦à¦ªà¦¿ à¦à¦°à§à¦¨\" 
à¦¬à¦¿à¦à¦²à§à¦ªà¦à¦¿ à¦¨à¦¿à¦°à§à¦¬à¦¾à¦à¦¨ à¦à¦°à§à¦¨à¥¤ 
à¦¤à¦¾à¦°à¦ªà¦° à¦à¦° à¦²à¦ à¦à¦à¦à¦¿ à¦à§à¦à§à¦¸à¦ à¦«à¦¾à¦à¦² 
à¦¬à¦¾ à¦à¦¨à§à¦¯ à¦¡à¦à§à¦®à§à¦¨à§à¦-à¦ à¦ªà§à¦¸à§à¦ 
à¦à¦°à§à¦¨à¥¤à¦à¦ªà¦¨à¦¿ à¦à¦ à¦¸à¦¾à¦§à¦¾à¦°à¦£ à¦²à¦ 
à¦¤à§à¦°à§à¦à¦¿à¦à§à¦²à¦¿à¦° à¦à¦à¦à¦¿ à¦¦à§à¦à¦¤à§ à¦ªà¦¾à¦¬à§à¦¨ 
(à¦à¦ªà¦¨à¦¾à¦° à¦à¦° à¦²à¦¾à¦à¦¨à§à¦° à¦¨à¦¿à¦®à§à¦¨à¦²à¦¿à¦à¦¿à¦¤

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-17 Thread translation

commit 571f1d22f164c7698b1fd25aa5cffce9b07a5e09
Author: Translation commit bot 
Date:   Thu May 17 19:19:03 2018 +

Update translations for support-connecting
---
 bn_BD.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bn_BD.json b/bn_BD.json
index 3cff5e619..fc564d1bf 100644
--- a/bn_BD.json
+++ b/bn_BD.json
@@ -3,7 +3,7 @@
"id": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-1",
"control": "à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-1",
"title": "à¦à¦° à¦¬à§à¦°à¦¾à¦à¦à¦¾à¦° à¦¸à¦à¦¯à§à¦ à¦à¦°à¦¬à§ 
à¦¨à¦¾, à¦¤à¦¬à§ à¦à¦à¦¿ à¦¸à§à¦¨à§à¦¸à¦°à¦¶à¦¿à¦ªà§à¦° à¦¸à¦¾à¦¥à§ 
à¦à¦à¦à¦¿ à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¬à¦²à§ à¦®à¦¨à§ à¦¹à¦à§à¦à§ à¦¨à¦¾à¥¤",
-   "description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
+   "description": "à¦à¦° à¦¬à§à¦°à¦¾à¦à¦à¦¾à¦°à§à¦° 
à¦¸à¦à¦¯à§à¦à§ à¦¸à¦¾à¦§à¦¾à¦°à¦£à¦¤ à¦¯à§ à¦¸à¦®à¦¸à§à¦¤ à¦à¦¾à¦°à¦£à§ 
à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¹à¦¯à¦¼ à¦¤à¦¾ à¦¹à¦² à¦à¦à¦à¦¿ à¦à§à¦² 
à¦¸à¦¿à¦¸à§à¦à§à¦® à¦à¦¡à¦¼à¦¿à¥¤ à¦à¦ªà¦¨à¦¾à¦° à¦¸à¦¿à¦¸à§à¦à§à¦® 
à¦à¦¡à¦¼à¦¿ à¦ à¦¸à¦®à¦¯à¦¼ à¦à§à¦¨ à¦¸à¦ à¦¿à¦à¦à¦¾à¦¬à§ à¦¸à§à¦ 
à¦à¦°à¦¾ à¦à¦à§ à¦¤à¦¾ à¦¨à¦¿à¦¶à§à¦à¦¿à¦¤ à¦à¦°à§à¦¨à¥¤ à¦à¦ 
à¦¸à¦®à¦¸à§à¦¯à¦¾à¦à¦¿ à¦ à¦¿à¦ à¦¨à¦¾ à¦¹à¦²à§, à¦à¦° 
à¦¬à§à¦°à¦¾à¦à¦à¦¾à¦° à¦®à§à¦¯à¦¾à¦¨à§à¦¯à¦¼à§à¦² à¦à¦° 
à¦à§à¦°à¦¾à¦¬à¦²à¦¶à§à¦à¦¿à¦ à¦ªà§à¦·à§à¦ à¦¾à¦à¦¿https://tb-manual.torproject.org/en-US/bridges.html\;> 
à¦¦à§à¦à§à¦¨à¥¤"
 },
 "connecting-2": {
"id": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-2",

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-11 Thread translation

commit 108b378081e7a37669e81034a83dd55f8d508ca9
Author: Translation commit bot 
Date:   Fri May 11 20:49:05 2018 +

Update translations for support-connecting
---
 ru.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ru.json b/ru.json
index 4d3e7f911..e8844d077 100644
--- a/ru.json
+++ b/ru.json
@@ -8,7 +8,7 @@
 "connecting-2": {
"id": "#connecting-2",
"control": "connecting-2",
-   "title": "I am having trouble connecting to Tor, and I canât figure 
out whatâs wrong.",
+   "title": "Ð£ Ð¼ÐµÐ½Ñ Ð¿ÑÐ¾Ð±Ð»ÐµÐ¼Ñ Ñ Ð¿Ð¾Ð´ÐºÐ»ÑÑÐµÐ½Ð¸ÐµÐ¼ Ðº 
Tor Ð¸ Ñ Ð½Ðµ Ð¼Ð¾Ð³Ñ Ð¿Ð¾Ð½ÑÑÑ, ÑÑÐ¾ Ð½Ðµ ÑÐ°Ðº.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
 },
 "connecting-3": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-10 Thread translation

commit d0a2630acaeec1d4efafe0dcd083e44fac4d25f2
Author: Translation commit bot 
Date:   Thu May 10 14:19:06 2018 +

Update translations for support-connecting
---
 pt_BR.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pt_BR.json b/pt_BR.json
index b9cc3f9b8..222d00ffd 100644
--- a/pt_BR.json
+++ b/pt_BR.json
@@ -2,7 +2,7 @@
 "connecting-1": {
"id": "#conectando-1",
"control": "conectando-1",
-   "title": "O Tor Browser nÃ£o estÃ¡ funcionando, mas nÃ£o parece ser 
algo relacionado Ã  censura.",
+   "title": "O Tor Browser nÃ£o estÃ¡ funcionando, mas nÃ£o parece ser 
algo relacionado a censura.",
"description": "Um dos problemas mais comuns que 
causa erros de conexÃ£o no Navegador Tor Ã© um relÃ³gio do sistema incorreto. 
Por favor, certifique-se de que o relÃ³gio do sistema e o fuso horÃ¡rio estejam 
definidos com precisÃ£o. Se isso nÃ£o resolver o problema, consulte a pÃ¡gina 
SoluÃ§Ã£o de Problemas no manual do Navegador Tor."
 },
 "connecting-2": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-10 Thread translation

commit 7e72b890d1b656a1090597e5162010588b4192ba
Author: Translation commit bot 
Date:   Thu May 10 10:48:57 2018 +

Update translations for support-connecting
---
 bn_BD.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bn_BD.json b/bn_BD.json
index 217af122b..3cff5e619 100644
--- a/bn_BD.json
+++ b/bn_BD.json
@@ -15,6 +15,6 @@
"id": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-3",
"control": "à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-3",
"title": "à¦à¦®à¦¿ X.onion à¦ à¦ªà§à¦à¦à¦¾à¦¤à§ à¦ªà¦¾à¦°à¦à¦¿ 
à¦¨à¦¾!",
-   "description": "à¦¯à¦¦à¦¿ à¦à¦ªà¦¨à¦¿ à¦ªà§à¦à¦¯à¦¼à¦¾à¦ 
à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾à¦¤à§ à¦ªà§à¦à¦à¦¾à¦¤à§ à¦¨à¦¾ à¦ªà¦¾à¦°à§à¦¨, 
à¦¤à¦¬à§ à¦¨à¦¿à¦¶à§à¦à¦¿à¦¤ à¦à¦°à§à¦¨ à¦¯à§ à¦à¦ªà¦¨à¦¿ 16-à¦
à¦à§à¦·à¦°à§à¦° à¦ªà§à¦à¦¯à¦¼à¦¾à¦à§à¦° à¦ à¦¿à¦à¦¾à¦¨à¦¾à¦¯à¦¼ à¦¸à¦ 
à¦¿à¦à¦à¦¾à¦¬à§ à¦ªà§à¦°à¦¬à§à¦¶ à¦à¦°à§à¦à§à¦¨: à¦à¦®à¦¨à¦à¦¿ 
à¦à¦à¦à¦¿ à¦à§à¦ à¦à§à¦² à¦à¦°à§ à¦¬à§à¦°à¦¾à¦à¦à¦¾à¦°à¦à¦¿ 
à¦¸à¦¾à¦à¦à§ à¦ªà§à¦à¦à¦¾à¦¤à§ à¦¸à¦à§à¦·à¦® à¦¹à¦¬à§à¦¨à¦¾à¥¤ 
à¦¯à¦¦à¦¿ à¦à¦ªà¦¨à¦¿ à¦à¦à¦¨à¦ à¦ªà§à¦à¦¯à¦¼à¦¾à¦ à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ 
à¦¸à¦à¦¯à§à¦ à¦à¦°à¦¤à§ à¦à¦à§à¦·à¦® à¦¹à¦¨, à¦¤à¦¾à¦¹à¦²à§ à¦ªà¦°à§ 
à¦à¦¬à¦¾à¦° à¦à§à¦·à§à¦à¦¾ à¦à¦°à§à¦¨à¥¤ à¦à¦à¦à¦¿ à¦
à¦¸à§à¦¥à¦¾à¦¯à¦¼à§ à¦¸à¦à¦¯à§à¦ à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¹à¦¤à§ 
à¦ªà¦¾à¦°à§, à¦¬à¦¾ à¦¸à¦¾à¦à¦ à¦à¦ªà¦¾à¦°à§à¦à¦° à¦à¦à¦¿ 
à¦¸à¦¤à¦°à§à¦à¦¬à¦¾à¦°à§à¦¤à¦¾ à¦à¦¾à¦¡à¦¼à¦¾à¦ à¦à¦«à¦²à¦¾à¦à¦¨à§ 
à¦¯à§à¦¤à§ à¦à¦¨à§à¦®à¦¤à¦¿ à¦¦à§à¦à¦¯à¦¼à¦¾ à¦¹à¦¤à§
  à¦ªà¦¾à¦°à§à¥¤ à¦à¦ªà¦¨à¦¿ à¦à¦ªà¦¨à¦¿ DuckDuckGo à¦à¦° 
à¦ªà§à¦à¦¯à¦¼à¦¾à¦ à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ à¦¸à¦à¦¯à§à¦ à¦à¦°à§ à¦
à¦¨à§à¦¯ à¦ªà§à¦à¦¯à¦¼à¦¾à¦ à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ à¦
à§à¦¯à¦¾à¦à§à¦¸à§à¦¸ à¦à¦°à¦¤à§ à¦ªà¦¾à¦°à¦¬à§à¦¨ à¦¤à¦¾ 
à¦¨à¦¿à¦¶à§à¦à¦¿à¦¤ à¦à¦°à¦¤à§ à¦ªà¦¾à¦°à§à¦¨à¥¤"
+   "description": "à¦¯à¦¦à¦¿ à¦à¦ªà¦¨à¦¿ à¦
à¦¨à¦¿à¦¯à¦¼à¦¨ à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾à¦¤à§ à¦ªà§à¦à¦à¦¾à¦¤à§ à¦¨à¦¾ 
à¦ªà¦¾à¦°à§à¦¨, à¦¤à¦¬à§ à¦¨à¦¿à¦¶à§à¦à¦¿à¦¤ à¦à¦°à§à¦¨ à¦¯à§ 
à¦à¦ªà¦¨à¦¿ 16-à¦à¦à§à¦·à¦°à§à¦° à¦à¦¨à¦¿à¦¯à¦¼à¦¨-à¦° à¦ 
à¦¿à¦à¦¾à¦¨à¦¾à¦¯à¦¼ à¦¸à¦ à¦¿à¦à¦à¦¾à¦¬à§ à¦ªà§à¦°à¦¬à§à¦¶ 
à¦à¦°à§à¦à§à¦¨: à¦à¦®à¦¨à¦à¦¿ à¦à¦à¦à¦¿ à¦à§à¦ à¦à§à¦²à¦à¦° 
à¦à¦¾à¦°à¦¨à§ à¦à¦°à§ à¦¬à§à¦°à¦¾à¦à¦à¦¾à¦°à¦à¦¿ à¦¸à¦¾à¦à¦à§ 
à¦ªà§à¦à¦à¦¾à¦¤à§ à¦¸à¦à§à¦·à¦® à¦¹à¦¬à§à¦¨à¦¾à¥¤ à¦¯à¦¦à¦¿ à¦à¦ªà¦¨à¦¿ 
à¦à¦à¦¨à¦ à¦à¦¨à¦¿à¦¯à¦¼à¦¨ à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ à¦¸à¦à¦¯à§à¦ 
à¦à¦°à¦¤à§ à¦à¦à§à¦·à¦® à¦¹à¦¨, à¦¤à¦¾à¦¹à¦²à§ à¦ªà¦°à§ à¦à¦¬à¦¾à¦° 
à¦à§à¦·à§à¦à¦¾ à¦à¦°à§à¦¨à¥¤ à¦à¦à¦à¦¿ à¦à¦¸à§à¦¥à¦¾à¦¯à¦¼à§ 
à¦¸à¦à¦¯à§à¦ à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¹à¦¤à§ à¦ªà¦¾à¦°à§, à¦¬à¦¾ à¦¸à¦¾à¦à¦ 
à¦à¦ªà¦¾à¦°à§à¦à¦°à¦°à¦¾ à¦à¦à¦¿à¦à§ à¦¸à¦¤à¦°à§à¦à¦¬à¦¾à¦°à§à¦¤à¦¾ 
à¦à¦¾à¦¡à¦¼à¦¾à¦ à¦à¦«à¦²à¦¾à¦à¦¨à§ à¦¯à§à¦¤à§ à¦à¦¨
 à§à¦®à¦¤à¦¿ à¦¦à¦¿à¦¯à¦¼à§à¦à§à¥¤ à¦à¦ªà¦¨à¦¿ http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo à¦à¦° à¦à¦¨à¦¿à¦¯à¦¼à¦¨ 
à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ à¦¸à¦à¦¯à§à¦ à¦à¦°à§ à¦à¦¨à§à¦¯ à¦à¦¨à¦¿à¦¯à¦¼à¦¨ 
à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ à¦à§à¦¯à¦¾à¦à§à¦¸à§à¦¸ à¦à¦°à¦¤à§ 
à¦ªà¦¾à¦°à¦¬à§à¦¨ à¦¤à¦¾ à¦¨à¦¿à¦¶à§à¦à¦¿à¦¤ à¦à¦°à¦¤à§ 
à¦ªà¦¾à¦°à§à¦¨à¥¤"
 }
 }

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-08 Thread translation

commit 3019288eb5dec7befeea1b05ec1d689afdd18043
Author: Translation commit bot 
Date:   Tue May 8 06:19:53 2018 +

Update translations for support-connecting
---
 bn_BD.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/bn_BD.json b/bn_BD.json
index 9d86e19ce..217af122b 100644
--- a/bn_BD.json
+++ b/bn_BD.json
@@ -14,7 +14,7 @@
 "connecting-3": {
"id": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-3",
"control": "à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-3",
-   "title": "I cannot reach X.onion!",
-   "description": "If you cannot reach the onion service 
you desire, make sure that you have entered the 16-character onion address 
correctly: even a small mistake will stop Tor Browser from being able to reach 
the site. If you are still unable to connect to the onion service, please try 
again later. There may be a temporary connection issue, or the site operators 
may have allowed it to go offline without warning.You can 
also ensure that you're able to access other onion services by connecting to http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo's âOnion Service."
+   "title": "à¦à¦®à¦¿ X.onion à¦ à¦ªà§à¦à¦à¦¾à¦¤à§ à¦ªà¦¾à¦°à¦à¦¿ 
à¦¨à¦¾!",
+   "description": "à¦¯à¦¦à¦¿ à¦à¦ªà¦¨à¦¿ à¦ªà§à¦à¦¯à¦¼à¦¾à¦ 
à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾à¦¤à§ à¦ªà§à¦à¦à¦¾à¦¤à§ à¦¨à¦¾ à¦ªà¦¾à¦°à§à¦¨, 
à¦¤à¦¬à§ à¦¨à¦¿à¦¶à§à¦à¦¿à¦¤ à¦à¦°à§à¦¨ à¦¯à§ à¦à¦ªà¦¨à¦¿ 16-à¦
à¦à§à¦·à¦°à§à¦° à¦ªà§à¦à¦¯à¦¼à¦¾à¦à§à¦° à¦ à¦¿à¦à¦¾à¦¨à¦¾à¦¯à¦¼ à¦¸à¦ 
à¦¿à¦à¦à¦¾à¦¬à§ à¦ªà§à¦°à¦¬à§à¦¶ à¦à¦°à§à¦à§à¦¨: à¦à¦®à¦¨à¦à¦¿ 
à¦à¦à¦à¦¿ à¦à§à¦ à¦à§à¦² à¦à¦°à§ à¦¬à§à¦°à¦¾à¦à¦à¦¾à¦°à¦à¦¿ 
à¦¸à¦¾à¦à¦à§ à¦ªà§à¦à¦à¦¾à¦¤à§ à¦¸à¦à§à¦·à¦® à¦¹à¦¬à§à¦¨à¦¾à¥¤ 
à¦¯à¦¦à¦¿ à¦à¦ªà¦¨à¦¿ à¦à¦à¦¨à¦ à¦ªà§à¦à¦¯à¦¼à¦¾à¦ à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ 
à¦¸à¦à¦¯à§à¦ à¦à¦°à¦¤à§ à¦à¦à§à¦·à¦® à¦¹à¦¨, à¦¤à¦¾à¦¹à¦²à§ à¦ªà¦°à§ 
à¦à¦¬à¦¾à¦° à¦à§à¦·à§à¦à¦¾ à¦à¦°à§à¦¨à¥¤ à¦à¦à¦à¦¿ à¦
à¦¸à§à¦¥à¦¾à¦¯à¦¼à§ à¦¸à¦à¦¯à§à¦ à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¹à¦¤à§ 
à¦ªà¦¾à¦°à§, à¦¬à¦¾ à¦¸à¦¾à¦à¦ à¦à¦ªà¦¾à¦°à§à¦à¦° à¦à¦à¦¿ 
à¦¸à¦¤à¦°à§à¦à¦¬à¦¾à¦°à§à¦¤à¦¾ à¦à¦¾à¦¡à¦¼à¦¾à¦ à¦à¦«à¦²à¦¾à¦à¦¨à§ 
à¦¯à§à¦¤à§ à¦à¦¨à§à¦®à¦¤à¦¿ à¦¦à§à¦à¦¯à¦¼à¦¾ à¦¹à¦¤à§
  à¦ªà¦¾à¦°à§à¥¤ à¦à¦ªà¦¨à¦¿ à¦à¦ªà¦¨à¦¿ DuckDuckGo à¦à¦° 
à¦ªà§à¦à¦¯à¦¼à¦¾à¦ à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ à¦¸à¦à¦¯à§à¦ à¦à¦°à§ à¦
à¦¨à§à¦¯ à¦ªà§à¦à¦¯à¦¼à¦¾à¦ à¦ªà¦°à¦¿à¦·à§à¦¬à¦¾ à¦
à§à¦¯à¦¾à¦à§à¦¸à§à¦¸ à¦à¦°à¦¤à§ à¦ªà¦¾à¦°à¦¬à§à¦¨ à¦¤à¦¾ 
à¦¨à¦¿à¦¶à§à¦à¦¿à¦¤ à¦à¦°à¦¤à§ à¦ªà¦¾à¦°à§à¦¨à¥¤"
 }
 }

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-07 Thread translation

commit e6df53a64b29eba5bc614c9aece1c92d0ab1d4e0
Author: Translation commit bot 
Date:   Tue May 8 05:20:17 2018 +

Update translations for support-connecting
---
 bn_BD.json | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/bn_BD.json b/bn_BD.json
index 1d53adab5..9d86e19ce 100644
--- a/bn_BD.json
+++ b/bn_BD.json
@@ -1,19 +1,19 @@
 {
 "connecting-1": {
-   "id": "#connecting-1",
-   "control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
+   "id": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-1",
+   "control": "à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-1",
+   "title": "à¦à¦° à¦¬à§à¦°à¦¾à¦à¦à¦¾à¦° à¦¸à¦à¦¯à§à¦ à¦à¦°à¦¬à§ 
à¦¨à¦¾, à¦¤à¦¬à§ à¦à¦à¦¿ à¦¸à§à¦¨à§à¦¸à¦°à¦¶à¦¿à¦ªà§à¦° à¦¸à¦¾à¦¥à§ 
à¦à¦à¦à¦¿ à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¬à¦²à§ à¦®à¦¨à§ à¦¹à¦à§à¦à§ à¦¨à¦¾à¥¤",
"description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
 },
 "connecting-2": {
-   "id": "#connecting-2",
-   "control": "connecting-2",
-   "title": "à¦à¦®à¦¿ à¦à¦° à¦¸à¦à¦¯à§à¦à§ à¦¸à¦®à¦¸à§à¦¯à¦¾ 
à¦¹à¦à§à¦à§, à¦à¦¬à¦ à¦à¦®à¦¿ à¦à¦¿ à¦à§à¦² à¦¬à§à¦à¦¤à§ 
à¦ªà¦¾à¦°à¦à¦¿ à¦¨à¦¾à¥¤",
+   "id": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-2",
+   "control": "# à¦¸à¦à¦¯à§à¦ à¦¹à¦à§à¦à§-2",
+   "title": "à¦à¦®à¦¾à¦° à¦à¦° à¦à¦° à¦¸à¦¾à¦¥à§ à¦¸à¦à¦¯à§à¦à§ 
à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¹à¦à§à¦à§, à¦à¦¬à¦ à¦à¦®à¦¿ à¦à¦¿ à¦à§à¦² 
à¦¬à§à¦à¦¤à§ à¦ªà¦¾à¦°à¦à¦¿ à¦¨à¦¾à¥¤",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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]

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-05-05 Thread translation

commit 134a809247ff470b2860176ef919c4ac94af877a
Author: Translation commit bot 
Date:   Sat May 5 22:50:09 2018 +

Update translations for support-connecting
---
 pt_BR.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pt_BR.json b/pt_BR.json
index 3000c283b..b9cc3f9b8 100644
--- a/pt_BR.json
+++ b/pt_BR.json
@@ -2,7 +2,7 @@
 "connecting-1": {
"id": "#conectando-1",
"control": "conectando-1",
-   "title": "O Navegador Tor nÃ£o se conectarÃ¡, mas nÃ£o parece ser um 
problema com a censura.",
+   "title": "O Tor Browser nÃ£o estÃ¡ funcionando, mas nÃ£o parece ser 
algo relacionado Ã  censura.",
"description": "Um dos problemas mais comuns que 
causa erros de conexÃ£o no Navegador Tor Ã© um relÃ³gio do sistema incorreto. 
Por favor, certifique-se de que o relÃ³gio do sistema e o fuso horÃ¡rio estejam 
definidos com precisÃ£o. Se isso nÃ£o resolver o problema, consulte a pÃ¡gina 
SoluÃ§Ã£o de Problemas no manual do Navegador Tor."
 },
 "connecting-2": {

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-04-28 Thread translation

commit 0398ab334ef1bccba220ccfe705e000977d9e1c9
Author: Translation commit bot 
Date:   Sat Apr 28 22:20:52 2018 +

Update translations for support-connecting
---
 da.json | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/da.json b/da.json
index 4d3e7f911..4c11166f8 100644
--- a/da.json
+++ b/da.json
@@ -2,19 +2,19 @@
 "connecting-1": {
"id": "#connecting-1",
"control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
-   "description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
+   "title": "Tor Browser kan ikke oprette forbindelse, men det ser ikke ud 
til skyldes censur.",
+   "description": "En af de mest almindelige Ã¥rsager 
til at Tor Browser ikke kan fÃ¥ forbindelse, er at system tiden er sat forkert. 
Tjek at din system tid og tidszone er sat korrekt. Hvis ikke dette lÃ¸ser 
problemet, kan du lÃ¦se mere i https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manualen."
 },
 "connecting-2": {
"id": "#connecting-2",
"control": "connecting-2",
-   "title": "I am having trouble connecting to Tor, and I canât figure 
out whatâs wrong.",
+   "title": "Jeg har problemer med at forbinde til Tor og kan ikke 
gennemskue hvad der er galt.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): It seems 
that our clock is behind by 1 days, 0 hours, 1

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-04-24 Thread translation

commit c3b220a2a451688e4f79dd47834db0b3407d587d
Author: Translation commit bot 
Date:   Tue Apr 24 20:20:07 2018 +

Update translations for support-connecting
---
 sk_SK.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sk_SK.json b/sk_SK.json
index 4d3e7f911..9584483d7 100644
--- a/sk_SK.json
+++ b/sk_SK.json
@@ -2,13 +2,13 @@
 "connecting-1": {
"id": "#connecting-1",
"control": "connecting-1",
-   "title": "Tor Browser won't connect, but it doesnât seem to be an 
issue with censorship.",
+   "title": "Tor Browser sa nevie pripojiÅ¥ ale nezdÃ¡ sa, Å¾e by to bol 
problÃ©m s cenzÃºrou.",
"description": "One of the most common issues that 
causes connection errors in Tor Browser is an incorrect system clock. Please 
make sure your system clock and timezone are set accurately. If this doesn't 
fix the problem, see the âTroubleshooting page on the https://tb-manual.torproject.org/en-US/bridges.html\;>âTor Browser 
manual."
 },
 "connecting-2": {
"id": "#connecting-2",
"control": "connecting-2",
-   "title": "I am having trouble connecting to Tor, and I canât figure 
out whatâs wrong.",
+   "title": "MÃ¡m problÃ©m pripojiÅ¥ sa k Tor a neviem prÃsÅ¥ na to v 
Äom je problÃ©m.",
"description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
 },

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-04-20 Thread translation

commit 9eb87c0b9688059f0b334d85d2a6350c3d1a2c30
Author: Translation commit bot 
Date:   Sat Apr 21 04:49:54 2018 +

Update translations for support-connecting
---
 zh_CN.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/zh_CN.json b/zh_CN.json
index 19d37ef0e..f70a3941e 100644
--- a/zh_CN.json
+++ b/zh_CN.json
@@ -9,7 +9,7 @@
"id": "#è¿æ¥-2",
"control": "è¿æ¥-2",
"title": "æ æ³è¿æ¥å° 
Torï¼æä¸ç¥éåçäºä»ä¹ä»ä¹éè¯¯ã",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "å¦ææ¨çè¿æ¥åºç°é®é¢ï¼è¯·éæ©âå¤å¶Toræ¥å¿å°åªè´´æ¿âéé¡¹ãç¶åç²è´´Toræ¥å¿å°ææ¬æä»¶æè
å¶ä»ææ¡£æ 
¼å¼ãæ¨åºè¯¥è½å¤å¨ç²è´´çToræ¥å¿ä¸åç°è¿äºå¸¸è§é®é¢ï¼è¯·å¨Toræ¥å¿éå¯»æ¾å¦ä¸æç¤ºçéè¯¯ï¼:
 å¸¸è§éè¯¯#1: ä»£çè¿æ¥å¤±è´¥ 
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:x (\\\"general SOCKS server 
failure\\\") \\n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
to xx..xxx..xxx.xx:x

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-04-18 Thread translation

commit 5f8c049ab9b4d28650ddaa2aac77914d5ce339f6
Author: Translation commit bot 
Date:   Wed Apr 18 16:20:22 2018 +

Update translations for support-connecting
---
 fr.json | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/fr.json b/fr.json
index 7fc09c393..45e706869 100644
--- a/fr.json
+++ b/fr.json
@@ -2,8 +2,8 @@
 "connecting-1": {
"id": "#connexion-1",
"control": "connexion-1",
-   "title": "Le navigateur Tor nâarrive pas Ã  se connecter, mais il ne 
semble pas que ce soit un problÃ¨me de censure.",
-   "description": "Lâun des problÃ¨mes les plus 
courants qui entraÃ®ne des erreurs de connexion dans le navigateur Tor est une 
horloge systÃ¨me qui nâest pas Ã  lâheure. Veuillez vous assurer que votre 
horloge systÃ¨me et votre fuseau horaire sont rÃ©glÃ©s avec prÃ©cision. Si le 
problÃ¨me persiste, voir la page DÃ©pannage du https://tb-manual.torproject.org/fr/bridges.html\;>âguide du 
navigateur Tor."
+   "title": "Le Navigateur Tor nâarrive pas Ã  se connecter, mais il ne 
semble pas que ce soit un problÃ¨me de censure.",
+   "description": "Lâun des problÃ¨mes les plus 
courants qui entraÃ®ne des erreurs de connexion dans le Navigateur Tor est une 
horloge systÃ¨me qui nâest pas Ã  lâheure. Veuillez vous assurer que votre 
horloge systÃ¨me et votre fuseau horaire sont rÃ©glÃ©s avec prÃ©cision. Si le 
problÃ¨me persiste, voir la page DÃ©pannage du https://tb-manual.torproject.org/fr/bridges.html\;>âguide du 
Navigateur Tor."
 },
 "connecting-2": {
"id": "#connexion-2",
@@ -15,6 +15,6 @@
"id": "#connexion-3",
"control": "connexion-3",
"title": "Je ne peux pas accÃ©der Ã  X.onionâ!",
-   "description": "Si vous ne pouvez pas atteindre le 
service oignon que vous souhaitez, assurez-vous dâavoir saisi correctement 
lâadresse oignon de 16 caractÃ¨res. Toute erreur, mÃªme minime, empÃªchera le 
navigateur Tor dâatteindre le site. Si vous nâarrivez toujours pas Ã  vous 
connecter au service oignon, veuillez ressayer ultÃ©rieurement. Il pourrait y 
avoir un problÃ¨me temporaire de connexion ou les exploitants du site 
pourraient lâavoir dÃ©sactivÃ© sans avertissement.Vous 
pouvez aussi vous assurer que vous arrivez Ã  accÃ©der Ã  dâautres services 
oignon en vous connectant au service oignon de http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo.\n\n"
+   "description": "Si vous ne pouvez pas atteindre le 
service oignon que vous souhaitez, assurez-vous dâavoir saisi correctement 
lâadresse oignon de 16 caractÃ¨res. Toute erreur, mÃªme minime, empÃªchera le 
Navigateur Tor dâatteindre le site. Si vous nâarrivez toujours pas Ã  vous 
connecter au service oignon, veuillez ressayer ultÃ©rieurement. Il pourrait y 
avoir un problÃ¨me temporaire de connexion ou les exploitants du site 
pourraient lâavoir dÃ©sactivÃ© sans avertissement.Vous 
pouvez aussi vous assurer que vous arrivez Ã  accÃ©der Ã  dâautres services 
oignon en vous connectant au service oignon de http://3g2upl4pq6kufc4m.onion\;>DuckDuckGo.\n\n"
 }
 }

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-04-18 Thread translation

commit 002874af664d6593928044adef709ee7401d784c
Author: Translation commit bot 
Date:   Wed Apr 18 07:49:54 2018 +

Update translations for support-connecting
---
 ja.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ja.json b/ja.json
index 4a2169eb3..e1eece31b 100644
--- a/ja.json
+++ b/ja.json
@@ -9,7 +9,7 @@
"id": "#æ¥ç¶-2",
"control": "æ¥ç¶-2",
"title": 
"Torã«ã¢ã¯ã»ã¹ã§ããªãããä½ãåé¡ãªã®ãåããã¾ããã",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "Torã«ã¢ã¯ã»ã¹ã§ããªãå 
´åããTorãã°ãã¯ãªãããã¼ãã«ã³ãã¼ãããé¸æè¢ãé¸ãã§ããã°ãã¡ã¢å¸³ãããã¯ããã¥ã¡ã³ããã¡ã¤ã«ã«è²¼ãä»ãã¦ä¸ãããä»¥ä¸ã®è¯ãããã¨ã©ã¼ã¡ãã»ã¼ã¸ãè¦ã¤ããã¯ãã§ãï¼ãããããã°ã¨ã©ã¼#1:
 ãããã·æ¥ç¶å¤±æ 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:x (\\\"general SOCKS server failure\\\") \\n 
2017-10-29 09:24:08.900 [WARN] Proxy Client:

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-04-12 Thread translation

commit 4cc817bdbf99af3749a59fa5bf897e006aef6b8f
Author: Translation commit bot 
Date:   Thu Apr 12 19:37:45 2018 +

Update translations for support-connecting
---
 es.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/es.json b/es.json
index 33397ea76..13c454253 100644
--- a/es.json
+++ b/es.json
@@ -9,7 +9,7 @@
"id": "#connecting-2",
"control": "connecting-2",
"title": "Estoy teniendo problemas conectando a Tor, y no logro 
averiguar quÃ© es lo que estÃ¡ mal.",
-   "description": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "Si tienes problemas para conectarte, por favor 
selecciona la opciÃ³n \"copiar el registro Tor al portapapeles\". Luego pega el 
registro de Tor en un archivo de texto u otro documento. DeberÃas ver uno de 
estos errores de registro comunes (busca las siguientes lÃneas en tu registro 
Tor): Error de registro comÃºn #1: Fallo de conexiÃ³n del proxy 2017-10-29 
09:23:40.800[AVISO] Abriendo el localizador de Socks en 127.0.0.1:9150 
2017-10-29 09:23:47.900[NOTICE] Bootstrapped 5%: ConexiÃ³n al servidor de 
directorio 2017-10-29 09:23:47.900[NOTICE] Bootstrapped 10%: Finalizar el 
handshake con el servidor de directorio 2017-10-29 09:24:08.900[WARN] Cliente 
proxy: no se puede conectar a xx..xxx..xxx..xxx.xx:x (\"fallo general del 
servidor SOCKS\")

[tor-commits] [translation/support-connecting] Update translations for support-connecting

2018-04-12 Thread translation

commit 86bf8aae47f26de17d8435e8457531975cdff0a1
Author: Translation commit bot 
Date:   Thu Apr 12 18:19:51 2018 +

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": "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):Common log error #1: Proxy connection failure 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:x (\"general 
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable 
to connect to xx..xxx..xxx.xx:x  (\"general SOCKS server failure\") \n 
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect 
toxx..xxx..xxx.xx:x  (\"general SOCKS server fa
 ilure\")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.Common log error #2: Canât reach guard relays 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.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.Common log error #3: Failed to complete TLS handshake 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)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.Common log error #4: Clock skew 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:): 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.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. "
+   "description": "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)Â 
: Erreur habituelle de journal no 1 : Ã©chec de connexion au 
mandataire 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

39 matches

Mail list logo