tor-commits

Download

tor-commits@lists.torproject.org

April 2018

17 participants
1638 discussions

[translation-tools/master] Add support-connecting
by colin＠torproject.org 06 Apr '18

06 Apr '18

commit 97c7b51392fb7a438077da2284fd07aad5a39225 Author: Colin Childs <colin(a)torproject.org> Date: Fri Apr 6 18:37:30 2018 -0500 Add support-connecting --- config | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/config b/config index 064aa29..e143c2d 100644 --- a/config +++ b/config @@ -36,7 +36,8 @@ tor-messenger-privproperties tor-messenger-privproperties_completed tor-messenger-uiproperties tor-messenger-uiproperties_completed tails-greeter-2 tails-greeter-2_completed exoneratorproperties exoneratorproperties_completed tor-browser-manual -tor-browser-manual_completed support-censorship support-censorship_completed" +tor-browser-manual_completed support-censorship support-censorship_completed +support-connecting support-connecting_completed" PIDFILE=/srv/translation.torproject.org/run/update_translations.pid

1 0

[translation/support-connecting_completed] pulling translations from transifex
by translation＠torproject.org 06 Apr '18

06 Apr '18

commit 56a4abecace4b3c32d9e61e9436a3742a896ad33 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Apr 6 23:47:26 2018 +0000 pulling translations from transifex --- de.json | 20 ++++++++++++++++++++ es.json | 20 ++++++++++++++++++++ fr.json | 20 ++++++++++++++++++++ ga.json | 20 ++++++++++++++++++++ id.json | 20 ++++++++++++++++++++ it.json | 20 ++++++++++++++++++++ ja.json | 20 ++++++++++++++++++++ ms_MY.json | 20 ++++++++++++++++++++ nl.json | 20 ++++++++++++++++++++ pt_BR.json | 20 ++++++++++++++++++++ ro.json | 20 ++++++++++++++++++++ support-connecting.json | 20 ++++++++++++++++++++ uk.json | 20 ++++++++++++++++++++ zh_CN.json | 20 ++++++++++++++++++++ 14 files changed, 280 insertions(+) diff --git a/de.json b/de.json new file mode 100644 index 000000000..05b1a5862 --- /dev/null +++ b/de.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "Tor-Browser kann sich nicht verbinden, aber es scheint nicht an Zensur-MaÃnahmen zu liegen.", + "description": "<p class=\"mb-3\">Eines der hÃ€ufigsten Probleme, die bei Tor-Browser Verbindungsprobleme verursacht, ist eine verstellte System-Uhr. Stelle daher sicher, dass deine System-Uhr und die Zeitzone richtig eingestellt ist. Wenn dies das Problem nicht behebt, besuche die Fehlerbehebungsseite in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor-Browser-Anleitung</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Ich habe Probleme mich mit Tor zu verbinden und kann die Ursache nicht finden.", + "description": "<p class=\"mb-3\">Wenn du Verbindungsprobleme hast, wÃ€hle bitte die Option \"Tor-Protokoll in die Zwischenablage kopieren\" aus. FÃŒge dann das Tor-Protokoll in eine Textdatei oder ein anderes Dokument ein. Du solltest nun einen der folgenden verbreiteten FehlereintrÃ€ge sehen (suche nach foldenden Zeilen in deinem Tor-Protokoll):</p><h5>Ãblicher Fehlereintrag #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung zu einem SOCKS-Proxy fehlschlÃ€gt. Wenn fÃŒr deine Netzwerkkonfiguration ein SOCKS-Proxy erforderlich ist, stelle sicher, dass du die erforderlichen Proxy-Daten korrekt eingegeben hast. Wenn kein SOCKS-Proxy benÃ¶tigt wird oder du diesbezÃŒglich nicht sicher bist, versuche ohne SOCKS-Proxy eine Verbindung zum Tor-Netzwerk herzustellen.<p><h5>Ãblicher Fehlereintrag #2: Kann WÃ€chter-Weiterleitung nicht erreichen</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/20 17 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung des Tor-Clients mit dem ersten Knoten im Tor-Circuit fehlschlÃ€gt. Dies kann bedeuten, dass du dich in einem zensierten Netzwerk befindest. Versuche dich mit BrÃŒcken zu verbinden, was das Problem beheben sollte.</p><h5>Ãblicher Fehlereintrag #3: Fehlschlag bei der VervollstÃ€ndigung des TLS-Handschlags</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass dein Tor-Client einen TLS-Handschlag mit den Verzeichnisinstanzen nicht erfolgreich abschlieÃen konnte. Die Verwendung von BrÃŒcken wird das wahrscheinlich beheben.</p><h5>Ãblicher Fehlereintrag #4: Taktversatz</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and d ate settings.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass deine System-Uhr verstellt ist. Bitte stelle sicher, dass deine System-Uhr und die entsprechende Zeitzone richtig gestellt sind. Starte Tor danach neu.</p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Ich kann X.onion nicht erreichen!", + "description": "<p class=\"mb-3\">Wenn du den gewÃŒnschten Onion-Dienst nicht erreichen kannst, stelle sicher, dass du die 16 Zeichen lange Onion-Adresse richtig eingegeben hast: Sogar ein kleiner Tippfehler verhindert, dass Tor-Browser die Website finden kann. Wenn du dich dann mit dem Onion-Dienst immer noch nicht verbinden kannst, versuche es spÃ€ter noch einmal. Es kann vorÃŒbergehende Verbindungsprobleme im Netz geben oder die Seitenbetreiber haben ohne Vorwarnung die Seite vom Netz genommen.</p><p class=\"mb-3\">Du kannst auch ÃŒberprÃŒfen, ob es dir grundsÃ€tzlich mÃ¶glich ist Onion-Dienste zu nutzen, in dem du dich mit <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>s Onion-Dienst verbindest.</p>" + } +} diff --git a/es.json b/es.json new file mode 100644 index 000000000..5f8938425 --- /dev/null +++ b/es.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "El Navegador Tor no conecta, pero no parece ser un problema con la censura.", + "description": "<p class=\"mb-3\">Uno de los problemas mÃ¡s habituales que causa errores de conexiÃ³n en el Navegador Tor es un reloj del sistema incorrectamente ajustado. Por favor, asegÃºrate de que el reloj de tu sistema y tu zona horaria estÃ¡n configurados correctamente. Si esto no soluciona tu problema, dirÃgete a la pÃ¡gina de SoluciÃ³n de Problemas en el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">manual del Navegador Tor</a></mark></p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Estoy teniendo problemas conectando a Tor, y no logro averiguar quÃ© es lo que estÃ¡ mal.", + "description": "Si tienes problemas para conectarte, por favor selecciona la opciÃ³n \"copiar el registro de Tor al portapapeles\". Luego pega el registro Tor en un archivo de texto u otro documento. DeberÃas ver uno de estos errores comunes de registro (busca las siguientes lÃneas en tu registro Tor): Error comÃºn de registro #1: Fallo de conexiÃ³n proxy 2017-10-29 09:23:40.800[NOTICE] Abriendo socks en 127.0.0.1:9150\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 10%: Finaliza hankshake con el servidor de directorios\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectar toxx.. xxx.. xxx. xx: xxxxxxx (\"fallo general del servidor SOCKS\") Si ves lÃneas como estas en tu registro Tor, significa que no te estÃ¡s conectando a un proxy SOCKS. Si se requiere un proxy SOCKS para la configuraciÃ³n de red, asegÃºrate de introducir correctamente los datos del proxy. Error de registro comÃºn #2: No se puede llegar a los relÃ©s de guardia 11/1/2017 21:11:43 PM. 500[AVISO] Abriendo el socks en 127.0.0.1:9150\n11/1/2017 21:11:44 PM. 300[AVISO] Bootstrapped 80%: ConexiÃ³n a la red Tor\n11/1/2017 21:11:44 PM. 300[ADVERTENCIA] No encontramos nodo para el salto 0 de nuestro camino. Descartar este circuito.\n11/1/2017 21:11:44 PM. 500[AVISO] Bootstrapped 85%: Acabando el handshake con el primer salto\n11/1/2017 21:11:11:45 PM. 300[ADVERTENCIA] No se ha encontrado nodo para el salto 0 de nuestra ruta. Descartando este circuito: si ves lÃneas como estas en tu registro Tor, significa que tu Tor no se conectÃ³ al primer nodo del circuito Tor. Esto podrÃa significar que estÃ¡s en una red ce nsurada. Error de registro comÃºn #3: No se pudo completar el handshake TLS 13-11-17 19:52:24:24.300[ATENCIÃN) Bootstrapped 10%: Finalizar handshake con el servidor de directorios\n13-11-17 19:53:49.300[ADVERTENCIA] Problema con el bootstrapping. Atascado al 10%: Acabando handshake con el servidor de directorios. (HECHO; HECHO; conteo 10; recomendaciÃ³n; host[host] en xxx. xxx. xxx. xxx. xx: xxx)\n13-11-17 19:53:49.300[ATENCIÃN] 10 conexiones han fallado:\n13-11-17 19:53:49.300[ADVERTENCIA] 9 conexiones caidas en estado handshaking (TLS) con estado SSL SSLv2/v3 lea servidor hola A en HANDSHAKE\n13-11-17 19:53:49.300[ADVERTENCIA] 1 conexiones muertas en estado connect()ing con estado SSL (sin objeto SSL) Si ves lÃneas como esta en tu registro de Tor, significa que Tor no pudo completar un handshake TLS con las competencias del directorio. Error de registro comÃºn #4: DesviaciÃ³n del reloj 19.11.2017 00:04:47.400[ATENCIÃN] IntÃ©rprete de socks de apertura en 127.0.0.0.1:9150\n19.1 1.2017 00:04:48.000[ADVERTENCIA] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n19.11.2017 00:04:48.200[ADVERTENCIA] Bootstrapped 10%: Finalizando el handshake con el servidor de directorios\n19.11.2017 00:04:48.800[ADVERTENCIA] Celda de NETINFO recibida con tiempo sesgado (OR: xxx. xx. xx. xx: xxxx): Parece que nuestro reloj estÃ¡ atrasado 1 dÃa, 0 horas, 1 minutos, o que el suyo estÃ¡ adelantado.\nTor requiere un reloj preciso para funcionar: por favor, comprueba tus ajustes de hora, zona horaria y fecha Si ves lÃneas como esta en tu registro Tor, significa que el reloj de tu sistema es incorrecto. AsegÃºrate de que tu reloj estÃ¡ ajustado correctamente, incluyendo la zona horaria. A continuaciÃ³n, reinicia Tor." + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Â¡No puedo conectar a X.onion!", + "description": "<p class=\"mb-3\">Si no puede alcanzar el servicio onion que desea, asegÃºrese de que ha introducido correctamente la direcciÃ³n onion de 16 caracteres: incluso un pequeÃ±o error evitarÃ¡ que el Navegador Tor logre alcanzar el sitio. Si aÃºn asÃ no puede conectar al servicio onion, por favor, intÃ©ntelo de nuevo mÃ¡s tarde. Puede haber un problema temporal con la conexiÃ³n, o los operadores del sitio pueden haberle permitido desconectar sin avisar.</p><p class=\"mb-3\">TambiÃ©n puede asegurarse de que es capaz de acceder a otros servicios onion conectando al servicio onion de <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/fr.json b/fr.json new file mode 100644 index 000000000..4ed10c84e --- /dev/null +++ b/fr.json @@ -0,0 +1,20 @@ +{ + "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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">âguide du navigateur Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connexion-2", + "control": "connexion-2", + "title": "JâÃ©prouve des difficultÃ©s Ã me connecter Ã Tor et je nâarrive pas Ã comprendre ce qui ne va pas.", + "description": "<p class=\"mb-3\">Si vous Ã©prouvez des difficultÃ©s Ã vous connecter, veuillez sÃ©lectionner lâoption Â«Â Copier le journal de Tor dans le presse-papiersÂ Â». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver lâune de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor)Â : </p><h5>Erreur habituelle de journal noÂ 1 : Ã©chec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter Ã un mandataire SOCKS. Si un mandataire SOCKS est nÃ©cessaire Ã la configuration de rÃ©seau, veuillez alors vous assurer dâavoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS nâest pas nÃ©cessaire ou si vous ne savez pas, veuillez tenter de vous connecter au rÃ©seau Tor sans mandataire SOCKS.<p><h5>Erreur habituelle de journal noÂ 2 : impossible dâatteindre les relais gardes</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/ 2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter au premier nÅud du circuit Tor. Cela pourrait signifier que vous Ãªtes sur un rÃ©seau qui est censurÃ©. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5>Erreur habituelle de journal noÂ 3 : Ã©chec dâÃ©tablissement dâune liaison TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19 :53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas rÃ©ussi Ã Ã©tablir une liaison TLS avec les autoritÃ©s d'annuaire. Lâutilisation de ponts corrigera certainement cette situation.</p><h5>Erreur habituelle de journal noÂ 4 : dÃ©calage dâhorloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or t hat theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">\nSi vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge systÃšme nâest pas juste. Veuillez vous assurer que votre horloge est rÃ©glÃ©e avec prÃ©cision, fuseau horaire inclus, puis redÃ©marrez Tor. </p>" + }, + "connecting-3": { + "id": "#connexion-3", + "control": "connexion-3", + "title": "Je ne peux pas accÃ©der Ã X.onionâ!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">Vous pouvez aussi vous assurer que vous arrivez Ã accÃ©der Ã dâautres services oignon en vous connectant au service oignon de <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>\n\n" + } +} diff --git a/ga.json b/ga.json new file mode 100644 index 000000000..26d45c2d5 --- /dev/null +++ b/ga.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "NÃ fÃ©idir le BrabhsÃ¡laÃ Tor ceangal a bhunÃº, cÃ© nach mbaineann an fhadhb le cÃºrsaÃ cinsireachta.", + "description": "<p class=\"mb-3\">Is minic go mbÃonn fadhb le clog an chÃ³rais ina chÃºis le hearrÃ¡idÃ i mBrabhsÃ¡laÃ Tor. Ba chÃ³ir duit deimhniÃº go bhfuil clog an chÃ³rais agus an crios ama socraithe mar is ceart. Mura rÃ©itÃonn seo an fhadhb, fÃ©ach an leathanach FabhtcheartÃº i <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">LÃ¡mhleabhar BhrabhsÃ¡laÃ Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "NÃ fÃ©idir liom ceangal le lÃonra Tor, agus nÃ thuigim cad Ã© an fhadhb.", + "description": "<p class=\"mb-3\">MÃ¡ tÃ¡ fadhb agat ag ceangal le lÃonra Tor, ÃºsÃ¡id an rogha âcÃ³ipeÃ¡il logchomhad Tor go dtÃ an ghearrthaisce.â Ansin, greamaigh an logchomhad i dtÃ©acschomhad nÃ³ cÃ¡ipÃ©is eile. Is dÃ³cha go bhfeicfidh tÃº ceann de na hearrÃ¡idÃ coitianta seo (cuardaigh na lÃnte seo a leanas sa logchomhad):</p><h5>EarrÃ¡id choitianta #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to co nnect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn siad gur theip ort ceangal a bhunÃº le seachfhreastalaÃ SOCKS. MÃ¡ theastaÃonn seachfhreastalaÃ SOCKS uait ar do lÃonra, deimhnigh gur chuir tÃº mionsonraÃ an fhreastalaÃ isteach go ceart. Mura dteastaÃonn seachfhreastalaÃ SOCKS uair, nÃ³ mura bhfuil tÃº cinnte, dÃ©an iarracht ceangal a bhunÃº le lÃonra Tor gan seachfhreastalaÃ SOCKS.<p><h5>EarrÃ¡id choitianta #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] F ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ort ceangal a bhunÃº leis an chÃ©ad nÃ³d sa gciorcad Tor. Uaireanta, ciallaÃonn seo go bhfuil do lÃonra faoi chinsireacht. Bain triail as ceangal trÃ dhroichead; is dÃ³cha go rÃ©iteoidh sin an fhadhb.</p><h5>EarrÃ¡id choitianta #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 co nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ar Tor croitheadh lÃ¡imhe TLS leis na hÃºdarÃ¡is a chur i gcrÃch. Is dÃ³cha go rÃ©iteoidh droichead an fhadhb seo.</p><h5>EarrÃ¡id choitianta #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, c iallaÃonn sÃ© go bhfuil an clog i do rÃomhaire mÃcheart. Ba chÃ³ir duit socruithe an chloig a dheimhniÃº, an t-am, dÃ¡ta, agus crios ama san Ã¡ireamh. Ansin, atosaigh Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "NÃlim in ann teacht ar X.onion!", + "description": "<p class=\"mb-3\">Mura bhfuil tÃº in ann seirbhÃs .onion a shroicheadh, deimhnigh gur chuir tÃº an seoladh 16-carachtar isteach go ceart: mÃ¡ tÃ¡ aon bhotÃºn ann, fiÃº botÃºn an-bheag, nÃ bheidh BrabhsÃ¡laÃ Tor in ann an suÃomh a shroicheadh. MÃ¡ tÃ¡ tÃº cinnte gur chuir tÃº an seoladh ceart isteach, bain triail eile as ar ball. Seans go bhfuil fadhb shealadach leis an lÃonra, nÃ³ b'fhÃ©idir gur bhain riarthÃ³irÃ an tsuÃmh as lÃne Ã© gan rabhadh.</p><p class=\"mb-3\">B'fhiÃº freisin fÃ©achaint an fÃ©idir leat dul i dteagmhÃ¡il le seirbhÃsÃ .onion eile, mar shampla <a href=\"http://3g2upl4pq6kufc4m.onion\">seirbhÃs DuckDuckGo</a>.</p>" + } +} diff --git a/id.json b/id.json new file mode 100644 index 000000000..0fdc118e3 --- /dev/null +++ b/id.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "Tor Browser tidak dapat tersambung, tapi ini tampaknya bukan akibat sensor oleh pihak lain.", + "description": "<p class=\"mb-3\">Salah satu masalah umum yang menyebabkan kegagalan koneksi di Tor Browser adalah jam sistem operasi yang tidak tepat. Silakan pastikan jam di sistem operasi dan zona waktu diatur dengan tepat di komputer Anda. Jika ini tidak memperbaiki masalah koneksi, lihat halaman Troubleshooting di <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", + "description": "<p class=\"mb-3\"> Jika Anda mendapat masalah dalam terhubung ke jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):\n\n</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS se rver failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.\n\n<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> Jika Anda melihat baris seperti ini, Tor gagal tersambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.\n\n</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.<h5>\n\nCommon log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. Tor memerlukan jam yang akurat supaya berfungsi dengan baik. Silakan periksa pengaturan waktu, zona waktu, dan tanggal. Pastikan jam di komputer Anda diatur dengan benar, termasuk zona waktu yang tepat. Lalu, restart Tor.\n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Tidak dapat terhubung ke X.onion!", + "description": "<p class=\"mb-3\">Jika Anda tidak dapat terhubung ke sebuah onion service yang diinginkan, pastikan Anda telah dengan tepat memasukkan 16-karakter alamat onion-nya. Bahkan kesalahan sedikit akan membuat Tor Browser tidak dapat terhubung ke situs yang dimaksud. Jika Anda tetap tidak dapat terhubung, silakan coba lagi nanti. Mungkin ada masalah sedikit di situsnya, atau operator situsnya sedang membuat situsnya menjadi offline tanpa pemberitahuan. </p><p class=\"mb-3\">Anda juga dapat memastikan jika Anda juga dapat terhubung ke situs onion service lain dengan mencoba terhubung ke <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>." + } +} diff --git a/it.json b/it.json new file mode 100644 index 000000000..7a04f1284 --- /dev/null +++ b/it.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connessione-1", + "control": "connessione-1", + "title": "Tor Browser non si connette, ma non sembra che sia dovuto alla censura.", + "description": "<p class=\"mb-3\">Uno dei problemi piÃ¹ comuni che causano errori di connessione in Tor Browser Ãš un orologio di sistema errato. Assicurati che l'orologio di sistema e il fuso orario siano impostati correttamente. Se ciÃ² non risolve il problema, consultare la pagina Risoluzione dei problemi su <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manuale di Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connessione-2", + "control": "connessione-2", + "title": "Sto avendo problemi nella connessione a Tor e non riesco a capire quale sia la causa.", + "description": "<p class=\"mb-3\">Se stai avendo problemi a connetterti, per favore seleziona l'opzione \"copia i log di Tor sulla clipboard.\" Poi incolla il log di Tor su un file di testo o un altro tipo di documento. Dovresti vedere uno di questi errori di log comuni (cerca per le seguenti linee nei log di Tor):</p><h5>Errore di log comune #1: Errore di connessione Proxy </h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150\n2017-10-29 09:23:47.900 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n2017-10-29 09:23:47.900 [AVVISO] Progressione 10%: Completando l'handshake con l'elenco dei server\n2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\nÂ 2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\n2017-10-29 09:24:08.900 [ATTENZIONE] Prox y Client: impossibile connettersi a xx..xxx..xxx.xx:xxxxx (\"errore generale server SOCKS\")</code></pre></p><p class=\"mb-3\">Se vedi delle linee come queste nei log di Tor, significa che la connessione a un proxy SOCKS sta fallendo.Se un proxy SOCKS Ãš richiesto per la tua configurazione di rete, controlla di aver inserito i dettagli del proxy correttamente.Se un proxy SOCKS non Ãš richiesto, o non ne sei sicuro, prova a connetterti alla rete Tor senza un proxy SOCKS.<p><h5>Errore di log comune #2: Non Ãš possibile raggiungere i guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150 \n11/1/2017 21:11:44 PM.300 [AVVISO] Progressione 80%: Connessione alla rete Tor\n11/1/2017 21:11:44 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.\n11/1/2017 21:11:44 PM.500 [AVVISO] Progressione 85%: Terminando l'handshake con il primo hop\nÂ 11/1/2017 21:11:45 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.</code></pre></p><p class=\"mb-3\">Se vedi delle linee come questo nel tuo log di Tor, significa che Tor ha fallito la connesione al primo nodo del circuito Tor. Questo potrebbe significare che ti trovi su una rete censurata. Per favore prova a connetterti con i bridge, e questo dovrebbe risolvere il problema.</p><h5>Errore di log comune #3: Errore nel completare l'handshake TLS</h5><p class=\"mb-3\"><pre><code>13-11-17 19:52:24.300 [AVVISO] Progressione 10%: Handshake con l'elenco dei server completato\n13-11-17 19:53:49.300 [ATTENZIONE] Problema durante la progressione. Fermo al 10%: Completando l'handshake con l'elenco dei server (FATTO; FATTO; contatore 10; avviso di raccomandazione; host [host] a xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [ATTENZIONE] 10 connessioni hanno fallito:\n13-11-17 19:53:49.300 [ATTENZIONE] 9 connessioni sono scadute durante lo stato di handshaking (TLS) con lo stato SSL di SSLv2/v3 r isposta server hello A in HANDSHAKE \n13-11-17 19:53:49.300 [ATTENZIONE] 1 connessione Ãš scaduta nello stato di connessione con stato SSL (Nessun oggetto SSL)</code></pre></p><p class=\"mb-3\">Se vedi delle linee cosÃ¬ nel tuo log Tor, significa che Tor ha fallito il completamento dell'handshake TLS con le autoritÃ dell'elenco. Usare i bridge risolverÃ probabilmente il problema.</p><h5>Errore log comune #4: Distorsione orario</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [AVVISO] Apertura ascoltatore porte SOCKS su 127.0.0.1:9150\n19.11.2017 00:04:48.000 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n19.11.2017 00:04:48.200 [AVVISO] Progressione 10%: Terminando l'handshake con l'elenco dei server\n19.11.2017 00:04:48.800 [ATTENZONE] Ricevuta cella NETINFO con orario distorto (O:xxx.xx.x.xx:xxxx): Sembra che il tuo orologio sia indietro di 1 giorno, 0 ore, 1 minuto, o che il loro sia avanti.\nTor richiede un orologio accurato per funzionare: per favore con trolla l'ora, la tua zona temporale e le impostazioni sulla data.</code></pre></p><p class=\"mb-3\">Se vedi queste linee nel tuo log di Tor, significa che l'ora del sistema Ãš incorretta. Per favore controlla che il tuo orologio sia impostato accuratamente, inclusa la zona temporale. DopodichÃ© riavvia Tor.</p>" + }, + "connecting-3": { + "id": "#connessione-3", + "control": "connessione-3", + "title": "Non posso raggiungere X.onion!", + "description": "<p class=\"mb-3\">Se non riesci a raggiungere il sito che desideri, assicurati di aver inserito correttamente l'indirizzo a 16 caratteri: anche un piccolo errore puÃ² impedire al Tor Browser di raggiungere il sito. Se non riesci ancora a connetterti al sito, riprova piÃ¹ tardi. Potrebbe esserci un problema di connessione temporaneo, oppure gli operatori del sito lo hanno lasciato andare offline senza lasciare preavviso.</p><p class=\"mb-3\">Puoi anche provare a connetterti a <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a> per vedere se riesci ad accedere ad altri siti.</p>" + } +} diff --git a/ja.json b/ja.json new file mode 100644 index 000000000..24309f341 --- /dev/null +++ b/ja.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#æ¥ç¶-1", + "control": "æ¥ç¶-1", + "title": "Torãã©ãŠã¶ãŒã¯æ¥ç¶ããŸããããæ€é²ã®åé¡ã§ã¯ãªãããã§ãã", + "description": "Torãã©ãŠã¶ãŒã§æ¥ç¶ãšã©ãŒãçºçããæãäžè¬çãªåé¡ã®1ã€ã¯ãäžæ£ãªã·ã¹ãã ã¯ããã¯ã§ããã·ã¹ãã ã®æèšãšã¿ã€ã ãŸãŒã³ãæ£ç¢ºã«èšå®ãããŠããããšãç¢ºèªããŠãã ãããããã§åé¡ãè§£æ±ºããªãå Žåã¯ãTorãã©ãŠã¶ãŒã®ããã¥ã¢ã«ã®ãã©ãã«ã·ã¥ãŒãã£ã³ã°ã®ããŒãžãåç§ããŠãã ããã" + }, + "connecting-2": { + "id": "#æ¥ç¶-2", + "control": "æ¥ç¶-2", + "title": "Torã«ã¢ã¯ã»ã¹ã§ããªãããäœãåé¡ãªã®ãåãããŸããã", + "description": "<p class=\"mb-3\">Torã«ã¢ã¯ã»ã¹ã§ããªãå ŽåããTorãã°ãã¯ãªããããŒãã«ã³ããŒãããéžæè¢ãéžãã§ããã°ãã¡ã¢åž³ãããã¯ããã¥ã¡ã³ããã¡ã€ã«ã«è²Œãä»ããŠäžãããä»¥äžã®è¯ããããšã©ãŒã¡ãã»ãŒãžãèŠã€ããã¯ãã§ãïŒ</p><h5>ãããããã°ãšã©ãŒ#1: ãããã·æ¥ç¶å€±æ</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx.. xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãSOCKSãããã·ãšç¹ãããªããšããããšã§ãããããã¯ãŒã¯ã«ã¯SOCKSãããã·ãå¿èŠãªããèšå®ãç¢ºèªããŠäžãããSOCKSãããã·ãå¿èŠã§ã¯ãªãå Žåããããã¯ããåãããªãå ŽåãSOCKSãããã·ç¡ãã§Torã«ã¢ã¯ã»ã¹ããŠã¿ãŠäžããã<p><h5>ãããããã°ãšã©ãŒ#2: ã¬ãŒããªã¬ãŒãšæ¥ç¶ã§ããªã</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discardi ng this circuit.</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorã¯circuitã®æåã®ããŒããšæ¥ç¶ã§ããªãã£ããšããããšã§ããæ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ããããŸããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããã¯ãã§ãã</p><h5>ãããããã°ãšã©ãŒ#3: TLSãã³ãã·ã§ã€ã¯ã®å€±æ</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorããã£ã¬ã¯ããªãªãŒãœãªãã£ãšTLSãã³ãã·ã§ã€ã¯ãå®äºã§ããªãã£ããšããããšã§ããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããå¯èœæ§ãããã</p><h5>ãããããã°ãšã©ãŒ#4: ã¯ããã¯ã¹ãã¥ãŒ</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p clas s=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãã·ã¹ãã ã»ã¯ããã¯ã«ã¯ééã£ãæå»ãèšå®ãããŸããã·ã¹ãã ã»ã¯ããã¯ãæ£ããæå»ãšã¿ã€ã ãŸãŒã³ã«åãããŠããTorãåèµ·åããŠäžããã </p>" + }, + "connecting-3": { + "id": "#æ¥ç¶-3", + "control": "æ¥ç¶-3", + "title": "X.onionãååŸã§ããŸããïŒ", + "description": "ããªããæããªããªã³ã®ãµãŒãã¹ã«ã¢ã¯ã»ã¹ã§ããªãå Žåã¯ã16æåã®ãªããªã³ã¢ãã¬ã¹ãæ£ããå¥åããããšãç¢ºèªããŠãã ãããå°ããªééãã§ããTorãã©ãŠã¶ãŒããµã€ãã«ã¢ã¯ã»ã¹ã§ããªããªããŸãã" + } +} diff --git a/ms_MY.json b/ms_MY.json new file mode 100644 index 000000000..94afcb73e --- /dev/null +++ b/ms_MY.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#menyambung-1", + "control": "menyambung-1", + "title": "Pelayar Tor tidak dapat bersambung, tetapi ia bukanlah isu berkenaan penapisan.", + "description": "<p class=\"mb-3\">Salah satu masalah utama yang menyebabkan ralat sambungan dalam Pelayar Tor ialah jam sistem yang salah. Sila pastikan jam sistem dan zon waktu anda telah ditetapkan dengan betul. Jika masalah ini masih berlaku, sila rujuk laman Pencarisilapan di dalam <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âpanduan Pelayar Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#menyambung-2", + "control": "menyambung-2", + "title": "Saya menghadapi masalah ketika menyambung dengan Tor, dan saya tidak tahu apa masalah yang berlaku.", + "description": "<p class=\"mb-3\">Jika anda menghadapi masalah sambungan, pilih pilihan \"salin log Tor ke papan keratan.â Kemudian tampal log Tor ke dalam fail teks atau lain-lain fail dokumen. Anda akan dapati terdapat ralat log (lihat baris berikut di dalam log Tor anda):</p><h5>Ralat log umum #1: Kegagalan sambungan proksi</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\" )</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud anda gagal menyambung dengan proksi SOCKS. Jika proksi SOCKS diperlukan untuk persediaan rangkaian anda, maka sila pastikan anda telah memasukkan perincian proksi tersebut dengan betul. Jika proksi SOCKS tidak diperlukan, atau anda tidak pasti, cuba sambung ke rangkaian Tor tanpa proksi SOCKS.<p><h5>Ralat log umum #2: Tidak dapat capai geganti pengawal</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb- 3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud Tor anda gagal menyambung ke nod pertama dalam litar Tor. Ia bermaksud anda berada dalam rangkaian bertapis. Cuba menyambung dengan titi, dan sepatutnya ia masalah selesai.</p><h5>Ralat log umum #3: Gagal menyelesaikan jabat-tangan TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat ba ris seperti ini di dalam log Tor anda, ia bermaksud Tor gagal menyelesaikan jabat-tangan TLS dengan autoriti direktori. Penggunaan titi dapat menyelesaikan masalah ini.</p><h5>Ralat log umum #4: Pencong jam</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini dalam log Tor anda, ia bermaksud jam sistem anda salah. Sila pastikan jam anda telah ditetapkan dengan tepat, termasuklah zon waktu yang betul. Kemudian mulakan semula Tor. </p>" + }, + "connecting-3": { + "id": "#menyambung-3", + "control": "menyambung-3", + "title": "Saya tidak dapat mencapai X.onion!", + "description": "<p class=\"mb-3\">Jika anda masih tidak dapat mencapai servis onion yang dikehendaki, pastikan anda telah memasukkan alamat onion 16-aksara dengan betul: walaupun dengan kesilapan kecil akan menghentikan Pelayar Tor mencapai laman. Jika anda masih tidak dapat menyambung ke servis onion, cuba sekali lagi. Kadangkala ia merupakan masalah sambungan sementara, atau operator laman telah menjadi luar talian tanpa apa-apa amaran.</p><p class=\"mb-3\">Anda juga perlu pastikan dapat mencapai servis onion lain dengan menyambung ke Servis Onion <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/nl.json b/nl.json new file mode 100644 index 000000000..4fdd4e365 --- /dev/null +++ b/nl.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#verbinden-1", + "control": "verbinden-1", + "title": "Tor Browser maakt geen verbinding, maar het lijkt geen probleem te zijn met censuur.", + "description": "<p class=\"mb-3\">Een van de meest voorkomende problemen die verbindingsfouten in Tor Browser veroorzaken, is een onjuiste systeemklok. Zorg ervoor dat uw systeemklok en tijdzone nauwkeurig zijn ingesteld. Als dit het probleem niet oplost, zie de pagina Problemen oplossen op de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser manual</a></mark>.</p>" + }, + "connecting-2": { + "id": "#verbinden-2", + "control": "verbinden-2", + "title": "Ik ondervind problemen bij het verbinding maken met Tor, en ik vind maar niet wat er fout gaat.", + "description": "<p class=\"mb-3\">Als u problemen ondervindt bij het verbinden, selecteert u de optie om \"Tor log naar klembord te kopiÃ«ren\". Plak vervolgens het Tor-log in een tekstbestand of een ander document. U zou een van deze Vaak voorkomend logfouten moeten zien (kijk naar de volgende regels in uw Tor-logboek): </p><h5>Vaak voorkomend logboekfout # 1: Proxy-verbindingsfout</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09: 23: 40.800 [LET OP] Opening Socks luisteraar op 127.0.0.1 : 9150 \n 2017-10-29 09: 23: 47.900 [LET OP] Bootstrapped 5%: verbinden met directoryserver \n 2017-10-29 09: 23: 47.900 [LETICE] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-clie nt: kan toxx..xxx..xxx.xx: xxxxx niet verbinden (\"algemene SOCKS-serverstoring\") </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, is dit betekent dat u geen verbinding kunt maken met een SOCKS-proxy. Als een SOCKS-proxy vereist is voor uw netwerkconfiguratie, moet u ervoor zorgen dat u uw proxy-gegevens correct hebt ingevoerd. Als een SOCKS-proxy niet vereist is, of als u het niet zeker weet, probeer dan verbinding te maken met het Tor-netwerk zonder een SOCKS-proxy.<p><h5>Gebruikslog fout # 2: Kan relais niet bereiken</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM .500 [LET OP] Luisteraar luisterpositie openen op 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [LET OP] Bootstrapped 80%: Verbinding maken met het Tor-netwerk \n 11/1/2017 21:11:44 PM.300 [WARN] Kan knooppunt voor hop 0 van ons pad niet vinden. Dit circuit weggooien. \n 11/1/2017 21:11:44 PM.500 [LET OP] Bootstrap 85%: Handshake beÃ«indigen met eerste hop \n 11/1/2017 21:11:45 P M.300 [WARN] Kan knooppunt niet vinden voor hop 0 van ons pad. Dit circuit verwijderen.</code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dit dat uw Tor geen verbinding kon maken met het eerste knooppunt in het Tor-circuit. Dit kan betekenen dat u zich op een netwerk bevindt dat gecensureerd is. Probeer te verbinden met bruggen, en dat zou het probleem moeten verhelpen.</p><h5> Algemene logfout # 3: Kan TLS-handshake niet voltooien</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 13-11-17 19: 53: 49.300 [WARN] Probleem met bootstrappen. Vastgelopen met 10%: handshake beÃ«indigen met directoryserver. (GEDAAN, GEDAAN, aantal 10; advieswaarschuwing; host [host] op xxx.xxx.xxx.xx: xxx) \n 13-11-17 19: 53: 49.300 [WARN] 10 verbindingen zijn mislukt: \n 13-11-17 19: 53: 49.300 [WARN] 9 verbindingen stierven in staatshandshaking (TLS) met SSL-status SSLv2 / v3 lezen server hallo A in HANDSHAKE \n 13-11-17 19: 53: 49.300 [WARN] 1 verbindingen zijn overleden in state connect () ing met SSL-staat (No SSL-object) </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dat Tor een TLS-handshake niet kon voltooien met de directory-autoriteiten. Het gebruik van bruggen lost dit waarschijnlijk op.</p><h5>Veel logboekfout # 4: Klok skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00: 04: 47.400 [LET OP] Opening Socks luisteraar op 127.0.0.1:9150 \n 19.11.2017 00: 04: 48.000 [LET OP] Bootstrap 5%: verbinding maken met directoryserver \n 19.11.2017 00: 04: 48.200 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 19.11.2017 00: 04: 48.800 [WARN] NETINFO-cel ontvangen met scheve tijd (OF: xxx.xx.x.xx: xxxx): het lijkt erop dat onze klok 1 dag, 0 uur, 1 minuut achterloopt, of die van hen liggen voor de deur. \n Tor vereist een nauwkeurige klok om te werken: controleer uw tijd-, tijdzone- en datuminstellin gen.</code></pre></p><p class=\"mb-3\">Als u lijnen zoals deze in uw Tor-logboek ziet, betekent dit dat uw systeemklok onjuist is. Zorg ervoor dat uw klok correct is ingesteld, inclusief de juiste tijdzone. Start dan Tor opnieuw. </p>" + }, + "connecting-3": { + "id": "#verbinden-3", + "control": "verbinden-3", + "title": "Ik kan X.onion niet bereiken!", + "description": "<p class=\"mb-3\">Als u de gewenste onion service niet kunt bereiken, moet u ervoor zorgen dat u het onion adres van 16 tekens correct hebt ingevoerd: zelfs een kleine fout zal ervoor zorgen dat Tor Browser de site niet kan bereiken. Als u nog steeds geen verbinding kunt maken met de onion service, probeert u het later opnieuw. Er kan een tijdelijke verbinding probleem zijn, of de site exploitanten kunnen hebben toegestaan dat het offline gaan zonder waarschuwing.</p><p class=\"mb-3\"> U kunt er ook voor zorgen dat u in staat om toegang te krijgen tot andere diensten ui door verbinding te maken <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s Onion Service.</p>" + } +} diff --git a/pt_BR.json b/pt_BR.json new file mode 100644 index 000000000..a1bf886e7 --- /dev/null +++ b/pt_BR.json @@ -0,0 +1,20 @@ +{ + "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.", + "description": "<p class=\"mb-3\">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</a></mark>.</p>" + }, + "connecting-2": { + "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": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opÃ§Ã£o para \"copiar o log de Tor para a Ã¡rea de transferÃªncias\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. VocÃª deverÃ¡ ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexÃ£o de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretÃ³rio\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretÃ³rio\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0 8.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se vocÃª encontrar linhas como estas em seu log do Tor, isto significa que falhou em conectar-se Ã um SOCKS proxy. Se um SOCKS proxy Ã© obrigatÃ³rio para a sua configuraÃ§Ã£o de rede, por favor certifique-se que vocÃª digitou seus detalhes de proxy corretamente. Se um SOCKS proxy nÃ£o Ã© obrigatÃ³rio, ou vocÃª nÃ£o estÃ¡ certo sobre isso, por favor tente conectar-se Ã rede Tor sem um 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\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.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\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hand shake 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\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor 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": "#conectando-3", + "control": "conectando-3", + "title": "NÃ£o consigo conectar ao X.onion!", + "description": "<p class=\"mb-3\">Se vocÃª nÃ£o conseguir acessar o serviÃ§o onion desejado, certifique-se de ter digitado o endereÃ§o onion com 16 caracteres corretamente: atÃ© mesmo um pequeno erro impedirÃ¡ que o Navegador Tor alcance o site. Se vocÃª ainda nÃ£o conseguir se conectar ao serviÃ§o onion, tente novamente mais tarde. Pode haver um problema de conexÃ£o temporÃ¡ria ou os operadores do site podem ter permitido que ele fique offline sem aviso prÃ©vio.</p><p class=\"mb-3\"> VocÃª tambÃ©m pode garantir que poderÃ¡ acessar outros serviÃ§os onion conectando-se ao <a href=\"http://3g2upl4pq6kufc4m.onion\">ServiÃ§o Onion</a>do DuckDuckGo.</p>" + } +} diff --git a/ro.json b/ro.json new file mode 100644 index 000000000..2fe13067e --- /dev/null +++ b/ro.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "conectare-1", + "title": "Tor Browser nu se conecteazÄ, dar nu pare a fi o problemÄ de cenzurÄ.", + "description": "<p class=\"mb-3\">Una din cele mai frecvente cauze pentru problemele de conectare ale Tor Browser este ora sistemului incorectÄ. VerificÄ dacÄ ora Èi fusul orar sunt setate corect. DacÄ aceasta nu rezolvÄ problema, urmeazÄ indicaÈiile de Depanare din <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âmanualul Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "conectare-2", + "title": "Am dificultÄÈi Ã®n conectarea la Tor Èi nu Ã®nÈeleg ce e greÈit.", + "description": "<p class=\"mb-3\">DacÄ ai probleme de conectare, selecteazÄ opÈiunea \"copiazÄ log-ul Tor Ã®n clipboard\". Apoi lipeÈte log-ul astfel copiat Ã®ntr-un fiÈier text sau alt document. Ar trebui sÄ vezi unul dintre aceste mesaje de eroare comune (cautÄ astfel de linii Ã®n log-ul Tor):</p><h5>Eroare comunÄ #1: Eroare de conectare la proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-ul Tor, Ã®nseamnÄ cÄ nu te poÈi conecta la un proxy SOCKS. DacÄ un proxy SOCKS este necesar pentru reÈeaua pe care o foloseÈti, atunci asigurÄ-te cÄ ai introdus setÄrile de proxy corecte. DacÄ un proxy SOCKS nu e necesar sau nu eÈti sigur, Ã®ncearcÄ sÄ te conectezi la reÈeaua Tor fÄrÄ un proxy SOCKS.<p><h5>Eroare comunÄ #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\" >DacÄ vezi astfel de linii in log-ul Tor Ã®nseamnÄ ca nu s-a reuÈit conectarea la primul nod din circuitul Tor. Aceasta ar putea Ã®nsemna cÄ te afli Ã®ntr-o reÈea cenzuratÄ. ÃncearcÄ conectarea prin punÈi, care ar trebui sÄ rezolve problema.</p><h5>Eroare comunÄ #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-u l Tor Ã®nseamnÄ cÄ nu s-a realizat o conexiune completÄ TLS cu serverele de directoare. Folosirea punÈilor va rezolva probabil acest lucru. </p><h5>Eroare comunÄ #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-ul Tor Ã®nseamnÄ cÄ ceasul sistemului tÄu e incorect. AsigurÄ-te cÄ ceasul sistemului este corect, inclusiv fusul orar, apoi reporneÈte Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "conectare-3", + "title": "Nu pot ajunge la X.onion!", + "description": "<p class=\"mb-3\">DacÄ nu poÈi ajunge la serviciul onion dorit, asigurÄ-te cÄ ai introdus cele 16 caractere din adresa onion corect - chiar Èi cea mai micÄ eroare va Ã®mpiedica Tor Browser sÄ ajungÄ la site. DacÄ tot nu poÈi ajunge la serviciul onion, Ã®ncearcÄ mai tÃ¢rziu. E posibil sÄ fie o problemÄ temporarÄ de conexiune sau operatorii site-ului l-au deconectat fÄrÄ avertizare. </p><p class=\"mb-3\">PoÈi sÄ te asiguri cÄ alte servicii onion sunt accesibile conectÃ¢ndu-te la serviciul onion al <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/support-connecting.json b/support-connecting.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/support-connecting.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/uk.json b/uk.json new file mode 100644 index 000000000..32a35f4fc --- /dev/null +++ b/uk.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-1", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-1", + "title": "ÐÑÐ°ÑÐ·ÐµÑ Tor ÐœÐµ Ð±ÑÐŽÐµ Ð¿ÑÐŽ'ÑÐŽÐœÑÐ²Ð°ÑÐžÑÑ, Ð°Ð»Ðµ ÑÐµ, Ð·ÐŽÐ°ÑÑÑÑÑ, ÐœÐµ Ñ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐŸÑ Ð· ÑÐµÐœÐ·ÑÑÐŸÑ.", + "description": "<p class=\"mb-3\">ÐÐŽÐœÑÑÑ Ð· ÐœÐ°Ð¹Ð±ÑÐ»ÑÑ Ð¿ÐŸÑÐžÑÐµÐœÐžÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ, ÑÐŸ Ð¿ÑÐžÐ·Ð²ÐŸÐŽÑÑÑ ÐŽÐŸ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ñ Ð±ÑÐ°ÑÐ·ÐµÑÑ Tor, Ñ ÐœÐµÐ¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐ¹ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº. ÐÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÑ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÑÐ° ÑÐ°ÑÐŸÐ²ÐžÐ¹ Ð¿ÐŸÑÑ Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÑÐŸÑÐœÐŸ. Ð¯ÐºÑÐŸ ÑÐµ ÐœÐµ Ð²ÐžÑÑÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ, Ð¿ÐµÑÐµÐ³Ð»ÑÐœÑÑÐµ ÑÑÐŸÑÑÐœÐºÑ ÑÑÑÐœÐµÐœÐœÑ ÐœÐµÐ¿ÐŸÐ»Ð°ÐŽÐŸÐº Ñ <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Ð¿ÐŸÑÑÐ±ÐœÐžÐºÑ ÐºÐŸÑÐžÑÑÑÐ²Ð°ÑÐ° Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-2", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-2", + "title": "Ð£ ÐŒÐµÐœÐµ Ð²ÐžÐœÐžÐºÐ»Ð° Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ ÐŽÐŸ Tor, Ñ Ñ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÑÐŸÐ·ÑÐŒÑÑÐž, ÑÐŸ ÐœÐµ ÑÐ°Ðº.", + "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð²Ð°Ñ Ð²ÐžÐœÐžÐºÐ»Ðž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐž Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ, Ð²ÐžÐ±ÐµÑÑÑÑ ÐŸÐ¿ÑÑÑ Â«ÐºÐŸÐ¿ÑÑÐ²Ð°ÑÐž Ð¶ÑÑÐœÐ°Ð» Tor Ñ Ð±ÑÑÐµÑ ÐŸÐ±ÐŒÑÐœÑÂ». ÐÐŸÑÑÐŒ Ð²ÑÑÐ°Ð²ÑÐµ Ð¶ÑÑÐœÐ°Ð» Tor Ñ ÑÐµÐºÑÑÐŸÐ²ÐžÐ¹ ÑÐ°Ð¹Ð» Ð°Ð±ÐŸ ÑÐœÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. ÐÐž ÐŒÐ°ÑÑÐµ Ð¿ÐŸÐ±Ð°ÑÐžÑÐž ÐŸÐŽÐœÑ Ð· ÑÐžÑ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ (ÑÑÐºÐ°Ð¹ÑÐµ ÐœÐ°ÑÑÑÐ¿ÐœÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor):</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â1: ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ð· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐŸÐŒ</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p> <p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS. Ð¯ÐºÑÐŸ ÐŽÐ»Ñ ÐœÐ°Ð»Ð°ÑÑÑÐ²Ð°ÐœÐœÑ ÐŒÐµÑÐµÐ¶Ñ Ð¿ÐŸÑÑÑÐ±ÐµÐœ Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑ SOCKS, Ð±ÑÐŽÑ Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž ÑÐœÑÐŸÑÐŒÐ°ÑÑÑ Ð¿ÑÐŸ Ð¿ÑÐŸÐºÑÑ. Ð¯ÐºÑÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS ÐœÐµ Ð¿ÐŸÑÑÑÐ±ÐœÐžÐ¹, Ð°Ð±ÐŸ Ð²Ðž ÐœÐµ Ð²Ð¿ÐµÐ²ÐœÐµÐœÑ, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÐŒÐµÑÐµÐ¶Ñ Tor Ð±ÐµÐ· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐ° SOCKS.<p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â2: ÐÐµ Ð²ÐŽÐ°ÑÑÑÑÑ Ð ŽÑÑÑÐ°ÑÐžÑÑ Ð±ÐµÐ·Ð¿ÐµÑÐœÐžÑ Ð¿ÐµÑÐµÐŽÐ°Ð²Ð°ÑÑÐ²</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð¶ÑÑÐœÐ°Ð»Ñ Tor Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž, ÑÐŸ ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°ÑÐŸÐŒÑ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÐµÑÑÐŸÐ³ÐŸ Ð²ÑÐ·Ð»Ð° Ð² Ð»Ð°ÐœÑÑÐ·Ñ Tor. ÐŠÐµ ÐŒÐŸÐ¶Ðµ ÐŸÐ·ÐœÐ°ÑÐ°ÑÐž, ÑÐŸ Ð²Ðž Ð¿ÐµÑÐµÐ±ÑÐ²Ð°ÑÑÐµ Ñ ÐŒÐµÑÐµÐ¶Ñ, ÑÐºÐ° Ð¿ÑÐŽÐŽÐ°ÑÑÑÑÑ ÑÐµÐœÐ·ÑÑÑ. ÐÑÐŽÑ Ð»Ð°ÑÐºÐ°, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽÐºÐ»ÑÑÐžÑÐžÑÑ ÐŽÐŸ ÐŒÐŸÑ ÑÑÐ², Ñ ÑÐµ ÐŒÐ°Ñ Ð²ÐžÑÑÑÐžÑÐž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ.</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â3: ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð·Ð°Ð²ÐµÑÑÐžÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð²ÐžÐºÐŸÐœÐ°ÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS Ð·Ð° ÐŽÐŸÐ¿ÐŸÐŒÐŸÐ³ÐŸÑ ÑÐ»ÑÐ¶Ð± ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ñ. ÐÐžÐºÐŸÑÐžÑÑÐ°ÐœÐœÑ ÐŒÐŸÑÑÑÐ², ÑÐ²ÐžÐŽÑÐµ Ð·Ð° Ð²ÑÐµ, Ð±ÑÐŽÐµ Ð²ÐžÐ¿ÑÐ°Ð²Ð»ÑÑÐž ÑÐµ.</p><h5> ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â4: Ð·Ð±ÐžÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°Ñ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÐœÐµÐ¿Ñ Ð°Ð²ÐžÐ»ÑÐœÐžÐ¹. ÐÑÐŽÑ-Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÐ¹ ÑÐŸÑÐœÐŸ, Ð²ÐºÐ»ÑÑÐœÐŸ Ð· Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐŒ ÑÐ°ÑÐŸÐ²ÐžÐŒ Ð¿ÐŸÑÑÐŸÐŒ. ÐÐŸÑÑÐŒ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÑÑÑ Tor.</p>" + }, + "connecting-3": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-3", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-3", + "title": "Ð¯ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÐœÐ°Ð¹ÑÐž X.onion!", + "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð·ÐœÐ°Ð¹ÑÐž ÑÐ»ÑÐ¶Ð±Ñ onion, ÑÐºÑ Ð²Ðž Ð±Ð°Ð¶Ð°ÑÑÐµ, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž 16-ÑÐžÐŒÐ²ÐŸÐ»ÑÐœÑ onion-Ð°ÐŽÑÐµÑÑ: ÐœÐ°Ð²ÑÑÑ ÐœÐµÐ²ÐµÐ»ÐžÐºÐ° Ð¿ÐŸÐŒÐžÐ»ÐºÐ° ÐœÐµ ÐŽÐŸÐ·Ð²ÐŸÐ»ÐžÑÑ Tor Browser Ð·Ð°Ð¹ÑÐž ÐœÐ° ÑÐ°Ð¹Ñ. Ð¯ÐºÑÐŸ Ð²Ðž Ð²ÑÐµ Ð¶ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÑÐ»ÑÐ¶Ð± onion, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐ·ÐœÑÑÐµ. ÐÐŸÐ¶Ðµ ÑÑÐ°Ð¿ÐžÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° ÑÐžÐŒÑÐ°ÑÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑ, Ð°Ð±ÐŸ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐž ÑÐ°Ð¹ÑÑ ÐŒÐŸÐ¶ÑÑÑ ÐŽÐŸÐ·Ð²ÐŸÐ»ÐžÑÐž Ð¹ÐŸÐŒÑ Ð²ÐžÑÐŸÐŽÐžÑÐž Ð² Ð°Ð²ÑÐŸÐœÐŸÐŒÐœÐžÐ¹ ÑÐµÐ¶ÐžÐŒ Ð±ÐµÐ· Ð¿ÐŸÐ¿ÐµÑÐµÐŽÐ¶ÐµÐœÐœÑ.</p><p class=\"mb-3\">ÐÐž ÑÐ°ÐºÐŸÐ¶ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐºÐŸÐœÐ°ÑÐžÑÑ, ÑÐŸ Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐžÐŒÐ°ÑÐž ÐŽÐŸÑÑÑÐ¿ ÐŽÐŸ ÑÐœÑÐžÑ Ð¿ÐŸÑÐ»ÑÐ³ onion, Ð¿ÑÐŽ'ÑÐŽÐœÐ°Ð²ÑÐžÑÑ ÐŽÐŸ ÑÐ»ÑÐ¶Ð±Ðž Onion ÐœÐ° <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</ a>.</p>" + } +} diff --git a/zh_CN.json b/zh_CN.json new file mode 100644 index 000000000..d2f692083 --- /dev/null +++ b/zh_CN.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#è¿æ¥-1", + "control": "è¿æ¥-1", + "title": "Toræµè§åšæ²¡æè¿æ¥äžäºèçœïŒäœè¿äŒŒä¹å¹¶äžæ¯å äžºçœç»ç®¡æ§é æçé®é¢ã", + "description": "<p class=\"mb-3\">é æTorè¿æ¥å€±èŽ¥çæåžžè§çé®é¢ä¹äžæ¯ç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçç³»ç»æ¶éŽä»¥åæ¶åºè®Ÿçœ®æ£ç¡®ãåŠæè¿äžªé®é¢è¿æ²¡æè¢«è§£å³ïŒè¯·æ¥çäœäº<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Toræµè§åšæå</a></mark>çæéææ¥çé¢ã</p>" + }, + "connecting-2": { + "id": "#è¿æ¥-2", + "control": "è¿æ¥-2", + "title": "æ æ³è¿æ¥å° TorïŒæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", + "description": "<p class=\"mb-3\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥ </h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæ šçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§éè¯¯#3: TLSæ¡æå€±èŽ¥ </h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor äžäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿ çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5>åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯ <pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n ToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœã</code></pre></p><p class=\"mb-3\">è¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ãåŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" + }, + "connecting-3": { + "id": "#è¿æ¥-3", + "control": "è¿æ¥-3", + "title": "ææ æ³è®¿é®X.onionïŒ", + "description": "<p class=\"mb-3\">åŠææšæ æ³è®¿é®æŽè±ç«ç¹ïŒè¯·ç¡®è®€æšèŸå¥äºæ£ç¡®çïŒ16äœççœåïŒå³äœ¿äžäžªåŸ®å°çéè¯¯ä¹äŒé»æ¢Toræµè§åšè®¿é®è¿äžªç«ç¹ãåŠææšè¿æ¯æ æ³è®¿é®è¿äžªçœç«ïŒè¯·çšåéè¯ãè¿å¯èœæ¯ææ¶æ§çé®é¢ïŒæèçœç«ç®¡çåæªç»åºæ ç€ºå°±äžçº¿äºçœç«ã</p><p class=\"mb-3\">æšä¹å¯ä»¥éè¿è®¿é®<a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>çæŽè±ç«ç¹æ¥ç¡®è®€æšçæµè§åšéçœ®æ£ç¡®ã" + } +}

1 0

[translation/master] Fixing master
by translation＠torproject.org 06 Apr '18

06 Apr '18

commit 6a64d8c44ebcff243550080bd5bf2fe47263a4e8 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Apr 6 23:45:14 2018 +0000 Fixing master --- .tx/config | 9 --------- 1 file changed, 9 deletions(-) diff --git a/.tx/config b/.tx/config deleted file mode 100644 index 819a1e2ae..000000000 --- a/.tx/config +++ /dev/null @@ -1,9 +0,0 @@ -[torproject.support-connectingjson] -file_filter = <lang>.json -source_file = support-connecting.json -source_lang = en - -[main] -host = https://www.transifex.net - -minimum_perc = 100

1 0

[translation/master] Fixing master
by translation＠torproject.org 06 Apr '18

06 Apr '18

commit 41d510bf6972a940b96e058df8fb57e77a2fcb15 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Apr 6 23:42:52 2018 +0000 Fixing master --- de.json | 20 -------------------- es.json | 20 -------------------- fr.json | 20 -------------------- ga.json | 20 -------------------- id.json | 20 -------------------- it.json | 20 -------------------- ja.json | 20 -------------------- ms_MY.json | 20 -------------------- nl.json | 20 -------------------- pt_BR.json | 20 -------------------- ro.json | 20 -------------------- support-connecting.json | 20 -------------------- uk.json | 20 -------------------- zh_CN.json | 20 -------------------- 14 files changed, 280 deletions(-) diff --git a/de.json b/de.json deleted file mode 100644 index 05b1a5862..000000000 --- a/de.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#connecting-1", - "control": "connecting-1", - "title": "Tor-Browser kann sich nicht verbinden, aber es scheint nicht an Zensur-MaÃnahmen zu liegen.", - "description": "<p class=\"mb-3\">Eines der hÃ€ufigsten Probleme, die bei Tor-Browser Verbindungsprobleme verursacht, ist eine verstellte System-Uhr. Stelle daher sicher, dass deine System-Uhr und die Zeitzone richtig eingestellt ist. Wenn dies das Problem nicht behebt, besuche die Fehlerbehebungsseite in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor-Browser-Anleitung</a></mark>.</p>" - }, - "connecting-2": { - "id": "#connecting-2", - "control": "connecting-2", - "title": "Ich habe Probleme mich mit Tor zu verbinden und kann die Ursache nicht finden.", - "description": "<p class=\"mb-3\">Wenn du Verbindungsprobleme hast, wÃ€hle bitte die Option \"Tor-Protokoll in die Zwischenablage kopieren\" aus. FÃŒge dann das Tor-Protokoll in eine Textdatei oder ein anderes Dokument ein. Du solltest nun einen der folgenden verbreiteten FehlereintrÃ€ge sehen (suche nach foldenden Zeilen in deinem Tor-Protokoll):</p><h5>Ãblicher Fehlereintrag #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung zu einem SOCKS-Proxy fehlschlÃ€gt. Wenn fÃŒr deine Netzwerkkonfiguration ein SOCKS-Proxy erforderlich ist, stelle sicher, dass du die erforderlichen Proxy-Daten korrekt eingegeben hast. Wenn kein SOCKS-Proxy benÃ¶tigt wird oder du diesbezÃŒglich nicht sicher bist, versuche ohne SOCKS-Proxy eine Verbindung zum Tor-Netzwerk herzustellen.<p><h5>Ãblicher Fehlereintrag #2: Kann WÃ€chter-Weiterleitung nicht erreichen</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/20 17 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung des Tor-Clients mit dem ersten Knoten im Tor-Circuit fehlschlÃ€gt. Dies kann bedeuten, dass du dich in einem zensierten Netzwerk befindest. Versuche dich mit BrÃŒcken zu verbinden, was das Problem beheben sollte.</p><h5>Ãblicher Fehlereintrag #3: Fehlschlag bei der VervollstÃ€ndigung des TLS-Handschlags</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass dein Tor-Client einen TLS-Handschlag mit den Verzeichnisinstanzen nicht erfolgreich abschlieÃen konnte. Die Verwendung von BrÃŒcken wird das wahrscheinlich beheben.</p><h5>Ãblicher Fehlereintrag #4: Taktversatz</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and d ate settings.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass deine System-Uhr verstellt ist. Bitte stelle sicher, dass deine System-Uhr und die entsprechende Zeitzone richtig gestellt sind. Starte Tor danach neu.</p>" - }, - "connecting-3": { - "id": "#connecting-3", - "control": "connecting-3", - "title": "Ich kann X.onion nicht erreichen!", - "description": "<p class=\"mb-3\">Wenn du den gewÃŒnschten Onion-Dienst nicht erreichen kannst, stelle sicher, dass du die 16 Zeichen lange Onion-Adresse richtig eingegeben hast: Sogar ein kleiner Tippfehler verhindert, dass Tor-Browser die Website finden kann. Wenn du dich dann mit dem Onion-Dienst immer noch nicht verbinden kannst, versuche es spÃ€ter noch einmal. Es kann vorÃŒbergehende Verbindungsprobleme im Netz geben oder die Seitenbetreiber haben ohne Vorwarnung die Seite vom Netz genommen.</p><p class=\"mb-3\">Du kannst auch ÃŒberprÃŒfen, ob es dir grundsÃ€tzlich mÃ¶glich ist Onion-Dienste zu nutzen, in dem du dich mit <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>s Onion-Dienst verbindest.</p>" - } -} diff --git a/es.json b/es.json deleted file mode 100644 index 5f8938425..000000000 --- a/es.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#connecting-1", - "control": "connecting-1", - "title": "El Navegador Tor no conecta, pero no parece ser un problema con la censura.", - "description": "<p class=\"mb-3\">Uno de los problemas mÃ¡s habituales que causa errores de conexiÃ³n en el Navegador Tor es un reloj del sistema incorrectamente ajustado. Por favor, asegÃºrate de que el reloj de tu sistema y tu zona horaria estÃ¡n configurados correctamente. Si esto no soluciona tu problema, dirÃgete a la pÃ¡gina de SoluciÃ³n de Problemas en el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">manual del Navegador Tor</a></mark></p>" - }, - "connecting-2": { - "id": "#connecting-2", - "control": "connecting-2", - "title": "Estoy teniendo problemas conectando a Tor, y no logro averiguar quÃ© es lo que estÃ¡ mal.", - "description": "Si tienes problemas para conectarte, por favor selecciona la opciÃ³n \"copiar el registro de Tor al portapapeles\". Luego pega el registro Tor en un archivo de texto u otro documento. DeberÃas ver uno de estos errores comunes de registro (busca las siguientes lÃneas en tu registro Tor): Error comÃºn de registro #1: Fallo de conexiÃ³n proxy 2017-10-29 09:23:40.800[NOTICE] Abriendo socks en 127.0.0.1:9150\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 10%: Finaliza hankshake con el servidor de directorios\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectar toxx.. xxx.. xxx. xx: xxxxxxx (\"fallo general del servidor SOCKS\") Si ves lÃneas como estas en tu registro Tor, significa que no te estÃ¡s conectando a un proxy SOCKS. Si se requiere un proxy SOCKS para la configuraciÃ³n de red, asegÃºrate de introducir correctamente los datos del proxy. Error de registro comÃºn #2: No se puede llegar a los relÃ©s de guardia 11/1/2017 21:11:43 PM. 500[AVISO] Abriendo el socks en 127.0.0.1:9150\n11/1/2017 21:11:44 PM. 300[AVISO] Bootstrapped 80%: ConexiÃ³n a la red Tor\n11/1/2017 21:11:44 PM. 300[ADVERTENCIA] No encontramos nodo para el salto 0 de nuestro camino. Descartar este circuito.\n11/1/2017 21:11:44 PM. 500[AVISO] Bootstrapped 85%: Acabando el handshake con el primer salto\n11/1/2017 21:11:11:45 PM. 300[ADVERTENCIA] No se ha encontrado nodo para el salto 0 de nuestra ruta. Descartando este circuito: si ves lÃneas como estas en tu registro Tor, significa que tu Tor no se conectÃ³ al primer nodo del circuito Tor. Esto podrÃa significar que estÃ¡s en una red ce nsurada. Error de registro comÃºn #3: No se pudo completar el handshake TLS 13-11-17 19:52:24:24.300[ATENCIÃN) Bootstrapped 10%: Finalizar handshake con el servidor de directorios\n13-11-17 19:53:49.300[ADVERTENCIA] Problema con el bootstrapping. Atascado al 10%: Acabando handshake con el servidor de directorios. (HECHO; HECHO; conteo 10; recomendaciÃ³n; host[host] en xxx. xxx. xxx. xxx. xx: xxx)\n13-11-17 19:53:49.300[ATENCIÃN] 10 conexiones han fallado:\n13-11-17 19:53:49.300[ADVERTENCIA] 9 conexiones caidas en estado handshaking (TLS) con estado SSL SSLv2/v3 lea servidor hola A en HANDSHAKE\n13-11-17 19:53:49.300[ADVERTENCIA] 1 conexiones muertas en estado connect()ing con estado SSL (sin objeto SSL) Si ves lÃneas como esta en tu registro de Tor, significa que Tor no pudo completar un handshake TLS con las competencias del directorio. Error de registro comÃºn #4: DesviaciÃ³n del reloj 19.11.2017 00:04:47.400[ATENCIÃN] IntÃ©rprete de socks de apertura en 127.0.0.0.1:9150\n19.1 1.2017 00:04:48.000[ADVERTENCIA] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n19.11.2017 00:04:48.200[ADVERTENCIA] Bootstrapped 10%: Finalizando el handshake con el servidor de directorios\n19.11.2017 00:04:48.800[ADVERTENCIA] Celda de NETINFO recibida con tiempo sesgado (OR: xxx. xx. xx. xx: xxxx): Parece que nuestro reloj estÃ¡ atrasado 1 dÃa, 0 horas, 1 minutos, o que el suyo estÃ¡ adelantado.\nTor requiere un reloj preciso para funcionar: por favor, comprueba tus ajustes de hora, zona horaria y fecha Si ves lÃneas como esta en tu registro Tor, significa que el reloj de tu sistema es incorrecto. AsegÃºrate de que tu reloj estÃ¡ ajustado correctamente, incluyendo la zona horaria. A continuaciÃ³n, reinicia Tor." - }, - "connecting-3": { - "id": "#connecting-3", - "control": "connecting-3", - "title": "Â¡No puedo conectar a X.onion!", - "description": "<p class=\"mb-3\">Si no puede alcanzar el servicio onion que desea, asegÃºrese de que ha introducido correctamente la direcciÃ³n onion de 16 caracteres: incluso un pequeÃ±o error evitarÃ¡ que el Navegador Tor logre alcanzar el sitio. Si aÃºn asÃ no puede conectar al servicio onion, por favor, intÃ©ntelo de nuevo mÃ¡s tarde. Puede haber un problema temporal con la conexiÃ³n, o los operadores del sitio pueden haberle permitido desconectar sin avisar.</p><p class=\"mb-3\">TambiÃ©n puede asegurarse de que es capaz de acceder a otros servicios onion conectando al servicio onion de <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" - } -} diff --git a/fr.json b/fr.json deleted file mode 100644 index 4ed10c84e..000000000 --- a/fr.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">âguide du navigateur Tor</a></mark>.</p>" - }, - "connecting-2": { - "id": "#connexion-2", - "control": "connexion-2", - "title": "JâÃ©prouve des difficultÃ©s Ã me connecter Ã Tor et je nâarrive pas Ã comprendre ce qui ne va pas.", - "description": "<p class=\"mb-3\">Si vous Ã©prouvez des difficultÃ©s Ã vous connecter, veuillez sÃ©lectionner lâoption Â«Â Copier le journal de Tor dans le presse-papiersÂ Â». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver lâune de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor)Â : </p><h5>Erreur habituelle de journal noÂ 1 : Ã©chec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter Ã un mandataire SOCKS. Si un mandataire SOCKS est nÃ©cessaire Ã la configuration de rÃ©seau, veuillez alors vous assurer dâavoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS nâest pas nÃ©cessaire ou si vous ne savez pas, veuillez tenter de vous connecter au rÃ©seau Tor sans mandataire SOCKS.<p><h5>Erreur habituelle de journal noÂ 2 : impossible dâatteindre les relais gardes</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/ 2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter au premier nÅud du circuit Tor. Cela pourrait signifier que vous Ãªtes sur un rÃ©seau qui est censurÃ©. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5>Erreur habituelle de journal noÂ 3 : Ã©chec dâÃ©tablissement dâune liaison TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19 :53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas rÃ©ussi Ã Ã©tablir une liaison TLS avec les autoritÃ©s d'annuaire. Lâutilisation de ponts corrigera certainement cette situation.</p><h5>Erreur habituelle de journal noÂ 4 : dÃ©calage dâhorloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or t hat theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">\nSi vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge systÃšme nâest pas juste. Veuillez vous assurer que votre horloge est rÃ©glÃ©e avec prÃ©cision, fuseau horaire inclus, puis redÃ©marrez Tor. </p>" - }, - "connecting-3": { - "id": "#connexion-3", - "control": "connexion-3", - "title": "Je ne peux pas accÃ©der Ã X.onionâ!", - "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">Vous pouvez aussi vous assurer que vous arrivez Ã accÃ©der Ã dâautres services oignon en vous connectant au service oignon de <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>\n\n" - } -} diff --git a/ga.json b/ga.json deleted file mode 100644 index 26d45c2d5..000000000 --- a/ga.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#connecting-1", - "control": "connecting-1", - "title": "NÃ fÃ©idir le BrabhsÃ¡laÃ Tor ceangal a bhunÃº, cÃ© nach mbaineann an fhadhb le cÃºrsaÃ cinsireachta.", - "description": "<p class=\"mb-3\">Is minic go mbÃonn fadhb le clog an chÃ³rais ina chÃºis le hearrÃ¡idÃ i mBrabhsÃ¡laÃ Tor. Ba chÃ³ir duit deimhniÃº go bhfuil clog an chÃ³rais agus an crios ama socraithe mar is ceart. Mura rÃ©itÃonn seo an fhadhb, fÃ©ach an leathanach FabhtcheartÃº i <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">LÃ¡mhleabhar BhrabhsÃ¡laÃ Tor</a></mark>.</p>" - }, - "connecting-2": { - "id": "#connecting-2", - "control": "connecting-2", - "title": "NÃ fÃ©idir liom ceangal le lÃonra Tor, agus nÃ thuigim cad Ã© an fhadhb.", - "description": "<p class=\"mb-3\">MÃ¡ tÃ¡ fadhb agat ag ceangal le lÃonra Tor, ÃºsÃ¡id an rogha âcÃ³ipeÃ¡il logchomhad Tor go dtÃ an ghearrthaisce.â Ansin, greamaigh an logchomhad i dtÃ©acschomhad nÃ³ cÃ¡ipÃ©is eile. Is dÃ³cha go bhfeicfidh tÃº ceann de na hearrÃ¡idÃ coitianta seo (cuardaigh na lÃnte seo a leanas sa logchomhad):</p><h5>EarrÃ¡id choitianta #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to co nnect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn siad gur theip ort ceangal a bhunÃº le seachfhreastalaÃ SOCKS. MÃ¡ theastaÃonn seachfhreastalaÃ SOCKS uait ar do lÃonra, deimhnigh gur chuir tÃº mionsonraÃ an fhreastalaÃ isteach go ceart. Mura dteastaÃonn seachfhreastalaÃ SOCKS uair, nÃ³ mura bhfuil tÃº cinnte, dÃ©an iarracht ceangal a bhunÃº le lÃonra Tor gan seachfhreastalaÃ SOCKS.<p><h5>EarrÃ¡id choitianta #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] F ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ort ceangal a bhunÃº leis an chÃ©ad nÃ³d sa gciorcad Tor. Uaireanta, ciallaÃonn seo go bhfuil do lÃonra faoi chinsireacht. Bain triail as ceangal trÃ dhroichead; is dÃ³cha go rÃ©iteoidh sin an fhadhb.</p><h5>EarrÃ¡id choitianta #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 co nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ar Tor croitheadh lÃ¡imhe TLS leis na hÃºdarÃ¡is a chur i gcrÃch. Is dÃ³cha go rÃ©iteoidh droichead an fhadhb seo.</p><h5>EarrÃ¡id choitianta #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, c iallaÃonn sÃ© go bhfuil an clog i do rÃomhaire mÃcheart. Ba chÃ³ir duit socruithe an chloig a dheimhniÃº, an t-am, dÃ¡ta, agus crios ama san Ã¡ireamh. Ansin, atosaigh Tor. </p>" - }, - "connecting-3": { - "id": "#connecting-3", - "control": "connecting-3", - "title": "NÃlim in ann teacht ar X.onion!", - "description": "<p class=\"mb-3\">Mura bhfuil tÃº in ann seirbhÃs .onion a shroicheadh, deimhnigh gur chuir tÃº an seoladh 16-carachtar isteach go ceart: mÃ¡ tÃ¡ aon bhotÃºn ann, fiÃº botÃºn an-bheag, nÃ bheidh BrabhsÃ¡laÃ Tor in ann an suÃomh a shroicheadh. MÃ¡ tÃ¡ tÃº cinnte gur chuir tÃº an seoladh ceart isteach, bain triail eile as ar ball. Seans go bhfuil fadhb shealadach leis an lÃonra, nÃ³ b'fhÃ©idir gur bhain riarthÃ³irÃ an tsuÃmh as lÃne Ã© gan rabhadh.</p><p class=\"mb-3\">B'fhiÃº freisin fÃ©achaint an fÃ©idir leat dul i dteagmhÃ¡il le seirbhÃsÃ .onion eile, mar shampla <a href=\"http://3g2upl4pq6kufc4m.onion\">seirbhÃs DuckDuckGo</a>.</p>" - } -} diff --git a/id.json b/id.json deleted file mode 100644 index 0fdc118e3..000000000 --- a/id.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#connecting-1", - "control": "connecting-1", - "title": "Tor Browser tidak dapat tersambung, tapi ini tampaknya bukan akibat sensor oleh pihak lain.", - "description": "<p class=\"mb-3\">Salah satu masalah umum yang menyebabkan kegagalan koneksi di Tor Browser adalah jam sistem operasi yang tidak tepat. Silakan pastikan jam di sistem operasi dan zona waktu diatur dengan tepat di komputer Anda. Jika ini tidak memperbaiki masalah koneksi, lihat halaman Troubleshooting di <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser</a></mark>.</p>" - }, - "connecting-2": { - "id": "#connecting-2", - "control": "connecting-2", - "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", - "description": "<p class=\"mb-3\"> Jika Anda mendapat masalah dalam terhubung ke jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):\n\n</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS se rver failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.\n\n<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> Jika Anda melihat baris seperti ini, Tor gagal tersambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.\n\n</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.<h5>\n\nCommon log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. Tor memerlukan jam yang akurat supaya berfungsi dengan baik. Silakan periksa pengaturan waktu, zona waktu, dan tanggal. Pastikan jam di komputer Anda diatur dengan benar, termasuk zona waktu yang tepat. Lalu, restart Tor.\n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" - }, - "connecting-3": { - "id": "#connecting-3", - "control": "connecting-3", - "title": "Tidak dapat terhubung ke X.onion!", - "description": "<p class=\"mb-3\">Jika Anda tidak dapat terhubung ke sebuah onion service yang diinginkan, pastikan Anda telah dengan tepat memasukkan 16-karakter alamat onion-nya. Bahkan kesalahan sedikit akan membuat Tor Browser tidak dapat terhubung ke situs yang dimaksud. Jika Anda tetap tidak dapat terhubung, silakan coba lagi nanti. Mungkin ada masalah sedikit di situsnya, atau operator situsnya sedang membuat situsnya menjadi offline tanpa pemberitahuan. </p><p class=\"mb-3\">Anda juga dapat memastikan jika Anda juga dapat terhubung ke situs onion service lain dengan mencoba terhubung ke <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>." - } -} diff --git a/it.json b/it.json deleted file mode 100644 index 7a04f1284..000000000 --- a/it.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#connessione-1", - "control": "connessione-1", - "title": "Tor Browser non si connette, ma non sembra che sia dovuto alla censura.", - "description": "<p class=\"mb-3\">Uno dei problemi piÃ¹ comuni che causano errori di connessione in Tor Browser Ãš un orologio di sistema errato. Assicurati che l'orologio di sistema e il fuso orario siano impostati correttamente. Se ciÃ² non risolve il problema, consultare la pagina Risoluzione dei problemi su <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manuale di Tor Browser</a></mark>.</p>" - }, - "connecting-2": { - "id": "#connessione-2", - "control": "connessione-2", - "title": "Sto avendo problemi nella connessione a Tor e non riesco a capire quale sia la causa.", - "description": "<p class=\"mb-3\">Se stai avendo problemi a connetterti, per favore seleziona l'opzione \"copia i log di Tor sulla clipboard.\" Poi incolla il log di Tor su un file di testo o un altro tipo di documento. Dovresti vedere uno di questi errori di log comuni (cerca per le seguenti linee nei log di Tor):</p><h5>Errore di log comune #1: Errore di connessione Proxy </h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150\n2017-10-29 09:23:47.900 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n2017-10-29 09:23:47.900 [AVVISO] Progressione 10%: Completando l'handshake con l'elenco dei server\n2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\nÂ 2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\n2017-10-29 09:24:08.900 [ATTENZIONE] Prox y Client: impossibile connettersi a xx..xxx..xxx.xx:xxxxx (\"errore generale server SOCKS\")</code></pre></p><p class=\"mb-3\">Se vedi delle linee come queste nei log di Tor, significa che la connessione a un proxy SOCKS sta fallendo.Se un proxy SOCKS Ãš richiesto per la tua configurazione di rete, controlla di aver inserito i dettagli del proxy correttamente.Se un proxy SOCKS non Ãš richiesto, o non ne sei sicuro, prova a connetterti alla rete Tor senza un proxy SOCKS.<p><h5>Errore di log comune #2: Non Ãš possibile raggiungere i guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150 \n11/1/2017 21:11:44 PM.300 [AVVISO] Progressione 80%: Connessione alla rete Tor\n11/1/2017 21:11:44 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.\n11/1/2017 21:11:44 PM.500 [AVVISO] Progressione 85%: Terminando l'handshake con il primo hop\nÂ 11/1/2017 21:11:45 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.</code></pre></p><p class=\"mb-3\">Se vedi delle linee come questo nel tuo log di Tor, significa che Tor ha fallito la connesione al primo nodo del circuito Tor. Questo potrebbe significare che ti trovi su una rete censurata. Per favore prova a connetterti con i bridge, e questo dovrebbe risolvere il problema.</p><h5>Errore di log comune #3: Errore nel completare l'handshake TLS</h5><p class=\"mb-3\"><pre><code>13-11-17 19:52:24.300 [AVVISO] Progressione 10%: Handshake con l'elenco dei server completato\n13-11-17 19:53:49.300 [ATTENZIONE] Problema durante la progressione. Fermo al 10%: Completando l'handshake con l'elenco dei server (FATTO; FATTO; contatore 10; avviso di raccomandazione; host [host] a xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [ATTENZIONE] 10 connessioni hanno fallito:\n13-11-17 19:53:49.300 [ATTENZIONE] 9 connessioni sono scadute durante lo stato di handshaking (TLS) con lo stato SSL di SSLv2/v3 r isposta server hello A in HANDSHAKE \n13-11-17 19:53:49.300 [ATTENZIONE] 1 connessione Ãš scaduta nello stato di connessione con stato SSL (Nessun oggetto SSL)</code></pre></p><p class=\"mb-3\">Se vedi delle linee cosÃ¬ nel tuo log Tor, significa che Tor ha fallito il completamento dell'handshake TLS con le autoritÃ dell'elenco. Usare i bridge risolverÃ probabilmente il problema.</p><h5>Errore log comune #4: Distorsione orario</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [AVVISO] Apertura ascoltatore porte SOCKS su 127.0.0.1:9150\n19.11.2017 00:04:48.000 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n19.11.2017 00:04:48.200 [AVVISO] Progressione 10%: Terminando l'handshake con l'elenco dei server\n19.11.2017 00:04:48.800 [ATTENZONE] Ricevuta cella NETINFO con orario distorto (O:xxx.xx.x.xx:xxxx): Sembra che il tuo orologio sia indietro di 1 giorno, 0 ore, 1 minuto, o che il loro sia avanti.\nTor richiede un orologio accurato per funzionare: per favore con trolla l'ora, la tua zona temporale e le impostazioni sulla data.</code></pre></p><p class=\"mb-3\">Se vedi queste linee nel tuo log di Tor, significa che l'ora del sistema Ãš incorretta. Per favore controlla che il tuo orologio sia impostato accuratamente, inclusa la zona temporale. DopodichÃ© riavvia Tor.</p>" - }, - "connecting-3": { - "id": "#connessione-3", - "control": "connessione-3", - "title": "Non posso raggiungere X.onion!", - "description": "<p class=\"mb-3\">Se non riesci a raggiungere il sito che desideri, assicurati di aver inserito correttamente l'indirizzo a 16 caratteri: anche un piccolo errore puÃ² impedire al Tor Browser di raggiungere il sito. Se non riesci ancora a connetterti al sito, riprova piÃ¹ tardi. Potrebbe esserci un problema di connessione temporaneo, oppure gli operatori del sito lo hanno lasciato andare offline senza lasciare preavviso.</p><p class=\"mb-3\">Puoi anche provare a connetterti a <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a> per vedere se riesci ad accedere ad altri siti.</p>" - } -} diff --git a/ja.json b/ja.json deleted file mode 100644 index 24309f341..000000000 --- a/ja.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#æ¥ç¶-1", - "control": "æ¥ç¶-1", - "title": "Torãã©ãŠã¶ãŒã¯æ¥ç¶ããŸããããæ€é²ã®åé¡ã§ã¯ãªãããã§ãã", - "description": "Torãã©ãŠã¶ãŒã§æ¥ç¶ãšã©ãŒãçºçããæãäžè¬çãªåé¡ã®1ã€ã¯ãäžæ£ãªã·ã¹ãã ã¯ããã¯ã§ããã·ã¹ãã ã®æèšãšã¿ã€ã ãŸãŒã³ãæ£ç¢ºã«èšå®ãããŠããããšãç¢ºèªããŠãã ãããããã§åé¡ãè§£æ±ºããªãå Žåã¯ãTorãã©ãŠã¶ãŒã®ããã¥ã¢ã«ã®ãã©ãã«ã·ã¥ãŒãã£ã³ã°ã®ããŒãžãåç§ããŠãã ããã" - }, - "connecting-2": { - "id": "#æ¥ç¶-2", - "control": "æ¥ç¶-2", - "title": "Torã«ã¢ã¯ã»ã¹ã§ããªãããäœãåé¡ãªã®ãåãããŸããã", - "description": "<p class=\"mb-3\">Torã«ã¢ã¯ã»ã¹ã§ããªãå ŽåããTorãã°ãã¯ãªããããŒãã«ã³ããŒãããéžæè¢ãéžãã§ããã°ãã¡ã¢åž³ãããã¯ããã¥ã¡ã³ããã¡ã€ã«ã«è²Œãä»ããŠäžãããä»¥äžã®è¯ããããšã©ãŒã¡ãã»ãŒãžãèŠã€ããã¯ãã§ãïŒ</p><h5>ãããããã°ãšã©ãŒ#1: ãããã·æ¥ç¶å€±æ</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx.. xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãSOCKSãããã·ãšç¹ãããªããšããããšã§ãããããã¯ãŒã¯ã«ã¯SOCKSãããã·ãå¿èŠãªããèšå®ãç¢ºèªããŠäžãããSOCKSãããã·ãå¿èŠã§ã¯ãªãå Žåããããã¯ããåãããªãå ŽåãSOCKSãããã·ç¡ãã§Torã«ã¢ã¯ã»ã¹ããŠã¿ãŠäžããã<p><h5>ãããããã°ãšã©ãŒ#2: ã¬ãŒããªã¬ãŒãšæ¥ç¶ã§ããªã</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discardi ng this circuit.</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorã¯circuitã®æåã®ããŒããšæ¥ç¶ã§ããªãã£ããšããããšã§ããæ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ããããŸããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããã¯ãã§ãã</p><h5>ãããããã°ãšã©ãŒ#3: TLSãã³ãã·ã§ã€ã¯ã®å€±æ</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorããã£ã¬ã¯ããªãªãŒãœãªãã£ãšTLSãã³ãã·ã§ã€ã¯ãå®äºã§ããªãã£ããšããããšã§ããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããå¯èœæ§ãããã</p><h5>ãããããã°ãšã©ãŒ#4: ã¯ããã¯ã¹ãã¥ãŒ</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p clas s=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãã·ã¹ãã ã»ã¯ããã¯ã«ã¯ééã£ãæå»ãèšå®ãããŸããã·ã¹ãã ã»ã¯ããã¯ãæ£ããæå»ãšã¿ã€ã ãŸãŒã³ã«åãããŠããTorãåèµ·åããŠäžããã </p>" - }, - "connecting-3": { - "id": "#æ¥ç¶-3", - "control": "æ¥ç¶-3", - "title": "X.onionãååŸã§ããŸããïŒ", - "description": "ããªããæããªããªã³ã®ãµãŒãã¹ã«ã¢ã¯ã»ã¹ã§ããªãå Žåã¯ã16æåã®ãªããªã³ã¢ãã¬ã¹ãæ£ããå¥åããããšãç¢ºèªããŠãã ãããå°ããªééãã§ããTorãã©ãŠã¶ãŒããµã€ãã«ã¢ã¯ã»ã¹ã§ããªããªããŸãã" - } -} diff --git a/ms_MY.json b/ms_MY.json deleted file mode 100644 index 94afcb73e..000000000 --- a/ms_MY.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#menyambung-1", - "control": "menyambung-1", - "title": "Pelayar Tor tidak dapat bersambung, tetapi ia bukanlah isu berkenaan penapisan.", - "description": "<p class=\"mb-3\">Salah satu masalah utama yang menyebabkan ralat sambungan dalam Pelayar Tor ialah jam sistem yang salah. Sila pastikan jam sistem dan zon waktu anda telah ditetapkan dengan betul. Jika masalah ini masih berlaku, sila rujuk laman Pencarisilapan di dalam <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âpanduan Pelayar Tor</a></mark>.</p>" - }, - "connecting-2": { - "id": "#menyambung-2", - "control": "menyambung-2", - "title": "Saya menghadapi masalah ketika menyambung dengan Tor, dan saya tidak tahu apa masalah yang berlaku.", - "description": "<p class=\"mb-3\">Jika anda menghadapi masalah sambungan, pilih pilihan \"salin log Tor ke papan keratan.â Kemudian tampal log Tor ke dalam fail teks atau lain-lain fail dokumen. Anda akan dapati terdapat ralat log (lihat baris berikut di dalam log Tor anda):</p><h5>Ralat log umum #1: Kegagalan sambungan proksi</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\" )</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud anda gagal menyambung dengan proksi SOCKS. Jika proksi SOCKS diperlukan untuk persediaan rangkaian anda, maka sila pastikan anda telah memasukkan perincian proksi tersebut dengan betul. Jika proksi SOCKS tidak diperlukan, atau anda tidak pasti, cuba sambung ke rangkaian Tor tanpa proksi SOCKS.<p><h5>Ralat log umum #2: Tidak dapat capai geganti pengawal</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb- 3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud Tor anda gagal menyambung ke nod pertama dalam litar Tor. Ia bermaksud anda berada dalam rangkaian bertapis. Cuba menyambung dengan titi, dan sepatutnya ia masalah selesai.</p><h5>Ralat log umum #3: Gagal menyelesaikan jabat-tangan TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat ba ris seperti ini di dalam log Tor anda, ia bermaksud Tor gagal menyelesaikan jabat-tangan TLS dengan autoriti direktori. Penggunaan titi dapat menyelesaikan masalah ini.</p><h5>Ralat log umum #4: Pencong jam</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini dalam log Tor anda, ia bermaksud jam sistem anda salah. Sila pastikan jam anda telah ditetapkan dengan tepat, termasuklah zon waktu yang betul. Kemudian mulakan semula Tor. </p>" - }, - "connecting-3": { - "id": "#menyambung-3", - "control": "menyambung-3", - "title": "Saya tidak dapat mencapai X.onion!", - "description": "<p class=\"mb-3\">Jika anda masih tidak dapat mencapai servis onion yang dikehendaki, pastikan anda telah memasukkan alamat onion 16-aksara dengan betul: walaupun dengan kesilapan kecil akan menghentikan Pelayar Tor mencapai laman. Jika anda masih tidak dapat menyambung ke servis onion, cuba sekali lagi. Kadangkala ia merupakan masalah sambungan sementara, atau operator laman telah menjadi luar talian tanpa apa-apa amaran.</p><p class=\"mb-3\">Anda juga perlu pastikan dapat mencapai servis onion lain dengan menyambung ke Servis Onion <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" - } -} diff --git a/nl.json b/nl.json deleted file mode 100644 index 4fdd4e365..000000000 --- a/nl.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#verbinden-1", - "control": "verbinden-1", - "title": "Tor Browser maakt geen verbinding, maar het lijkt geen probleem te zijn met censuur.", - "description": "<p class=\"mb-3\">Een van de meest voorkomende problemen die verbindingsfouten in Tor Browser veroorzaken, is een onjuiste systeemklok. Zorg ervoor dat uw systeemklok en tijdzone nauwkeurig zijn ingesteld. Als dit het probleem niet oplost, zie de pagina Problemen oplossen op de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser manual</a></mark>.</p>" - }, - "connecting-2": { - "id": "#verbinden-2", - "control": "verbinden-2", - "title": "Ik ondervind problemen bij het verbinding maken met Tor, en ik vind maar niet wat er fout gaat.", - "description": "<p class=\"mb-3\">Als u problemen ondervindt bij het verbinden, selecteert u de optie om \"Tor log naar klembord te kopiÃ«ren\". Plak vervolgens het Tor-log in een tekstbestand of een ander document. U zou een van deze Vaak voorkomend logfouten moeten zien (kijk naar de volgende regels in uw Tor-logboek): </p><h5>Vaak voorkomend logboekfout # 1: Proxy-verbindingsfout</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09: 23: 40.800 [LET OP] Opening Socks luisteraar op 127.0.0.1 : 9150 \n 2017-10-29 09: 23: 47.900 [LET OP] Bootstrapped 5%: verbinden met directoryserver \n 2017-10-29 09: 23: 47.900 [LETICE] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-clie nt: kan toxx..xxx..xxx.xx: xxxxx niet verbinden (\"algemene SOCKS-serverstoring\") </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, is dit betekent dat u geen verbinding kunt maken met een SOCKS-proxy. Als een SOCKS-proxy vereist is voor uw netwerkconfiguratie, moet u ervoor zorgen dat u uw proxy-gegevens correct hebt ingevoerd. Als een SOCKS-proxy niet vereist is, of als u het niet zeker weet, probeer dan verbinding te maken met het Tor-netwerk zonder een SOCKS-proxy.<p><h5>Gebruikslog fout # 2: Kan relais niet bereiken</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM .500 [LET OP] Luisteraar luisterpositie openen op 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [LET OP] Bootstrapped 80%: Verbinding maken met het Tor-netwerk \n 11/1/2017 21:11:44 PM.300 [WARN] Kan knooppunt voor hop 0 van ons pad niet vinden. Dit circuit weggooien. \n 11/1/2017 21:11:44 PM.500 [LET OP] Bootstrap 85%: Handshake beÃ«indigen met eerste hop \n 11/1/2017 21:11:45 P M.300 [WARN] Kan knooppunt niet vinden voor hop 0 van ons pad. Dit circuit verwijderen.</code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dit dat uw Tor geen verbinding kon maken met het eerste knooppunt in het Tor-circuit. Dit kan betekenen dat u zich op een netwerk bevindt dat gecensureerd is. Probeer te verbinden met bruggen, en dat zou het probleem moeten verhelpen.</p><h5> Algemene logfout # 3: Kan TLS-handshake niet voltooien</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 13-11-17 19: 53: 49.300 [WARN] Probleem met bootstrappen. Vastgelopen met 10%: handshake beÃ«indigen met directoryserver. (GEDAAN, GEDAAN, aantal 10; advieswaarschuwing; host [host] op xxx.xxx.xxx.xx: xxx) \n 13-11-17 19: 53: 49.300 [WARN] 10 verbindingen zijn mislukt: \n 13-11-17 19: 53: 49.300 [WARN] 9 verbindingen stierven in staatshandshaking (TLS) met SSL-status SSLv2 / v3 lezen server hallo A in HANDSHAKE \n 13-11-17 19: 53: 49.300 [WARN] 1 verbindingen zijn overleden in state connect () ing met SSL-staat (No SSL-object) </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dat Tor een TLS-handshake niet kon voltooien met de directory-autoriteiten. Het gebruik van bruggen lost dit waarschijnlijk op.</p><h5>Veel logboekfout # 4: Klok skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00: 04: 47.400 [LET OP] Opening Socks luisteraar op 127.0.0.1:9150 \n 19.11.2017 00: 04: 48.000 [LET OP] Bootstrap 5%: verbinding maken met directoryserver \n 19.11.2017 00: 04: 48.200 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 19.11.2017 00: 04: 48.800 [WARN] NETINFO-cel ontvangen met scheve tijd (OF: xxx.xx.x.xx: xxxx): het lijkt erop dat onze klok 1 dag, 0 uur, 1 minuut achterloopt, of die van hen liggen voor de deur. \n Tor vereist een nauwkeurige klok om te werken: controleer uw tijd-, tijdzone- en datuminstellin gen.</code></pre></p><p class=\"mb-3\">Als u lijnen zoals deze in uw Tor-logboek ziet, betekent dit dat uw systeemklok onjuist is. Zorg ervoor dat uw klok correct is ingesteld, inclusief de juiste tijdzone. Start dan Tor opnieuw. </p>" - }, - "connecting-3": { - "id": "#verbinden-3", - "control": "verbinden-3", - "title": "Ik kan X.onion niet bereiken!", - "description": "<p class=\"mb-3\">Als u de gewenste onion service niet kunt bereiken, moet u ervoor zorgen dat u het onion adres van 16 tekens correct hebt ingevoerd: zelfs een kleine fout zal ervoor zorgen dat Tor Browser de site niet kan bereiken. Als u nog steeds geen verbinding kunt maken met de onion service, probeert u het later opnieuw. Er kan een tijdelijke verbinding probleem zijn, of de site exploitanten kunnen hebben toegestaan dat het offline gaan zonder waarschuwing.</p><p class=\"mb-3\"> U kunt er ook voor zorgen dat u in staat om toegang te krijgen tot andere diensten ui door verbinding te maken <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s Onion Service.</p>" - } -} diff --git a/pt_BR.json b/pt_BR.json deleted file mode 100644 index a1bf886e7..000000000 --- a/pt_BR.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "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.", - "description": "<p class=\"mb-3\">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</a></mark>.</p>" - }, - "connecting-2": { - "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": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opÃ§Ã£o para \"copiar o log de Tor para a Ã¡rea de transferÃªncias\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. VocÃª deverÃ¡ ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexÃ£o de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretÃ³rio\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretÃ³rio\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0 8.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se vocÃª encontrar linhas como estas em seu log do Tor, isto significa que falhou em conectar-se Ã um SOCKS proxy. Se um SOCKS proxy Ã© obrigatÃ³rio para a sua configuraÃ§Ã£o de rede, por favor certifique-se que vocÃª digitou seus detalhes de proxy corretamente. Se um SOCKS proxy nÃ£o Ã© obrigatÃ³rio, ou vocÃª nÃ£o estÃ¡ certo sobre isso, por favor tente conectar-se Ã rede Tor sem um 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\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.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\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hand shake 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\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor 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": "#conectando-3", - "control": "conectando-3", - "title": "NÃ£o consigo conectar ao X.onion!", - "description": "<p class=\"mb-3\">Se vocÃª nÃ£o conseguir acessar o serviÃ§o onion desejado, certifique-se de ter digitado o endereÃ§o onion com 16 caracteres corretamente: atÃ© mesmo um pequeno erro impedirÃ¡ que o Navegador Tor alcance o site. Se vocÃª ainda nÃ£o conseguir se conectar ao serviÃ§o onion, tente novamente mais tarde. Pode haver um problema de conexÃ£o temporÃ¡ria ou os operadores do site podem ter permitido que ele fique offline sem aviso prÃ©vio.</p><p class=\"mb-3\"> VocÃª tambÃ©m pode garantir que poderÃ¡ acessar outros serviÃ§os onion conectando-se ao <a href=\"http://3g2upl4pq6kufc4m.onion\">ServiÃ§o Onion</a>do DuckDuckGo.</p>" - } -} diff --git a/ro.json b/ro.json deleted file mode 100644 index 2fe13067e..000000000 --- a/ro.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#connecting-1", - "control": "conectare-1", - "title": "Tor Browser nu se conecteazÄ, dar nu pare a fi o problemÄ de cenzurÄ.", - "description": "<p class=\"mb-3\">Una din cele mai frecvente cauze pentru problemele de conectare ale Tor Browser este ora sistemului incorectÄ. VerificÄ dacÄ ora Èi fusul orar sunt setate corect. DacÄ aceasta nu rezolvÄ problema, urmeazÄ indicaÈiile de Depanare din <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âmanualul Tor Browser</a></mark>.</p>" - }, - "connecting-2": { - "id": "#connecting-2", - "control": "conectare-2", - "title": "Am dificultÄÈi Ã®n conectarea la Tor Èi nu Ã®nÈeleg ce e greÈit.", - "description": "<p class=\"mb-3\">DacÄ ai probleme de conectare, selecteazÄ opÈiunea \"copiazÄ log-ul Tor Ã®n clipboard\". Apoi lipeÈte log-ul astfel copiat Ã®ntr-un fiÈier text sau alt document. Ar trebui sÄ vezi unul dintre aceste mesaje de eroare comune (cautÄ astfel de linii Ã®n log-ul Tor):</p><h5>Eroare comunÄ #1: Eroare de conectare la proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-ul Tor, Ã®nseamnÄ cÄ nu te poÈi conecta la un proxy SOCKS. DacÄ un proxy SOCKS este necesar pentru reÈeaua pe care o foloseÈti, atunci asigurÄ-te cÄ ai introdus setÄrile de proxy corecte. DacÄ un proxy SOCKS nu e necesar sau nu eÈti sigur, Ã®ncearcÄ sÄ te conectezi la reÈeaua Tor fÄrÄ un proxy SOCKS.<p><h5>Eroare comunÄ #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\" >DacÄ vezi astfel de linii in log-ul Tor Ã®nseamnÄ ca nu s-a reuÈit conectarea la primul nod din circuitul Tor. Aceasta ar putea Ã®nsemna cÄ te afli Ã®ntr-o reÈea cenzuratÄ. ÃncearcÄ conectarea prin punÈi, care ar trebui sÄ rezolve problema.</p><h5>Eroare comunÄ #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-u l Tor Ã®nseamnÄ cÄ nu s-a realizat o conexiune completÄ TLS cu serverele de directoare. Folosirea punÈilor va rezolva probabil acest lucru. </p><h5>Eroare comunÄ #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-ul Tor Ã®nseamnÄ cÄ ceasul sistemului tÄu e incorect. AsigurÄ-te cÄ ceasul sistemului este corect, inclusiv fusul orar, apoi reporneÈte Tor. </p>" - }, - "connecting-3": { - "id": "#connecting-3", - "control": "conectare-3", - "title": "Nu pot ajunge la X.onion!", - "description": "<p class=\"mb-3\">DacÄ nu poÈi ajunge la serviciul onion dorit, asigurÄ-te cÄ ai introdus cele 16 caractere din adresa onion corect - chiar Èi cea mai micÄ eroare va Ã®mpiedica Tor Browser sÄ ajungÄ la site. DacÄ tot nu poÈi ajunge la serviciul onion, Ã®ncearcÄ mai tÃ¢rziu. E posibil sÄ fie o problemÄ temporarÄ de conexiune sau operatorii site-ului l-au deconectat fÄrÄ avertizare. </p><p class=\"mb-3\">PoÈi sÄ te asiguri cÄ alte servicii onion sunt accesibile conectÃ¢ndu-te la serviciul onion al <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" - } -} diff --git a/support-connecting.json b/support-connecting.json deleted file mode 100644 index cac143183..000000000 --- a/support-connecting.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" - }, - "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" - }, - "connecting-3": { - "id": "#connecting-3", - "control": "connecting-3", - "title": "I cannot reach X.onion!", - "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" - } -} diff --git a/uk.json b/uk.json deleted file mode 100644 index 32a35f4fc..000000000 --- a/uk.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-1", - "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-1", - "title": "ÐÑÐ°ÑÐ·ÐµÑ Tor ÐœÐµ Ð±ÑÐŽÐµ Ð¿ÑÐŽ'ÑÐŽÐœÑÐ²Ð°ÑÐžÑÑ, Ð°Ð»Ðµ ÑÐµ, Ð·ÐŽÐ°ÑÑÑÑÑ, ÐœÐµ Ñ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐŸÑ Ð· ÑÐµÐœÐ·ÑÑÐŸÑ.", - "description": "<p class=\"mb-3\">ÐÐŽÐœÑÑÑ Ð· ÐœÐ°Ð¹Ð±ÑÐ»ÑÑ Ð¿ÐŸÑÐžÑÐµÐœÐžÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ, ÑÐŸ Ð¿ÑÐžÐ·Ð²ÐŸÐŽÑÑÑ ÐŽÐŸ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ñ Ð±ÑÐ°ÑÐ·ÐµÑÑ Tor, Ñ ÐœÐµÐ¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐ¹ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº. ÐÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÑ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÑÐ° ÑÐ°ÑÐŸÐ²ÐžÐ¹ Ð¿ÐŸÑÑ Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÑÐŸÑÐœÐŸ. Ð¯ÐºÑÐŸ ÑÐµ ÐœÐµ Ð²ÐžÑÑÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ, Ð¿ÐµÑÐµÐ³Ð»ÑÐœÑÑÐµ ÑÑÐŸÑÑÐœÐºÑ ÑÑÑÐœÐµÐœÐœÑ ÐœÐµÐ¿ÐŸÐ»Ð°ÐŽÐŸÐº Ñ <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Ð¿ÐŸÑÑÐ±ÐœÐžÐºÑ ÐºÐŸÑÐžÑÑÑÐ²Ð°ÑÐ° Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor</a></mark>.</p>" - }, - "connecting-2": { - "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-2", - "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-2", - "title": "Ð£ ÐŒÐµÐœÐµ Ð²ÐžÐœÐžÐºÐ»Ð° Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ ÐŽÐŸ Tor, Ñ Ñ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÑÐŸÐ·ÑÐŒÑÑÐž, ÑÐŸ ÐœÐµ ÑÐ°Ðº.", - "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð²Ð°Ñ Ð²ÐžÐœÐžÐºÐ»Ðž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐž Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ, Ð²ÐžÐ±ÐµÑÑÑÑ ÐŸÐ¿ÑÑÑ Â«ÐºÐŸÐ¿ÑÑÐ²Ð°ÑÐž Ð¶ÑÑÐœÐ°Ð» Tor Ñ Ð±ÑÑÐµÑ ÐŸÐ±ÐŒÑÐœÑÂ». ÐÐŸÑÑÐŒ Ð²ÑÑÐ°Ð²ÑÐµ Ð¶ÑÑÐœÐ°Ð» Tor Ñ ÑÐµÐºÑÑÐŸÐ²ÐžÐ¹ ÑÐ°Ð¹Ð» Ð°Ð±ÐŸ ÑÐœÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. ÐÐž ÐŒÐ°ÑÑÐµ Ð¿ÐŸÐ±Ð°ÑÐžÑÐž ÐŸÐŽÐœÑ Ð· ÑÐžÑ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ (ÑÑÐºÐ°Ð¹ÑÐµ ÐœÐ°ÑÑÑÐ¿ÐœÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor):</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â1: ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ð· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐŸÐŒ</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p> <p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS. Ð¯ÐºÑÐŸ ÐŽÐ»Ñ ÐœÐ°Ð»Ð°ÑÑÑÐ²Ð°ÐœÐœÑ ÐŒÐµÑÐµÐ¶Ñ Ð¿ÐŸÑÑÑÐ±ÐµÐœ Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑ SOCKS, Ð±ÑÐŽÑ Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž ÑÐœÑÐŸÑÐŒÐ°ÑÑÑ Ð¿ÑÐŸ Ð¿ÑÐŸÐºÑÑ. Ð¯ÐºÑÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS ÐœÐµ Ð¿ÐŸÑÑÑÐ±ÐœÐžÐ¹, Ð°Ð±ÐŸ Ð²Ðž ÐœÐµ Ð²Ð¿ÐµÐ²ÐœÐµÐœÑ, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÐŒÐµÑÐµÐ¶Ñ Tor Ð±ÐµÐ· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐ° SOCKS.<p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â2: ÐÐµ Ð²ÐŽÐ°ÑÑÑÑÑ Ð ŽÑÑÑÐ°ÑÐžÑÑ Ð±ÐµÐ·Ð¿ÐµÑÐœÐžÑ Ð¿ÐµÑÐµÐŽÐ°Ð²Ð°ÑÑÐ²</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð¶ÑÑÐœÐ°Ð»Ñ Tor Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž, ÑÐŸ ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°ÑÐŸÐŒÑ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÐµÑÑÐŸÐ³ÐŸ Ð²ÑÐ·Ð»Ð° Ð² Ð»Ð°ÐœÑÑÐ·Ñ Tor. ÐŠÐµ ÐŒÐŸÐ¶Ðµ ÐŸÐ·ÐœÐ°ÑÐ°ÑÐž, ÑÐŸ Ð²Ðž Ð¿ÐµÑÐµÐ±ÑÐ²Ð°ÑÑÐµ Ñ ÐŒÐµÑÐµÐ¶Ñ, ÑÐºÐ° Ð¿ÑÐŽÐŽÐ°ÑÑÑÑÑ ÑÐµÐœÐ·ÑÑÑ. ÐÑÐŽÑ Ð»Ð°ÑÐºÐ°, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽÐºÐ»ÑÑÐžÑÐžÑÑ ÐŽÐŸ ÐŒÐŸÑ ÑÑÐ², Ñ ÑÐµ ÐŒÐ°Ñ Ð²ÐžÑÑÑÐžÑÐž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ.</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â3: ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð·Ð°Ð²ÐµÑÑÐžÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð²ÐžÐºÐŸÐœÐ°ÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS Ð·Ð° ÐŽÐŸÐ¿ÐŸÐŒÐŸÐ³ÐŸÑ ÑÐ»ÑÐ¶Ð± ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ñ. ÐÐžÐºÐŸÑÐžÑÑÐ°ÐœÐœÑ ÐŒÐŸÑÑÑÐ², ÑÐ²ÐžÐŽÑÐµ Ð·Ð° Ð²ÑÐµ, Ð±ÑÐŽÐµ Ð²ÐžÐ¿ÑÐ°Ð²Ð»ÑÑÐž ÑÐµ.</p><h5> ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â4: Ð·Ð±ÐžÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°Ñ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÐœÐµÐ¿Ñ Ð°Ð²ÐžÐ»ÑÐœÐžÐ¹. ÐÑÐŽÑ-Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÐ¹ ÑÐŸÑÐœÐŸ, Ð²ÐºÐ»ÑÑÐœÐŸ Ð· Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐŒ ÑÐ°ÑÐŸÐ²ÐžÐŒ Ð¿ÐŸÑÑÐŸÐŒ. ÐÐŸÑÑÐŒ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÑÑÑ Tor.</p>" - }, - "connecting-3": { - "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-3", - "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-3", - "title": "Ð¯ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÐœÐ°Ð¹ÑÐž X.onion!", - "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð·ÐœÐ°Ð¹ÑÐž ÑÐ»ÑÐ¶Ð±Ñ onion, ÑÐºÑ Ð²Ðž Ð±Ð°Ð¶Ð°ÑÑÐµ, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž 16-ÑÐžÐŒÐ²ÐŸÐ»ÑÐœÑ onion-Ð°ÐŽÑÐµÑÑ: ÐœÐ°Ð²ÑÑÑ ÐœÐµÐ²ÐµÐ»ÐžÐºÐ° Ð¿ÐŸÐŒÐžÐ»ÐºÐ° ÐœÐµ ÐŽÐŸÐ·Ð²ÐŸÐ»ÐžÑÑ Tor Browser Ð·Ð°Ð¹ÑÐž ÐœÐ° ÑÐ°Ð¹Ñ. Ð¯ÐºÑÐŸ Ð²Ðž Ð²ÑÐµ Ð¶ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÑÐ»ÑÐ¶Ð± onion, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐ·ÐœÑÑÐµ. ÐÐŸÐ¶Ðµ ÑÑÐ°Ð¿ÐžÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° ÑÐžÐŒÑÐ°ÑÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑ, Ð°Ð±ÐŸ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐž ÑÐ°Ð¹ÑÑ ÐŒÐŸÐ¶ÑÑÑ ÐŽÐŸÐ·Ð²ÐŸÐ»ÐžÑÐž Ð¹ÐŸÐŒÑ Ð²ÐžÑÐŸÐŽÐžÑÐž Ð² Ð°Ð²ÑÐŸÐœÐŸÐŒÐœÐžÐ¹ ÑÐµÐ¶ÐžÐŒ Ð±ÐµÐ· Ð¿ÐŸÐ¿ÐµÑÐµÐŽÐ¶ÐµÐœÐœÑ.</p><p class=\"mb-3\">ÐÐž ÑÐ°ÐºÐŸÐ¶ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐºÐŸÐœÐ°ÑÐžÑÑ, ÑÐŸ Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐžÐŒÐ°ÑÐž ÐŽÐŸÑÑÑÐ¿ ÐŽÐŸ ÑÐœÑÐžÑ Ð¿ÐŸÑÐ»ÑÐ³ onion, Ð¿ÑÐŽ'ÑÐŽÐœÐ°Ð²ÑÐžÑÑ ÐŽÐŸ ÑÐ»ÑÐ¶Ð±Ðž Onion ÐœÐ° <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</ a>.</p>" - } -} diff --git a/zh_CN.json b/zh_CN.json deleted file mode 100644 index d2f692083..000000000 --- a/zh_CN.json +++ /dev/null @@ -1,20 +0,0 @@ -{ - "connecting-1": { - "id": "#è¿æ¥-1", - "control": "è¿æ¥-1", - "title": "Toræµè§åšæ²¡æè¿æ¥äžäºèçœïŒäœè¿äŒŒä¹å¹¶äžæ¯å äžºçœç»ç®¡æ§é æçé®é¢ã", - "description": "<p class=\"mb-3\">é æTorè¿æ¥å€±èŽ¥çæåžžè§çé®é¢ä¹äžæ¯ç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçç³»ç»æ¶éŽä»¥åæ¶åºè®Ÿçœ®æ£ç¡®ãåŠæè¿äžªé®é¢è¿æ²¡æè¢«è§£å³ïŒè¯·æ¥çäœäº<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Toræµè§åšæå</a></mark>çæéææ¥çé¢ã</p>" - }, - "connecting-2": { - "id": "#è¿æ¥-2", - "control": "è¿æ¥-2", - "title": "æ æ³è¿æ¥å° TorïŒæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", - "description": "<p class=\"mb-3\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥ </h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæ šçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§éè¯¯#3: TLSæ¡æå€±èŽ¥ </h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor äžäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿ çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5>åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯ <pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n ToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœã</code></pre></p><p class=\"mb-3\">è¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ãåŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" - }, - "connecting-3": { - "id": "#è¿æ¥-3", - "control": "è¿æ¥-3", - "title": "ææ æ³è®¿é®X.onionïŒ", - "description": "<p class=\"mb-3\">åŠææšæ æ³è®¿é®æŽè±ç«ç¹ïŒè¯·ç¡®è®€æšèŸå¥äºæ£ç¡®çïŒ16äœççœåïŒå³äœ¿äžäžªåŸ®å°çéè¯¯ä¹äŒé»æ¢Toræµè§åšè®¿é®è¿äžªç«ç¹ãåŠææšè¿æ¯æ æ³è®¿é®è¿äžªçœç«ïŒè¯·çšåéè¯ãè¿å¯èœæ¯ææ¶æ§çé®é¢ïŒæèçœç«ç®¡çåæªç»åºæ ç€ºå°±äžçº¿äºçœç«ã</p><p class=\"mb-3\">æšä¹å¯ä»¥éè¿è®¿é®<a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>çæŽè±ç«ç¹æ¥ç¡®è®€æšçæµè§åšéçœ®æ£ç¡®ã" - } -}

1 0

[translation/master] pulling translations from transifex
by translation＠torproject.org 06 Apr '18

06 Apr '18

commit 403e59d23a7292da1f75424e746b1a92fd70bb8f Author: Translation commit bot <translation(a)torproject.org> Date: Fri Apr 6 23:42:13 2018 +0000 pulling translations from transifex --- .tx/config | 9 +++++++++ de.json | 20 ++++++++++++++++++++ es.json | 20 ++++++++++++++++++++ fr.json | 20 ++++++++++++++++++++ ga.json | 20 ++++++++++++++++++++ id.json | 20 ++++++++++++++++++++ it.json | 20 ++++++++++++++++++++ ja.json | 20 ++++++++++++++++++++ ms_MY.json | 20 ++++++++++++++++++++ nl.json | 20 ++++++++++++++++++++ pt_BR.json | 20 ++++++++++++++++++++ ro.json | 20 ++++++++++++++++++++ support-connecting.json | 20 ++++++++++++++++++++ uk.json | 20 ++++++++++++++++++++ zh_CN.json | 20 ++++++++++++++++++++ 15 files changed, 289 insertions(+) diff --git a/.tx/config b/.tx/config new file mode 100644 index 000000000..819a1e2ae --- /dev/null +++ b/.tx/config @@ -0,0 +1,9 @@ +[torproject.support-connectingjson] +file_filter = <lang>.json +source_file = support-connecting.json +source_lang = en + +[main] +host = https://www.transifex.net + +minimum_perc = 100 diff --git a/de.json b/de.json new file mode 100644 index 000000000..05b1a5862 --- /dev/null +++ b/de.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "Tor-Browser kann sich nicht verbinden, aber es scheint nicht an Zensur-MaÃnahmen zu liegen.", + "description": "<p class=\"mb-3\">Eines der hÃ€ufigsten Probleme, die bei Tor-Browser Verbindungsprobleme verursacht, ist eine verstellte System-Uhr. Stelle daher sicher, dass deine System-Uhr und die Zeitzone richtig eingestellt ist. Wenn dies das Problem nicht behebt, besuche die Fehlerbehebungsseite in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor-Browser-Anleitung</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Ich habe Probleme mich mit Tor zu verbinden und kann die Ursache nicht finden.", + "description": "<p class=\"mb-3\">Wenn du Verbindungsprobleme hast, wÃ€hle bitte die Option \"Tor-Protokoll in die Zwischenablage kopieren\" aus. FÃŒge dann das Tor-Protokoll in eine Textdatei oder ein anderes Dokument ein. Du solltest nun einen der folgenden verbreiteten FehlereintrÃ€ge sehen (suche nach foldenden Zeilen in deinem Tor-Protokoll):</p><h5>Ãblicher Fehlereintrag #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung zu einem SOCKS-Proxy fehlschlÃ€gt. Wenn fÃŒr deine Netzwerkkonfiguration ein SOCKS-Proxy erforderlich ist, stelle sicher, dass du die erforderlichen Proxy-Daten korrekt eingegeben hast. Wenn kein SOCKS-Proxy benÃ¶tigt wird oder du diesbezÃŒglich nicht sicher bist, versuche ohne SOCKS-Proxy eine Verbindung zum Tor-Netzwerk herzustellen.<p><h5>Ãblicher Fehlereintrag #2: Kann WÃ€chter-Weiterleitung nicht erreichen</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/20 17 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung des Tor-Clients mit dem ersten Knoten im Tor-Circuit fehlschlÃ€gt. Dies kann bedeuten, dass du dich in einem zensierten Netzwerk befindest. Versuche dich mit BrÃŒcken zu verbinden, was das Problem beheben sollte.</p><h5>Ãblicher Fehlereintrag #3: Fehlschlag bei der VervollstÃ€ndigung des TLS-Handschlags</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass dein Tor-Client einen TLS-Handschlag mit den Verzeichnisinstanzen nicht erfolgreich abschlieÃen konnte. Die Verwendung von BrÃŒcken wird das wahrscheinlich beheben.</p><h5>Ãblicher Fehlereintrag #4: Taktversatz</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and d ate settings.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass deine System-Uhr verstellt ist. Bitte stelle sicher, dass deine System-Uhr und die entsprechende Zeitzone richtig gestellt sind. Starte Tor danach neu.</p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Ich kann X.onion nicht erreichen!", + "description": "<p class=\"mb-3\">Wenn du den gewÃŒnschten Onion-Dienst nicht erreichen kannst, stelle sicher, dass du die 16 Zeichen lange Onion-Adresse richtig eingegeben hast: Sogar ein kleiner Tippfehler verhindert, dass Tor-Browser die Website finden kann. Wenn du dich dann mit dem Onion-Dienst immer noch nicht verbinden kannst, versuche es spÃ€ter noch einmal. Es kann vorÃŒbergehende Verbindungsprobleme im Netz geben oder die Seitenbetreiber haben ohne Vorwarnung die Seite vom Netz genommen.</p><p class=\"mb-3\">Du kannst auch ÃŒberprÃŒfen, ob es dir grundsÃ€tzlich mÃ¶glich ist Onion-Dienste zu nutzen, in dem du dich mit <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>s Onion-Dienst verbindest.</p>" + } +} diff --git a/es.json b/es.json new file mode 100644 index 000000000..5f8938425 --- /dev/null +++ b/es.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "El Navegador Tor no conecta, pero no parece ser un problema con la censura.", + "description": "<p class=\"mb-3\">Uno de los problemas mÃ¡s habituales que causa errores de conexiÃ³n en el Navegador Tor es un reloj del sistema incorrectamente ajustado. Por favor, asegÃºrate de que el reloj de tu sistema y tu zona horaria estÃ¡n configurados correctamente. Si esto no soluciona tu problema, dirÃgete a la pÃ¡gina de SoluciÃ³n de Problemas en el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">manual del Navegador Tor</a></mark></p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Estoy teniendo problemas conectando a Tor, y no logro averiguar quÃ© es lo que estÃ¡ mal.", + "description": "Si tienes problemas para conectarte, por favor selecciona la opciÃ³n \"copiar el registro de Tor al portapapeles\". Luego pega el registro Tor en un archivo de texto u otro documento. DeberÃas ver uno de estos errores comunes de registro (busca las siguientes lÃneas en tu registro Tor): Error comÃºn de registro #1: Fallo de conexiÃ³n proxy 2017-10-29 09:23:40.800[NOTICE] Abriendo socks en 127.0.0.1:9150\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 10%: Finaliza hankshake con el servidor de directorios\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectar toxx.. xxx.. xxx. xx: xxxxxxx (\"fallo general del servidor SOCKS\") Si ves lÃneas como estas en tu registro Tor, significa que no te estÃ¡s conectando a un proxy SOCKS. Si se requiere un proxy SOCKS para la configuraciÃ³n de red, asegÃºrate de introducir correctamente los datos del proxy. Error de registro comÃºn #2: No se puede llegar a los relÃ©s de guardia 11/1/2017 21:11:43 PM. 500[AVISO] Abriendo el socks en 127.0.0.1:9150\n11/1/2017 21:11:44 PM. 300[AVISO] Bootstrapped 80%: ConexiÃ³n a la red Tor\n11/1/2017 21:11:44 PM. 300[ADVERTENCIA] No encontramos nodo para el salto 0 de nuestro camino. Descartar este circuito.\n11/1/2017 21:11:44 PM. 500[AVISO] Bootstrapped 85%: Acabando el handshake con el primer salto\n11/1/2017 21:11:11:45 PM. 300[ADVERTENCIA] No se ha encontrado nodo para el salto 0 de nuestra ruta. Descartando este circuito: si ves lÃneas como estas en tu registro Tor, significa que tu Tor no se conectÃ³ al primer nodo del circuito Tor. Esto podrÃa significar que estÃ¡s en una red ce nsurada. Error de registro comÃºn #3: No se pudo completar el handshake TLS 13-11-17 19:52:24:24.300[ATENCIÃN) Bootstrapped 10%: Finalizar handshake con el servidor de directorios\n13-11-17 19:53:49.300[ADVERTENCIA] Problema con el bootstrapping. Atascado al 10%: Acabando handshake con el servidor de directorios. (HECHO; HECHO; conteo 10; recomendaciÃ³n; host[host] en xxx. xxx. xxx. xxx. xx: xxx)\n13-11-17 19:53:49.300[ATENCIÃN] 10 conexiones han fallado:\n13-11-17 19:53:49.300[ADVERTENCIA] 9 conexiones caidas en estado handshaking (TLS) con estado SSL SSLv2/v3 lea servidor hola A en HANDSHAKE\n13-11-17 19:53:49.300[ADVERTENCIA] 1 conexiones muertas en estado connect()ing con estado SSL (sin objeto SSL) Si ves lÃneas como esta en tu registro de Tor, significa que Tor no pudo completar un handshake TLS con las competencias del directorio. Error de registro comÃºn #4: DesviaciÃ³n del reloj 19.11.2017 00:04:47.400[ATENCIÃN] IntÃ©rprete de socks de apertura en 127.0.0.0.1:9150\n19.1 1.2017 00:04:48.000[ADVERTENCIA] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n19.11.2017 00:04:48.200[ADVERTENCIA] Bootstrapped 10%: Finalizando el handshake con el servidor de directorios\n19.11.2017 00:04:48.800[ADVERTENCIA] Celda de NETINFO recibida con tiempo sesgado (OR: xxx. xx. xx. xx: xxxx): Parece que nuestro reloj estÃ¡ atrasado 1 dÃa, 0 horas, 1 minutos, o que el suyo estÃ¡ adelantado.\nTor requiere un reloj preciso para funcionar: por favor, comprueba tus ajustes de hora, zona horaria y fecha Si ves lÃneas como esta en tu registro Tor, significa que el reloj de tu sistema es incorrecto. AsegÃºrate de que tu reloj estÃ¡ ajustado correctamente, incluyendo la zona horaria. A continuaciÃ³n, reinicia Tor." + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Â¡No puedo conectar a X.onion!", + "description": "<p class=\"mb-3\">Si no puede alcanzar el servicio onion que desea, asegÃºrese de que ha introducido correctamente la direcciÃ³n onion de 16 caracteres: incluso un pequeÃ±o error evitarÃ¡ que el Navegador Tor logre alcanzar el sitio. Si aÃºn asÃ no puede conectar al servicio onion, por favor, intÃ©ntelo de nuevo mÃ¡s tarde. Puede haber un problema temporal con la conexiÃ³n, o los operadores del sitio pueden haberle permitido desconectar sin avisar.</p><p class=\"mb-3\">TambiÃ©n puede asegurarse de que es capaz de acceder a otros servicios onion conectando al servicio onion de <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/fr.json b/fr.json new file mode 100644 index 000000000..4ed10c84e --- /dev/null +++ b/fr.json @@ -0,0 +1,20 @@ +{ + "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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">âguide du navigateur Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connexion-2", + "control": "connexion-2", + "title": "JâÃ©prouve des difficultÃ©s Ã me connecter Ã Tor et je nâarrive pas Ã comprendre ce qui ne va pas.", + "description": "<p class=\"mb-3\">Si vous Ã©prouvez des difficultÃ©s Ã vous connecter, veuillez sÃ©lectionner lâoption Â«Â Copier le journal de Tor dans le presse-papiersÂ Â». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver lâune de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor)Â : </p><h5>Erreur habituelle de journal noÂ 1 : Ã©chec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter Ã un mandataire SOCKS. Si un mandataire SOCKS est nÃ©cessaire Ã la configuration de rÃ©seau, veuillez alors vous assurer dâavoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS nâest pas nÃ©cessaire ou si vous ne savez pas, veuillez tenter de vous connecter au rÃ©seau Tor sans mandataire SOCKS.<p><h5>Erreur habituelle de journal noÂ 2 : impossible dâatteindre les relais gardes</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/ 2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter au premier nÅud du circuit Tor. Cela pourrait signifier que vous Ãªtes sur un rÃ©seau qui est censurÃ©. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5>Erreur habituelle de journal noÂ 3 : Ã©chec dâÃ©tablissement dâune liaison TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19 :53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas rÃ©ussi Ã Ã©tablir une liaison TLS avec les autoritÃ©s d'annuaire. Lâutilisation de ponts corrigera certainement cette situation.</p><h5>Erreur habituelle de journal noÂ 4 : dÃ©calage dâhorloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or t hat theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">\nSi vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge systÃšme nâest pas juste. Veuillez vous assurer que votre horloge est rÃ©glÃ©e avec prÃ©cision, fuseau horaire inclus, puis redÃ©marrez Tor. </p>" + }, + "connecting-3": { + "id": "#connexion-3", + "control": "connexion-3", + "title": "Je ne peux pas accÃ©der Ã X.onionâ!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">Vous pouvez aussi vous assurer que vous arrivez Ã accÃ©der Ã dâautres services oignon en vous connectant au service oignon de <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>\n\n" + } +} diff --git a/ga.json b/ga.json new file mode 100644 index 000000000..26d45c2d5 --- /dev/null +++ b/ga.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "NÃ fÃ©idir le BrabhsÃ¡laÃ Tor ceangal a bhunÃº, cÃ© nach mbaineann an fhadhb le cÃºrsaÃ cinsireachta.", + "description": "<p class=\"mb-3\">Is minic go mbÃonn fadhb le clog an chÃ³rais ina chÃºis le hearrÃ¡idÃ i mBrabhsÃ¡laÃ Tor. Ba chÃ³ir duit deimhniÃº go bhfuil clog an chÃ³rais agus an crios ama socraithe mar is ceart. Mura rÃ©itÃonn seo an fhadhb, fÃ©ach an leathanach FabhtcheartÃº i <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">LÃ¡mhleabhar BhrabhsÃ¡laÃ Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "NÃ fÃ©idir liom ceangal le lÃonra Tor, agus nÃ thuigim cad Ã© an fhadhb.", + "description": "<p class=\"mb-3\">MÃ¡ tÃ¡ fadhb agat ag ceangal le lÃonra Tor, ÃºsÃ¡id an rogha âcÃ³ipeÃ¡il logchomhad Tor go dtÃ an ghearrthaisce.â Ansin, greamaigh an logchomhad i dtÃ©acschomhad nÃ³ cÃ¡ipÃ©is eile. Is dÃ³cha go bhfeicfidh tÃº ceann de na hearrÃ¡idÃ coitianta seo (cuardaigh na lÃnte seo a leanas sa logchomhad):</p><h5>EarrÃ¡id choitianta #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to co nnect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn siad gur theip ort ceangal a bhunÃº le seachfhreastalaÃ SOCKS. MÃ¡ theastaÃonn seachfhreastalaÃ SOCKS uait ar do lÃonra, deimhnigh gur chuir tÃº mionsonraÃ an fhreastalaÃ isteach go ceart. Mura dteastaÃonn seachfhreastalaÃ SOCKS uair, nÃ³ mura bhfuil tÃº cinnte, dÃ©an iarracht ceangal a bhunÃº le lÃonra Tor gan seachfhreastalaÃ SOCKS.<p><h5>EarrÃ¡id choitianta #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] F ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ort ceangal a bhunÃº leis an chÃ©ad nÃ³d sa gciorcad Tor. Uaireanta, ciallaÃonn seo go bhfuil do lÃonra faoi chinsireacht. Bain triail as ceangal trÃ dhroichead; is dÃ³cha go rÃ©iteoidh sin an fhadhb.</p><h5>EarrÃ¡id choitianta #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 co nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ar Tor croitheadh lÃ¡imhe TLS leis na hÃºdarÃ¡is a chur i gcrÃch. Is dÃ³cha go rÃ©iteoidh droichead an fhadhb seo.</p><h5>EarrÃ¡id choitianta #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, c iallaÃonn sÃ© go bhfuil an clog i do rÃomhaire mÃcheart. Ba chÃ³ir duit socruithe an chloig a dheimhniÃº, an t-am, dÃ¡ta, agus crios ama san Ã¡ireamh. Ansin, atosaigh Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "NÃlim in ann teacht ar X.onion!", + "description": "<p class=\"mb-3\">Mura bhfuil tÃº in ann seirbhÃs .onion a shroicheadh, deimhnigh gur chuir tÃº an seoladh 16-carachtar isteach go ceart: mÃ¡ tÃ¡ aon bhotÃºn ann, fiÃº botÃºn an-bheag, nÃ bheidh BrabhsÃ¡laÃ Tor in ann an suÃomh a shroicheadh. MÃ¡ tÃ¡ tÃº cinnte gur chuir tÃº an seoladh ceart isteach, bain triail eile as ar ball. Seans go bhfuil fadhb shealadach leis an lÃonra, nÃ³ b'fhÃ©idir gur bhain riarthÃ³irÃ an tsuÃmh as lÃne Ã© gan rabhadh.</p><p class=\"mb-3\">B'fhiÃº freisin fÃ©achaint an fÃ©idir leat dul i dteagmhÃ¡il le seirbhÃsÃ .onion eile, mar shampla <a href=\"http://3g2upl4pq6kufc4m.onion\">seirbhÃs DuckDuckGo</a>.</p>" + } +} diff --git a/id.json b/id.json new file mode 100644 index 000000000..0fdc118e3 --- /dev/null +++ b/id.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "Tor Browser tidak dapat tersambung, tapi ini tampaknya bukan akibat sensor oleh pihak lain.", + "description": "<p class=\"mb-3\">Salah satu masalah umum yang menyebabkan kegagalan koneksi di Tor Browser adalah jam sistem operasi yang tidak tepat. Silakan pastikan jam di sistem operasi dan zona waktu diatur dengan tepat di komputer Anda. Jika ini tidak memperbaiki masalah koneksi, lihat halaman Troubleshooting di <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", + "description": "<p class=\"mb-3\"> Jika Anda mendapat masalah dalam terhubung ke jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):\n\n</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS se rver failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.\n\n<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> Jika Anda melihat baris seperti ini, Tor gagal tersambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.\n\n</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.<h5>\n\nCommon log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. Tor memerlukan jam yang akurat supaya berfungsi dengan baik. Silakan periksa pengaturan waktu, zona waktu, dan tanggal. Pastikan jam di komputer Anda diatur dengan benar, termasuk zona waktu yang tepat. Lalu, restart Tor.\n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Tidak dapat terhubung ke X.onion!", + "description": "<p class=\"mb-3\">Jika Anda tidak dapat terhubung ke sebuah onion service yang diinginkan, pastikan Anda telah dengan tepat memasukkan 16-karakter alamat onion-nya. Bahkan kesalahan sedikit akan membuat Tor Browser tidak dapat terhubung ke situs yang dimaksud. Jika Anda tetap tidak dapat terhubung, silakan coba lagi nanti. Mungkin ada masalah sedikit di situsnya, atau operator situsnya sedang membuat situsnya menjadi offline tanpa pemberitahuan. </p><p class=\"mb-3\">Anda juga dapat memastikan jika Anda juga dapat terhubung ke situs onion service lain dengan mencoba terhubung ke <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>." + } +} diff --git a/it.json b/it.json new file mode 100644 index 000000000..7a04f1284 --- /dev/null +++ b/it.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connessione-1", + "control": "connessione-1", + "title": "Tor Browser non si connette, ma non sembra che sia dovuto alla censura.", + "description": "<p class=\"mb-3\">Uno dei problemi piÃ¹ comuni che causano errori di connessione in Tor Browser Ãš un orologio di sistema errato. Assicurati che l'orologio di sistema e il fuso orario siano impostati correttamente. Se ciÃ² non risolve il problema, consultare la pagina Risoluzione dei problemi su <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manuale di Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connessione-2", + "control": "connessione-2", + "title": "Sto avendo problemi nella connessione a Tor e non riesco a capire quale sia la causa.", + "description": "<p class=\"mb-3\">Se stai avendo problemi a connetterti, per favore seleziona l'opzione \"copia i log di Tor sulla clipboard.\" Poi incolla il log di Tor su un file di testo o un altro tipo di documento. Dovresti vedere uno di questi errori di log comuni (cerca per le seguenti linee nei log di Tor):</p><h5>Errore di log comune #1: Errore di connessione Proxy </h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150\n2017-10-29 09:23:47.900 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n2017-10-29 09:23:47.900 [AVVISO] Progressione 10%: Completando l'handshake con l'elenco dei server\n2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\nÂ 2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\n2017-10-29 09:24:08.900 [ATTENZIONE] Prox y Client: impossibile connettersi a xx..xxx..xxx.xx:xxxxx (\"errore generale server SOCKS\")</code></pre></p><p class=\"mb-3\">Se vedi delle linee come queste nei log di Tor, significa che la connessione a un proxy SOCKS sta fallendo.Se un proxy SOCKS Ãš richiesto per la tua configurazione di rete, controlla di aver inserito i dettagli del proxy correttamente.Se un proxy SOCKS non Ãš richiesto, o non ne sei sicuro, prova a connetterti alla rete Tor senza un proxy SOCKS.<p><h5>Errore di log comune #2: Non Ãš possibile raggiungere i guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150 \n11/1/2017 21:11:44 PM.300 [AVVISO] Progressione 80%: Connessione alla rete Tor\n11/1/2017 21:11:44 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.\n11/1/2017 21:11:44 PM.500 [AVVISO] Progressione 85%: Terminando l'handshake con il primo hop\nÂ 11/1/2017 21:11:45 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.</code></pre></p><p class=\"mb-3\">Se vedi delle linee come questo nel tuo log di Tor, significa che Tor ha fallito la connesione al primo nodo del circuito Tor. Questo potrebbe significare che ti trovi su una rete censurata. Per favore prova a connetterti con i bridge, e questo dovrebbe risolvere il problema.</p><h5>Errore di log comune #3: Errore nel completare l'handshake TLS</h5><p class=\"mb-3\"><pre><code>13-11-17 19:52:24.300 [AVVISO] Progressione 10%: Handshake con l'elenco dei server completato\n13-11-17 19:53:49.300 [ATTENZIONE] Problema durante la progressione. Fermo al 10%: Completando l'handshake con l'elenco dei server (FATTO; FATTO; contatore 10; avviso di raccomandazione; host [host] a xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [ATTENZIONE] 10 connessioni hanno fallito:\n13-11-17 19:53:49.300 [ATTENZIONE] 9 connessioni sono scadute durante lo stato di handshaking (TLS) con lo stato SSL di SSLv2/v3 r isposta server hello A in HANDSHAKE \n13-11-17 19:53:49.300 [ATTENZIONE] 1 connessione Ãš scaduta nello stato di connessione con stato SSL (Nessun oggetto SSL)</code></pre></p><p class=\"mb-3\">Se vedi delle linee cosÃ¬ nel tuo log Tor, significa che Tor ha fallito il completamento dell'handshake TLS con le autoritÃ dell'elenco. Usare i bridge risolverÃ probabilmente il problema.</p><h5>Errore log comune #4: Distorsione orario</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [AVVISO] Apertura ascoltatore porte SOCKS su 127.0.0.1:9150\n19.11.2017 00:04:48.000 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n19.11.2017 00:04:48.200 [AVVISO] Progressione 10%: Terminando l'handshake con l'elenco dei server\n19.11.2017 00:04:48.800 [ATTENZONE] Ricevuta cella NETINFO con orario distorto (O:xxx.xx.x.xx:xxxx): Sembra che il tuo orologio sia indietro di 1 giorno, 0 ore, 1 minuto, o che il loro sia avanti.\nTor richiede un orologio accurato per funzionare: per favore con trolla l'ora, la tua zona temporale e le impostazioni sulla data.</code></pre></p><p class=\"mb-3\">Se vedi queste linee nel tuo log di Tor, significa che l'ora del sistema Ãš incorretta. Per favore controlla che il tuo orologio sia impostato accuratamente, inclusa la zona temporale. DopodichÃ© riavvia Tor.</p>" + }, + "connecting-3": { + "id": "#connessione-3", + "control": "connessione-3", + "title": "Non posso raggiungere X.onion!", + "description": "<p class=\"mb-3\">Se non riesci a raggiungere il sito che desideri, assicurati di aver inserito correttamente l'indirizzo a 16 caratteri: anche un piccolo errore puÃ² impedire al Tor Browser di raggiungere il sito. Se non riesci ancora a connetterti al sito, riprova piÃ¹ tardi. Potrebbe esserci un problema di connessione temporaneo, oppure gli operatori del sito lo hanno lasciato andare offline senza lasciare preavviso.</p><p class=\"mb-3\">Puoi anche provare a connetterti a <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a> per vedere se riesci ad accedere ad altri siti.</p>" + } +} diff --git a/ja.json b/ja.json new file mode 100644 index 000000000..24309f341 --- /dev/null +++ b/ja.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#æ¥ç¶-1", + "control": "æ¥ç¶-1", + "title": "Torãã©ãŠã¶ãŒã¯æ¥ç¶ããŸããããæ€é²ã®åé¡ã§ã¯ãªãããã§ãã", + "description": "Torãã©ãŠã¶ãŒã§æ¥ç¶ãšã©ãŒãçºçããæãäžè¬çãªåé¡ã®1ã€ã¯ãäžæ£ãªã·ã¹ãã ã¯ããã¯ã§ããã·ã¹ãã ã®æèšãšã¿ã€ã ãŸãŒã³ãæ£ç¢ºã«èšå®ãããŠããããšãç¢ºèªããŠãã ãããããã§åé¡ãè§£æ±ºããªãå Žåã¯ãTorãã©ãŠã¶ãŒã®ããã¥ã¢ã«ã®ãã©ãã«ã·ã¥ãŒãã£ã³ã°ã®ããŒãžãåç§ããŠãã ããã" + }, + "connecting-2": { + "id": "#æ¥ç¶-2", + "control": "æ¥ç¶-2", + "title": "Torã«ã¢ã¯ã»ã¹ã§ããªãããäœãåé¡ãªã®ãåãããŸããã", + "description": "<p class=\"mb-3\">Torã«ã¢ã¯ã»ã¹ã§ããªãå ŽåããTorãã°ãã¯ãªããããŒãã«ã³ããŒãããéžæè¢ãéžãã§ããã°ãã¡ã¢åž³ãããã¯ããã¥ã¡ã³ããã¡ã€ã«ã«è²Œãä»ããŠäžãããä»¥äžã®è¯ããããšã©ãŒã¡ãã»ãŒãžãèŠã€ããã¯ãã§ãïŒ</p><h5>ãããããã°ãšã©ãŒ#1: ãããã·æ¥ç¶å€±æ</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx.. xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãSOCKSãããã·ãšç¹ãããªããšããããšã§ãããããã¯ãŒã¯ã«ã¯SOCKSãããã·ãå¿èŠãªããèšå®ãç¢ºèªããŠäžãããSOCKSãããã·ãå¿èŠã§ã¯ãªãå Žåããããã¯ããåãããªãå ŽåãSOCKSãããã·ç¡ãã§Torã«ã¢ã¯ã»ã¹ããŠã¿ãŠäžããã<p><h5>ãããããã°ãšã©ãŒ#2: ã¬ãŒããªã¬ãŒãšæ¥ç¶ã§ããªã</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discardi ng this circuit.</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorã¯circuitã®æåã®ããŒããšæ¥ç¶ã§ããªãã£ããšããããšã§ããæ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ããããŸããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããã¯ãã§ãã</p><h5>ãããããã°ãšã©ãŒ#3: TLSãã³ãã·ã§ã€ã¯ã®å€±æ</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorããã£ã¬ã¯ããªãªãŒãœãªãã£ãšTLSãã³ãã·ã§ã€ã¯ãå®äºã§ããªãã£ããšããããšã§ããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããå¯èœæ§ãããã</p><h5>ãããããã°ãšã©ãŒ#4: ã¯ããã¯ã¹ãã¥ãŒ</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p clas s=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãã·ã¹ãã ã»ã¯ããã¯ã«ã¯ééã£ãæå»ãèšå®ãããŸããã·ã¹ãã ã»ã¯ããã¯ãæ£ããæå»ãšã¿ã€ã ãŸãŒã³ã«åãããŠããTorãåèµ·åããŠäžããã </p>" + }, + "connecting-3": { + "id": "#æ¥ç¶-3", + "control": "æ¥ç¶-3", + "title": "X.onionãååŸã§ããŸããïŒ", + "description": "ããªããæããªããªã³ã®ãµãŒãã¹ã«ã¢ã¯ã»ã¹ã§ããªãå Žåã¯ã16æåã®ãªããªã³ã¢ãã¬ã¹ãæ£ããå¥åããããšãç¢ºèªããŠãã ãããå°ããªééãã§ããTorãã©ãŠã¶ãŒããµã€ãã«ã¢ã¯ã»ã¹ã§ããªããªããŸãã" + } +} diff --git a/ms_MY.json b/ms_MY.json new file mode 100644 index 000000000..94afcb73e --- /dev/null +++ b/ms_MY.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#menyambung-1", + "control": "menyambung-1", + "title": "Pelayar Tor tidak dapat bersambung, tetapi ia bukanlah isu berkenaan penapisan.", + "description": "<p class=\"mb-3\">Salah satu masalah utama yang menyebabkan ralat sambungan dalam Pelayar Tor ialah jam sistem yang salah. Sila pastikan jam sistem dan zon waktu anda telah ditetapkan dengan betul. Jika masalah ini masih berlaku, sila rujuk laman Pencarisilapan di dalam <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âpanduan Pelayar Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#menyambung-2", + "control": "menyambung-2", + "title": "Saya menghadapi masalah ketika menyambung dengan Tor, dan saya tidak tahu apa masalah yang berlaku.", + "description": "<p class=\"mb-3\">Jika anda menghadapi masalah sambungan, pilih pilihan \"salin log Tor ke papan keratan.â Kemudian tampal log Tor ke dalam fail teks atau lain-lain fail dokumen. Anda akan dapati terdapat ralat log (lihat baris berikut di dalam log Tor anda):</p><h5>Ralat log umum #1: Kegagalan sambungan proksi</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\" )</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud anda gagal menyambung dengan proksi SOCKS. Jika proksi SOCKS diperlukan untuk persediaan rangkaian anda, maka sila pastikan anda telah memasukkan perincian proksi tersebut dengan betul. Jika proksi SOCKS tidak diperlukan, atau anda tidak pasti, cuba sambung ke rangkaian Tor tanpa proksi SOCKS.<p><h5>Ralat log umum #2: Tidak dapat capai geganti pengawal</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb- 3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud Tor anda gagal menyambung ke nod pertama dalam litar Tor. Ia bermaksud anda berada dalam rangkaian bertapis. Cuba menyambung dengan titi, dan sepatutnya ia masalah selesai.</p><h5>Ralat log umum #3: Gagal menyelesaikan jabat-tangan TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat ba ris seperti ini di dalam log Tor anda, ia bermaksud Tor gagal menyelesaikan jabat-tangan TLS dengan autoriti direktori. Penggunaan titi dapat menyelesaikan masalah ini.</p><h5>Ralat log umum #4: Pencong jam</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini dalam log Tor anda, ia bermaksud jam sistem anda salah. Sila pastikan jam anda telah ditetapkan dengan tepat, termasuklah zon waktu yang betul. Kemudian mulakan semula Tor. </p>" + }, + "connecting-3": { + "id": "#menyambung-3", + "control": "menyambung-3", + "title": "Saya tidak dapat mencapai X.onion!", + "description": "<p class=\"mb-3\">Jika anda masih tidak dapat mencapai servis onion yang dikehendaki, pastikan anda telah memasukkan alamat onion 16-aksara dengan betul: walaupun dengan kesilapan kecil akan menghentikan Pelayar Tor mencapai laman. Jika anda masih tidak dapat menyambung ke servis onion, cuba sekali lagi. Kadangkala ia merupakan masalah sambungan sementara, atau operator laman telah menjadi luar talian tanpa apa-apa amaran.</p><p class=\"mb-3\">Anda juga perlu pastikan dapat mencapai servis onion lain dengan menyambung ke Servis Onion <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/nl.json b/nl.json new file mode 100644 index 000000000..4fdd4e365 --- /dev/null +++ b/nl.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#verbinden-1", + "control": "verbinden-1", + "title": "Tor Browser maakt geen verbinding, maar het lijkt geen probleem te zijn met censuur.", + "description": "<p class=\"mb-3\">Een van de meest voorkomende problemen die verbindingsfouten in Tor Browser veroorzaken, is een onjuiste systeemklok. Zorg ervoor dat uw systeemklok en tijdzone nauwkeurig zijn ingesteld. Als dit het probleem niet oplost, zie de pagina Problemen oplossen op de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser manual</a></mark>.</p>" + }, + "connecting-2": { + "id": "#verbinden-2", + "control": "verbinden-2", + "title": "Ik ondervind problemen bij het verbinding maken met Tor, en ik vind maar niet wat er fout gaat.", + "description": "<p class=\"mb-3\">Als u problemen ondervindt bij het verbinden, selecteert u de optie om \"Tor log naar klembord te kopiÃ«ren\". Plak vervolgens het Tor-log in een tekstbestand of een ander document. U zou een van deze Vaak voorkomend logfouten moeten zien (kijk naar de volgende regels in uw Tor-logboek): </p><h5>Vaak voorkomend logboekfout # 1: Proxy-verbindingsfout</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09: 23: 40.800 [LET OP] Opening Socks luisteraar op 127.0.0.1 : 9150 \n 2017-10-29 09: 23: 47.900 [LET OP] Bootstrapped 5%: verbinden met directoryserver \n 2017-10-29 09: 23: 47.900 [LETICE] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-clie nt: kan toxx..xxx..xxx.xx: xxxxx niet verbinden (\"algemene SOCKS-serverstoring\") </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, is dit betekent dat u geen verbinding kunt maken met een SOCKS-proxy. Als een SOCKS-proxy vereist is voor uw netwerkconfiguratie, moet u ervoor zorgen dat u uw proxy-gegevens correct hebt ingevoerd. Als een SOCKS-proxy niet vereist is, of als u het niet zeker weet, probeer dan verbinding te maken met het Tor-netwerk zonder een SOCKS-proxy.<p><h5>Gebruikslog fout # 2: Kan relais niet bereiken</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM .500 [LET OP] Luisteraar luisterpositie openen op 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [LET OP] Bootstrapped 80%: Verbinding maken met het Tor-netwerk \n 11/1/2017 21:11:44 PM.300 [WARN] Kan knooppunt voor hop 0 van ons pad niet vinden. Dit circuit weggooien. \n 11/1/2017 21:11:44 PM.500 [LET OP] Bootstrap 85%: Handshake beÃ«indigen met eerste hop \n 11/1/2017 21:11:45 P M.300 [WARN] Kan knooppunt niet vinden voor hop 0 van ons pad. Dit circuit verwijderen.</code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dit dat uw Tor geen verbinding kon maken met het eerste knooppunt in het Tor-circuit. Dit kan betekenen dat u zich op een netwerk bevindt dat gecensureerd is. Probeer te verbinden met bruggen, en dat zou het probleem moeten verhelpen.</p><h5> Algemene logfout # 3: Kan TLS-handshake niet voltooien</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 13-11-17 19: 53: 49.300 [WARN] Probleem met bootstrappen. Vastgelopen met 10%: handshake beÃ«indigen met directoryserver. (GEDAAN, GEDAAN, aantal 10; advieswaarschuwing; host [host] op xxx.xxx.xxx.xx: xxx) \n 13-11-17 19: 53: 49.300 [WARN] 10 verbindingen zijn mislukt: \n 13-11-17 19: 53: 49.300 [WARN] 9 verbindingen stierven in staatshandshaking (TLS) met SSL-status SSLv2 / v3 lezen server hallo A in HANDSHAKE \n 13-11-17 19: 53: 49.300 [WARN] 1 verbindingen zijn overleden in state connect () ing met SSL-staat (No SSL-object) </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dat Tor een TLS-handshake niet kon voltooien met de directory-autoriteiten. Het gebruik van bruggen lost dit waarschijnlijk op.</p><h5>Veel logboekfout # 4: Klok skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00: 04: 47.400 [LET OP] Opening Socks luisteraar op 127.0.0.1:9150 \n 19.11.2017 00: 04: 48.000 [LET OP] Bootstrap 5%: verbinding maken met directoryserver \n 19.11.2017 00: 04: 48.200 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 19.11.2017 00: 04: 48.800 [WARN] NETINFO-cel ontvangen met scheve tijd (OF: xxx.xx.x.xx: xxxx): het lijkt erop dat onze klok 1 dag, 0 uur, 1 minuut achterloopt, of die van hen liggen voor de deur. \n Tor vereist een nauwkeurige klok om te werken: controleer uw tijd-, tijdzone- en datuminstellin gen.</code></pre></p><p class=\"mb-3\">Als u lijnen zoals deze in uw Tor-logboek ziet, betekent dit dat uw systeemklok onjuist is. Zorg ervoor dat uw klok correct is ingesteld, inclusief de juiste tijdzone. Start dan Tor opnieuw. </p>" + }, + "connecting-3": { + "id": "#verbinden-3", + "control": "verbinden-3", + "title": "Ik kan X.onion niet bereiken!", + "description": "<p class=\"mb-3\">Als u de gewenste onion service niet kunt bereiken, moet u ervoor zorgen dat u het onion adres van 16 tekens correct hebt ingevoerd: zelfs een kleine fout zal ervoor zorgen dat Tor Browser de site niet kan bereiken. Als u nog steeds geen verbinding kunt maken met de onion service, probeert u het later opnieuw. Er kan een tijdelijke verbinding probleem zijn, of de site exploitanten kunnen hebben toegestaan dat het offline gaan zonder waarschuwing.</p><p class=\"mb-3\"> U kunt er ook voor zorgen dat u in staat om toegang te krijgen tot andere diensten ui door verbinding te maken <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s Onion Service.</p>" + } +} diff --git a/pt_BR.json b/pt_BR.json new file mode 100644 index 000000000..a1bf886e7 --- /dev/null +++ b/pt_BR.json @@ -0,0 +1,20 @@ +{ + "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.", + "description": "<p class=\"mb-3\">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</a></mark>.</p>" + }, + "connecting-2": { + "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": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opÃ§Ã£o para \"copiar o log de Tor para a Ã¡rea de transferÃªncias\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. VocÃª deverÃ¡ ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexÃ£o de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretÃ³rio\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretÃ³rio\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0 8.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se vocÃª encontrar linhas como estas em seu log do Tor, isto significa que falhou em conectar-se Ã um SOCKS proxy. Se um SOCKS proxy Ã© obrigatÃ³rio para a sua configuraÃ§Ã£o de rede, por favor certifique-se que vocÃª digitou seus detalhes de proxy corretamente. Se um SOCKS proxy nÃ£o Ã© obrigatÃ³rio, ou vocÃª nÃ£o estÃ¡ certo sobre isso, por favor tente conectar-se Ã rede Tor sem um 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\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.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\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hand shake 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\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor 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": "#conectando-3", + "control": "conectando-3", + "title": "NÃ£o consigo conectar ao X.onion!", + "description": "<p class=\"mb-3\">Se vocÃª nÃ£o conseguir acessar o serviÃ§o onion desejado, certifique-se de ter digitado o endereÃ§o onion com 16 caracteres corretamente: atÃ© mesmo um pequeno erro impedirÃ¡ que o Navegador Tor alcance o site. Se vocÃª ainda nÃ£o conseguir se conectar ao serviÃ§o onion, tente novamente mais tarde. Pode haver um problema de conexÃ£o temporÃ¡ria ou os operadores do site podem ter permitido que ele fique offline sem aviso prÃ©vio.</p><p class=\"mb-3\"> VocÃª tambÃ©m pode garantir que poderÃ¡ acessar outros serviÃ§os onion conectando-se ao <a href=\"http://3g2upl4pq6kufc4m.onion\">ServiÃ§o Onion</a>do DuckDuckGo.</p>" + } +} diff --git a/ro.json b/ro.json new file mode 100644 index 000000000..2fe13067e --- /dev/null +++ b/ro.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "conectare-1", + "title": "Tor Browser nu se conecteazÄ, dar nu pare a fi o problemÄ de cenzurÄ.", + "description": "<p class=\"mb-3\">Una din cele mai frecvente cauze pentru problemele de conectare ale Tor Browser este ora sistemului incorectÄ. VerificÄ dacÄ ora Èi fusul orar sunt setate corect. DacÄ aceasta nu rezolvÄ problema, urmeazÄ indicaÈiile de Depanare din <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âmanualul Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "conectare-2", + "title": "Am dificultÄÈi Ã®n conectarea la Tor Èi nu Ã®nÈeleg ce e greÈit.", + "description": "<p class=\"mb-3\">DacÄ ai probleme de conectare, selecteazÄ opÈiunea \"copiazÄ log-ul Tor Ã®n clipboard\". Apoi lipeÈte log-ul astfel copiat Ã®ntr-un fiÈier text sau alt document. Ar trebui sÄ vezi unul dintre aceste mesaje de eroare comune (cautÄ astfel de linii Ã®n log-ul Tor):</p><h5>Eroare comunÄ #1: Eroare de conectare la proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-ul Tor, Ã®nseamnÄ cÄ nu te poÈi conecta la un proxy SOCKS. DacÄ un proxy SOCKS este necesar pentru reÈeaua pe care o foloseÈti, atunci asigurÄ-te cÄ ai introdus setÄrile de proxy corecte. DacÄ un proxy SOCKS nu e necesar sau nu eÈti sigur, Ã®ncearcÄ sÄ te conectezi la reÈeaua Tor fÄrÄ un proxy SOCKS.<p><h5>Eroare comunÄ #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\" >DacÄ vezi astfel de linii in log-ul Tor Ã®nseamnÄ ca nu s-a reuÈit conectarea la primul nod din circuitul Tor. Aceasta ar putea Ã®nsemna cÄ te afli Ã®ntr-o reÈea cenzuratÄ. ÃncearcÄ conectarea prin punÈi, care ar trebui sÄ rezolve problema.</p><h5>Eroare comunÄ #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-u l Tor Ã®nseamnÄ cÄ nu s-a realizat o conexiune completÄ TLS cu serverele de directoare. Folosirea punÈilor va rezolva probabil acest lucru. </p><h5>Eroare comunÄ #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-ul Tor Ã®nseamnÄ cÄ ceasul sistemului tÄu e incorect. AsigurÄ-te cÄ ceasul sistemului este corect, inclusiv fusul orar, apoi reporneÈte Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "conectare-3", + "title": "Nu pot ajunge la X.onion!", + "description": "<p class=\"mb-3\">DacÄ nu poÈi ajunge la serviciul onion dorit, asigurÄ-te cÄ ai introdus cele 16 caractere din adresa onion corect - chiar Èi cea mai micÄ eroare va Ã®mpiedica Tor Browser sÄ ajungÄ la site. DacÄ tot nu poÈi ajunge la serviciul onion, Ã®ncearcÄ mai tÃ¢rziu. E posibil sÄ fie o problemÄ temporarÄ de conexiune sau operatorii site-ului l-au deconectat fÄrÄ avertizare. </p><p class=\"mb-3\">PoÈi sÄ te asiguri cÄ alte servicii onion sunt accesibile conectÃ¢ndu-te la serviciul onion al <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/support-connecting.json b/support-connecting.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/support-connecting.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/uk.json b/uk.json new file mode 100644 index 000000000..32a35f4fc --- /dev/null +++ b/uk.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-1", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-1", + "title": "ÐÑÐ°ÑÐ·ÐµÑ Tor ÐœÐµ Ð±ÑÐŽÐµ Ð¿ÑÐŽ'ÑÐŽÐœÑÐ²Ð°ÑÐžÑÑ, Ð°Ð»Ðµ ÑÐµ, Ð·ÐŽÐ°ÑÑÑÑÑ, ÐœÐµ Ñ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐŸÑ Ð· ÑÐµÐœÐ·ÑÑÐŸÑ.", + "description": "<p class=\"mb-3\">ÐÐŽÐœÑÑÑ Ð· ÐœÐ°Ð¹Ð±ÑÐ»ÑÑ Ð¿ÐŸÑÐžÑÐµÐœÐžÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ, ÑÐŸ Ð¿ÑÐžÐ·Ð²ÐŸÐŽÑÑÑ ÐŽÐŸ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ñ Ð±ÑÐ°ÑÐ·ÐµÑÑ Tor, Ñ ÐœÐµÐ¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐ¹ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº. ÐÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÑ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÑÐ° ÑÐ°ÑÐŸÐ²ÐžÐ¹ Ð¿ÐŸÑÑ Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÑÐŸÑÐœÐŸ. Ð¯ÐºÑÐŸ ÑÐµ ÐœÐµ Ð²ÐžÑÑÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ, Ð¿ÐµÑÐµÐ³Ð»ÑÐœÑÑÐµ ÑÑÐŸÑÑÐœÐºÑ ÑÑÑÐœÐµÐœÐœÑ ÐœÐµÐ¿ÐŸÐ»Ð°ÐŽÐŸÐº Ñ <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Ð¿ÐŸÑÑÐ±ÐœÐžÐºÑ ÐºÐŸÑÐžÑÑÑÐ²Ð°ÑÐ° Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-2", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-2", + "title": "Ð£ ÐŒÐµÐœÐµ Ð²ÐžÐœÐžÐºÐ»Ð° Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ ÐŽÐŸ Tor, Ñ Ñ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÑÐŸÐ·ÑÐŒÑÑÐž, ÑÐŸ ÐœÐµ ÑÐ°Ðº.", + "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð²Ð°Ñ Ð²ÐžÐœÐžÐºÐ»Ðž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐž Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ, Ð²ÐžÐ±ÐµÑÑÑÑ ÐŸÐ¿ÑÑÑ Â«ÐºÐŸÐ¿ÑÑÐ²Ð°ÑÐž Ð¶ÑÑÐœÐ°Ð» Tor Ñ Ð±ÑÑÐµÑ ÐŸÐ±ÐŒÑÐœÑÂ». ÐÐŸÑÑÐŒ Ð²ÑÑÐ°Ð²ÑÐµ Ð¶ÑÑÐœÐ°Ð» Tor Ñ ÑÐµÐºÑÑÐŸÐ²ÐžÐ¹ ÑÐ°Ð¹Ð» Ð°Ð±ÐŸ ÑÐœÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. ÐÐž ÐŒÐ°ÑÑÐµ Ð¿ÐŸÐ±Ð°ÑÐžÑÐž ÐŸÐŽÐœÑ Ð· ÑÐžÑ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ (ÑÑÐºÐ°Ð¹ÑÐµ ÐœÐ°ÑÑÑÐ¿ÐœÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor):</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â1: ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ð· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐŸÐŒ</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p> <p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS. Ð¯ÐºÑÐŸ ÐŽÐ»Ñ ÐœÐ°Ð»Ð°ÑÑÑÐ²Ð°ÐœÐœÑ ÐŒÐµÑÐµÐ¶Ñ Ð¿ÐŸÑÑÑÐ±ÐµÐœ Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑ SOCKS, Ð±ÑÐŽÑ Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž ÑÐœÑÐŸÑÐŒÐ°ÑÑÑ Ð¿ÑÐŸ Ð¿ÑÐŸÐºÑÑ. Ð¯ÐºÑÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS ÐœÐµ Ð¿ÐŸÑÑÑÐ±ÐœÐžÐ¹, Ð°Ð±ÐŸ Ð²Ðž ÐœÐµ Ð²Ð¿ÐµÐ²ÐœÐµÐœÑ, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÐŒÐµÑÐµÐ¶Ñ Tor Ð±ÐµÐ· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐ° SOCKS.<p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â2: ÐÐµ Ð²ÐŽÐ°ÑÑÑÑÑ Ð ŽÑÑÑÐ°ÑÐžÑÑ Ð±ÐµÐ·Ð¿ÐµÑÐœÐžÑ Ð¿ÐµÑÐµÐŽÐ°Ð²Ð°ÑÑÐ²</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð¶ÑÑÐœÐ°Ð»Ñ Tor Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž, ÑÐŸ ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°ÑÐŸÐŒÑ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÐµÑÑÐŸÐ³ÐŸ Ð²ÑÐ·Ð»Ð° Ð² Ð»Ð°ÐœÑÑÐ·Ñ Tor. ÐŠÐµ ÐŒÐŸÐ¶Ðµ ÐŸÐ·ÐœÐ°ÑÐ°ÑÐž, ÑÐŸ Ð²Ðž Ð¿ÐµÑÐµÐ±ÑÐ²Ð°ÑÑÐµ Ñ ÐŒÐµÑÐµÐ¶Ñ, ÑÐºÐ° Ð¿ÑÐŽÐŽÐ°ÑÑÑÑÑ ÑÐµÐœÐ·ÑÑÑ. ÐÑÐŽÑ Ð»Ð°ÑÐºÐ°, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽÐºÐ»ÑÑÐžÑÐžÑÑ ÐŽÐŸ ÐŒÐŸÑ ÑÑÐ², Ñ ÑÐµ ÐŒÐ°Ñ Ð²ÐžÑÑÑÐžÑÐž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ.</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â3: ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð·Ð°Ð²ÐµÑÑÐžÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð²ÐžÐºÐŸÐœÐ°ÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS Ð·Ð° ÐŽÐŸÐ¿ÐŸÐŒÐŸÐ³ÐŸÑ ÑÐ»ÑÐ¶Ð± ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ñ. ÐÐžÐºÐŸÑÐžÑÑÐ°ÐœÐœÑ ÐŒÐŸÑÑÑÐ², ÑÐ²ÐžÐŽÑÐµ Ð·Ð° Ð²ÑÐµ, Ð±ÑÐŽÐµ Ð²ÐžÐ¿ÑÐ°Ð²Ð»ÑÑÐž ÑÐµ.</p><h5> ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â4: Ð·Ð±ÐžÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°Ñ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÐœÐµÐ¿Ñ Ð°Ð²ÐžÐ»ÑÐœÐžÐ¹. ÐÑÐŽÑ-Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÐ¹ ÑÐŸÑÐœÐŸ, Ð²ÐºÐ»ÑÑÐœÐŸ Ð· Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐŒ ÑÐ°ÑÐŸÐ²ÐžÐŒ Ð¿ÐŸÑÑÐŸÐŒ. ÐÐŸÑÑÐŒ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÑÑÑ Tor.</p>" + }, + "connecting-3": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-3", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-3", + "title": "Ð¯ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÐœÐ°Ð¹ÑÐž X.onion!", + "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð·ÐœÐ°Ð¹ÑÐž ÑÐ»ÑÐ¶Ð±Ñ onion, ÑÐºÑ Ð²Ðž Ð±Ð°Ð¶Ð°ÑÑÐµ, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž 16-ÑÐžÐŒÐ²ÐŸÐ»ÑÐœÑ onion-Ð°ÐŽÑÐµÑÑ: ÐœÐ°Ð²ÑÑÑ ÐœÐµÐ²ÐµÐ»ÐžÐºÐ° Ð¿ÐŸÐŒÐžÐ»ÐºÐ° ÐœÐµ ÐŽÐŸÐ·Ð²ÐŸÐ»ÐžÑÑ Tor Browser Ð·Ð°Ð¹ÑÐž ÐœÐ° ÑÐ°Ð¹Ñ. Ð¯ÐºÑÐŸ Ð²Ðž Ð²ÑÐµ Ð¶ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÑÐ»ÑÐ¶Ð± onion, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐ·ÐœÑÑÐµ. ÐÐŸÐ¶Ðµ ÑÑÐ°Ð¿ÐžÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° ÑÐžÐŒÑÐ°ÑÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑ, Ð°Ð±ÐŸ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐž ÑÐ°Ð¹ÑÑ ÐŒÐŸÐ¶ÑÑÑ ÐŽÐŸÐ·Ð²ÐŸÐ»ÐžÑÐž Ð¹ÐŸÐŒÑ Ð²ÐžÑÐŸÐŽÐžÑÐž Ð² Ð°Ð²ÑÐŸÐœÐŸÐŒÐœÐžÐ¹ ÑÐµÐ¶ÐžÐŒ Ð±ÐµÐ· Ð¿ÐŸÐ¿ÐµÑÐµÐŽÐ¶ÐµÐœÐœÑ.</p><p class=\"mb-3\">ÐÐž ÑÐ°ÐºÐŸÐ¶ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐºÐŸÐœÐ°ÑÐžÑÑ, ÑÐŸ Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐžÐŒÐ°ÑÐž ÐŽÐŸÑÑÑÐ¿ ÐŽÐŸ ÑÐœÑÐžÑ Ð¿ÐŸÑÐ»ÑÐ³ onion, Ð¿ÑÐŽ'ÑÐŽÐœÐ°Ð²ÑÐžÑÑ ÐŽÐŸ ÑÐ»ÑÐ¶Ð±Ðž Onion ÐœÐ° <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</ a>.</p>" + } +} diff --git a/zh_CN.json b/zh_CN.json new file mode 100644 index 000000000..d2f692083 --- /dev/null +++ b/zh_CN.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#è¿æ¥-1", + "control": "è¿æ¥-1", + "title": "Toræµè§åšæ²¡æè¿æ¥äžäºèçœïŒäœè¿äŒŒä¹å¹¶äžæ¯å äžºçœç»ç®¡æ§é æçé®é¢ã", + "description": "<p class=\"mb-3\">é æTorè¿æ¥å€±èŽ¥çæåžžè§çé®é¢ä¹äžæ¯ç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçç³»ç»æ¶éŽä»¥åæ¶åºè®Ÿçœ®æ£ç¡®ãåŠæè¿äžªé®é¢è¿æ²¡æè¢«è§£å³ïŒè¯·æ¥çäœäº<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Toræµè§åšæå</a></mark>çæéææ¥çé¢ã</p>" + }, + "connecting-2": { + "id": "#è¿æ¥-2", + "control": "è¿æ¥-2", + "title": "æ æ³è¿æ¥å° TorïŒæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", + "description": "<p class=\"mb-3\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥ </h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæ šçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§éè¯¯#3: TLSæ¡æå€±èŽ¥ </h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor äžäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿ çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5>åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯ <pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n ToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœã</code></pre></p><p class=\"mb-3\">è¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ãåŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" + }, + "connecting-3": { + "id": "#è¿æ¥-3", + "control": "è¿æ¥-3", + "title": "ææ æ³è®¿é®X.onionïŒ", + "description": "<p class=\"mb-3\">åŠææšæ æ³è®¿é®æŽè±ç«ç¹ïŒè¯·ç¡®è®€æšèŸå¥äºæ£ç¡®çïŒ16äœççœåïŒå³äœ¿äžäžªåŸ®å°çéè¯¯ä¹äŒé»æ¢Toræµè§åšè®¿é®è¿äžªç«ç¹ãåŠææšè¿æ¯æ æ³è®¿é®è¿äžªçœç«ïŒè¯·çšåéè¯ãè¿å¯èœæ¯ææ¶æ§çé®é¢ïŒæèçœç«ç®¡çåæªç»åºæ ç€ºå°±äžçº¿äºçœç«ã</p><p class=\"mb-3\">æšä¹å¯ä»¥éè¿è®¿é®<a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>çæŽè±ç«ç¹æ¥ç¡®è®€æšçæµè§åšéçœ®æ£ç¡®ã" + } +}

1 0

[translation/support-connecting] pulling translations from transifex
by translation＠torproject.org 06 Apr '18

06 Apr '18

commit 1fbf3983514632b46033c84e754634c3797cf149 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Apr 6 23:40:41 2018 +0000 pulling translations from transifex --- ach.json | 20 ++++++++++++++++++++ ady.json | 20 ++++++++++++++++++++ af.json | 20 ++++++++++++++++++++ ak.json | 20 ++++++++++++++++++++ am.json | 20 ++++++++++++++++++++ ar.json | 20 ++++++++++++++++++++ arn.json | 20 ++++++++++++++++++++ ast.json | 20 ++++++++++++++++++++ az.json | 20 ++++++++++++++++++++ ba.json | 20 ++++++++++++++++++++ be.json | 20 ++++++++++++++++++++ bg.json | 20 ++++++++++++++++++++ bn.json | 20 ++++++++++++++++++++ bn_BD.json | 20 ++++++++++++++++++++ bn_IN.json | 20 ++++++++++++++++++++ bo.json | 20 ++++++++++++++++++++ br.json | 20 ++++++++++++++++++++ brx.json | 20 ++++++++++++++++++++ bs.json | 20 ++++++++++++++++++++ ca.json | 20 ++++++++++++++++++++ ceb.json | 20 ++++++++++++++++++++ cs.json | 20 ++++++++++++++++++++ csb.json | 20 ++++++++++++++++++++ cv.json | 20 ++++++++++++++++++++ cy.json | 20 ++++++++++++++++++++ da.json | 20 ++++++++++++++++++++ de.json | 20 ++++++++++++++++++++ dz.json | 20 ++++++++++++++++++++ el.json | 20 ++++++++++++++++++++ en_GB.json | 20 ++++++++++++++++++++ eo.json | 20 ++++++++++++++++++++ es.json | 20 ++++++++++++++++++++ es_AR.json | 20 ++++++++++++++++++++ es_CL.json | 20 ++++++++++++++++++++ es_CO.json | 20 ++++++++++++++++++++ es_MX.json | 20 ++++++++++++++++++++ et.json | 20 ++++++++++++++++++++ eu.json | 20 ++++++++++++++++++++ fa.json | 20 ++++++++++++++++++++ fi.json | 20 ++++++++++++++++++++ fil.json | 20 ++++++++++++++++++++ fo.json | 20 ++++++++++++++++++++ fr.json | 20 ++++++++++++++++++++ fr_CA.json | 20 ++++++++++++++++++++ fur.json | 20 ++++++++++++++++++++ fy.json | 20 ++++++++++++++++++++ ga.json | 20 ++++++++++++++++++++ gd.json | 20 ++++++++++++++++++++ gl.json | 20 ++++++++++++++++++++ gu.json | 20 ++++++++++++++++++++ gu_IN.json | 20 ++++++++++++++++++++ gun.json | 20 ++++++++++++++++++++ ha.json | 20 ++++++++++++++++++++ he.json | 20 ++++++++++++++++++++ hi.json | 20 ++++++++++++++++++++ hr.json | 20 ++++++++++++++++++++ hr_HR.json | 20 ++++++++++++++++++++ ht.json | 20 ++++++++++++++++++++ hu.json | 20 ++++++++++++++++++++ hy.json | 20 ++++++++++++++++++++ ia.json | 20 ++++++++++++++++++++ id.json | 20 ++++++++++++++++++++ is.json | 20 ++++++++++++++++++++ it.json | 20 ++++++++++++++++++++ ja.json | 20 ++++++++++++++++++++ jv.json | 20 ++++++++++++++++++++ ka.json | 20 ++++++++++++++++++++ kk.json | 20 ++++++++++++++++++++ km.json | 20 ++++++++++++++++++++ kn.json | 20 ++++++++++++++++++++ ko.json | 20 ++++++++++++++++++++ ko_KR.json | 20 ++++++++++++++++++++ ku.json | 20 ++++++++++++++++++++ ku_IQ.json | 20 ++++++++++++++++++++ kw.json | 20 ++++++++++++++++++++ ky.json | 20 ++++++++++++++++++++ la.json | 20 ++++++++++++++++++++ lb.json | 20 ++++++++++++++++++++ lg.json | 20 ++++++++++++++++++++ ln.json | 20 ++++++++++++++++++++ lo.json | 20 ++++++++++++++++++++ lt.json | 20 ++++++++++++++++++++ lv.json | 20 ++++++++++++++++++++ mg.json | 20 ++++++++++++++++++++ mi.json | 20 ++++++++++++++++++++ mk.json | 20 ++++++++++++++++++++ ml.json | 20 ++++++++++++++++++++ mn.json | 20 ++++++++++++++++++++ mr.json | 20 ++++++++++++++++++++ ms_MY.json | 20 ++++++++++++++++++++ mt.json | 20 ++++++++++++++++++++ my.json | 20 ++++++++++++++++++++ nah.json | 20 ++++++++++++++++++++ nap.json | 20 ++++++++++++++++++++ nb.json | 20 ++++++++++++++++++++ nds.json | 20 ++++++++++++++++++++ ne.json | 20 ++++++++++++++++++++ nl.json | 20 ++++++++++++++++++++ nl_BE.json | 20 ++++++++++++++++++++ nn.json | 20 ++++++++++++++++++++ nso.json | 20 ++++++++++++++++++++ oc.json | 20 ++++++++++++++++++++ om.json | 20 ++++++++++++++++++++ or.json | 20 ++++++++++++++++++++ pa.json | 20 ++++++++++++++++++++ pap.json | 20 ++++++++++++++++++++ pl.json | 20 ++++++++++++++++++++ pms.json | 20 ++++++++++++++++++++ ps.json | 20 ++++++++++++++++++++ pt.json | 20 ++++++++++++++++++++ pt_BR.json | 20 ++++++++++++++++++++ ro.json | 20 ++++++++++++++++++++ ru.json | 20 ++++++++++++++++++++ ru(a)petr1708.json | 20 ++++++++++++++++++++ scn.json | 20 ++++++++++++++++++++ sco.json | 20 ++++++++++++++++++++ si_LK.json | 20 ++++++++++++++++++++ sk.json | 20 ++++++++++++++++++++ sk_SK.json | 20 ++++++++++++++++++++ sl.json | 20 ++++++++++++++++++++ sl_SI.json | 20 ++++++++++++++++++++ sn.json | 20 ++++++++++++++++++++ so.json | 20 ++++++++++++++++++++ son.json | 20 ++++++++++++++++++++ sq.json | 20 ++++++++++++++++++++ sr.json | 20 ++++++++++++++++++++ sr(a)latin.json | 20 ++++++++++++++++++++ st.json | 20 ++++++++++++++++++++ su.json | 20 ++++++++++++++++++++ support-connecting.json | 20 ++++++++++++++++++++ sv.json | 20 ++++++++++++++++++++ sw.json | 20 ++++++++++++++++++++ szl.json | 20 ++++++++++++++++++++ ta.json | 20 ++++++++++++++++++++ te.json | 20 ++++++++++++++++++++ te_IN.json | 20 ++++++++++++++++++++ tg.json | 20 ++++++++++++++++++++ th.json | 20 ++++++++++++++++++++ ti.json | 20 ++++++++++++++++++++ tk.json | 20 ++++++++++++++++++++ tr.json | 20 ++++++++++++++++++++ tzm.json | 20 ++++++++++++++++++++ ug(a)Arab.json | 20 ++++++++++++++++++++ uk.json | 20 ++++++++++++++++++++ ur.json | 20 ++++++++++++++++++++ ur_PK.json | 20 ++++++++++++++++++++ uz.json | 20 ++++++++++++++++++++ ve.json | 20 ++++++++++++++++++++ vi.json | 20 ++++++++++++++++++++ wa.json | 20 ++++++++++++++++++++ wo.json | 20 ++++++++++++++++++++ zh_CN.json | 20 ++++++++++++++++++++ zh_HK.json | 20 ++++++++++++++++++++ zh_TW.json | 20 ++++++++++++++++++++ zu.json | 20 ++++++++++++++++++++ 155 files changed, 3100 insertions(+) diff --git a/ach.json b/ach.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ach.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ady.json b/ady.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ady.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/af.json b/af.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/af.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ak.json b/ak.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ak.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/am.json b/am.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/am.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ar.json b/ar.json new file mode 100644 index 000000000..fb8f552b6 --- /dev/null +++ b/ar.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Ø£ÙØ§Ø¬Ù ØµØ¹ÙØšØ© ÙÙ Ø§ÙØ¥ØªØµØ§Ù ØšØŽØšÙØ© ØªÙØ± ÙÙØ§ Ø£Ø¯Ø±Ù Ø£ÙÙ ØªÙÙÙ Ø§ÙÙÙØŽÙÙØ©.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "ÙØ§ ÙÙÙÙÙÙÙÙ Ø§ÙÙÙØ§Ø° Ø¥ÙÙ Ø§ÙÙØ·Ø§Ù X.onion !", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/arn.json b/arn.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/arn.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ast.json b/ast.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ast.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/az.json b/az.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/az.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ba.json b/ba.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ba.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/be.json b/be.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/be.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/bg.json b/bg.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/bg.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/bn.json b/bn.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/bn.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/bn_BD.json b/bn_BD.json new file mode 100644 index 000000000..ef98c9a1e --- /dev/null +++ b/bn_BD.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "àŠàŠ®àŠ¿ àŠàŠ° àŠžàŠàŠ¯à§àŠà§ àŠžàŠ®àŠžà§àŠ¯àŠŸ àŠ¹àŠà§àŠà§, àŠàŠ¬àŠ àŠàŠ®àŠ¿ àŠàŠ¿ àŠà§àŠ² àŠ¬à§àŠàŠ€à§ àŠªàŠŸàŠ°àŠàŠ¿ àŠšàŠŸà¥€", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/bn_IN.json b/bn_IN.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/bn_IN.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/bo.json b/bo.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/bo.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/br.json b/br.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/br.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/brx.json b/brx.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/brx.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/bs.json b/bs.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/bs.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ca.json b/ca.json new file mode 100644 index 000000000..83d0a0649 --- /dev/null +++ b/ca.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Tinc problemes per connectar amb el Tor i desconec el motiu.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ceb.json b/ceb.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ceb.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/cs.json b/cs.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/cs.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/csb.json b/csb.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/csb.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/cv.json b/cv.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/cv.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/cy.json b/cy.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/cy.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/da.json b/da.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/da.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/de.json b/de.json new file mode 100644 index 000000000..05b1a5862 --- /dev/null +++ b/de.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "Tor-Browser kann sich nicht verbinden, aber es scheint nicht an Zensur-MaÃnahmen zu liegen.", + "description": "<p class=\"mb-3\">Eines der hÃ€ufigsten Probleme, die bei Tor-Browser Verbindungsprobleme verursacht, ist eine verstellte System-Uhr. Stelle daher sicher, dass deine System-Uhr und die Zeitzone richtig eingestellt ist. Wenn dies das Problem nicht behebt, besuche die Fehlerbehebungsseite in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor-Browser-Anleitung</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Ich habe Probleme mich mit Tor zu verbinden und kann die Ursache nicht finden.", + "description": "<p class=\"mb-3\">Wenn du Verbindungsprobleme hast, wÃ€hle bitte die Option \"Tor-Protokoll in die Zwischenablage kopieren\" aus. FÃŒge dann das Tor-Protokoll in eine Textdatei oder ein anderes Dokument ein. Du solltest nun einen der folgenden verbreiteten FehlereintrÃ€ge sehen (suche nach foldenden Zeilen in deinem Tor-Protokoll):</p><h5>Ãblicher Fehlereintrag #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung zu einem SOCKS-Proxy fehlschlÃ€gt. Wenn fÃŒr deine Netzwerkkonfiguration ein SOCKS-Proxy erforderlich ist, stelle sicher, dass du die erforderlichen Proxy-Daten korrekt eingegeben hast. Wenn kein SOCKS-Proxy benÃ¶tigt wird oder du diesbezÃŒglich nicht sicher bist, versuche ohne SOCKS-Proxy eine Verbindung zum Tor-Netzwerk herzustellen.<p><h5>Ãblicher Fehlereintrag #2: Kann WÃ€chter-Weiterleitung nicht erreichen</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/20 17 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung des Tor-Clients mit dem ersten Knoten im Tor-Circuit fehlschlÃ€gt. Dies kann bedeuten, dass du dich in einem zensierten Netzwerk befindest. Versuche dich mit BrÃŒcken zu verbinden, was das Problem beheben sollte.</p><h5>Ãblicher Fehlereintrag #3: Fehlschlag bei der VervollstÃ€ndigung des TLS-Handschlags</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass dein Tor-Client einen TLS-Handschlag mit den Verzeichnisinstanzen nicht erfolgreich abschlieÃen konnte. Die Verwendung von BrÃŒcken wird das wahrscheinlich beheben.</p><h5>Ãblicher Fehlereintrag #4: Taktversatz</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and d ate settings.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass deine System-Uhr verstellt ist. Bitte stelle sicher, dass deine System-Uhr und die entsprechende Zeitzone richtig gestellt sind. Starte Tor danach neu.</p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Ich kann X.onion nicht erreichen!", + "description": "<p class=\"mb-3\">Wenn du den gewÃŒnschten Onion-Dienst nicht erreichen kannst, stelle sicher, dass du die 16 Zeichen lange Onion-Adresse richtig eingegeben hast: Sogar ein kleiner Tippfehler verhindert, dass Tor-Browser die Website finden kann. Wenn du dich dann mit dem Onion-Dienst immer noch nicht verbinden kannst, versuche es spÃ€ter noch einmal. Es kann vorÃŒbergehende Verbindungsprobleme im Netz geben oder die Seitenbetreiber haben ohne Vorwarnung die Seite vom Netz genommen.</p><p class=\"mb-3\">Du kannst auch ÃŒberprÃŒfen, ob es dir grundsÃ€tzlich mÃ¶glich ist Onion-Dienste zu nutzen, in dem du dich mit <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>s Onion-Dienst verbindest.</p>" + } +} diff --git a/dz.json b/dz.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/dz.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/el.json b/el.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/el.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/en_GB.json b/en_GB.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/en_GB.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/eo.json b/eo.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/eo.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/es.json b/es.json new file mode 100644 index 000000000..5f8938425 --- /dev/null +++ b/es.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "El Navegador Tor no conecta, pero no parece ser un problema con la censura.", + "description": "<p class=\"mb-3\">Uno de los problemas mÃ¡s habituales que causa errores de conexiÃ³n en el Navegador Tor es un reloj del sistema incorrectamente ajustado. Por favor, asegÃºrate de que el reloj de tu sistema y tu zona horaria estÃ¡n configurados correctamente. Si esto no soluciona tu problema, dirÃgete a la pÃ¡gina de SoluciÃ³n de Problemas en el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">manual del Navegador Tor</a></mark></p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Estoy teniendo problemas conectando a Tor, y no logro averiguar quÃ© es lo que estÃ¡ mal.", + "description": "Si tienes problemas para conectarte, por favor selecciona la opciÃ³n \"copiar el registro de Tor al portapapeles\". Luego pega el registro Tor en un archivo de texto u otro documento. DeberÃas ver uno de estos errores comunes de registro (busca las siguientes lÃneas en tu registro Tor): Error comÃºn de registro #1: Fallo de conexiÃ³n proxy 2017-10-29 09:23:40.800[NOTICE] Abriendo socks en 127.0.0.1:9150\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 10%: Finaliza hankshake con el servidor de directorios\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectar toxx.. xxx.. xxx. xx: xxxxxxx (\"fallo general del servidor SOCKS\") Si ves lÃneas como estas en tu registro Tor, significa que no te estÃ¡s conectando a un proxy SOCKS. Si se requiere un proxy SOCKS para la configuraciÃ³n de red, asegÃºrate de introducir correctamente los datos del proxy. Error de registro comÃºn #2: No se puede llegar a los relÃ©s de guardia 11/1/2017 21:11:43 PM. 500[AVISO] Abriendo el socks en 127.0.0.1:9150\n11/1/2017 21:11:44 PM. 300[AVISO] Bootstrapped 80%: ConexiÃ³n a la red Tor\n11/1/2017 21:11:44 PM. 300[ADVERTENCIA] No encontramos nodo para el salto 0 de nuestro camino. Descartar este circuito.\n11/1/2017 21:11:44 PM. 500[AVISO] Bootstrapped 85%: Acabando el handshake con el primer salto\n11/1/2017 21:11:11:45 PM. 300[ADVERTENCIA] No se ha encontrado nodo para el salto 0 de nuestra ruta. Descartando este circuito: si ves lÃneas como estas en tu registro Tor, significa que tu Tor no se conectÃ³ al primer nodo del circuito Tor. Esto podrÃa significar que estÃ¡s en una red ce nsurada. Error de registro comÃºn #3: No se pudo completar el handshake TLS 13-11-17 19:52:24:24.300[ATENCIÃN) Bootstrapped 10%: Finalizar handshake con el servidor de directorios\n13-11-17 19:53:49.300[ADVERTENCIA] Problema con el bootstrapping. Atascado al 10%: Acabando handshake con el servidor de directorios. (HECHO; HECHO; conteo 10; recomendaciÃ³n; host[host] en xxx. xxx. xxx. xxx. xx: xxx)\n13-11-17 19:53:49.300[ATENCIÃN] 10 conexiones han fallado:\n13-11-17 19:53:49.300[ADVERTENCIA] 9 conexiones caidas en estado handshaking (TLS) con estado SSL SSLv2/v3 lea servidor hola A en HANDSHAKE\n13-11-17 19:53:49.300[ADVERTENCIA] 1 conexiones muertas en estado connect()ing con estado SSL (sin objeto SSL) Si ves lÃneas como esta en tu registro de Tor, significa que Tor no pudo completar un handshake TLS con las competencias del directorio. Error de registro comÃºn #4: DesviaciÃ³n del reloj 19.11.2017 00:04:47.400[ATENCIÃN] IntÃ©rprete de socks de apertura en 127.0.0.0.1:9150\n19.1 1.2017 00:04:48.000[ADVERTENCIA] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n19.11.2017 00:04:48.200[ADVERTENCIA] Bootstrapped 10%: Finalizando el handshake con el servidor de directorios\n19.11.2017 00:04:48.800[ADVERTENCIA] Celda de NETINFO recibida con tiempo sesgado (OR: xxx. xx. xx. xx: xxxx): Parece que nuestro reloj estÃ¡ atrasado 1 dÃa, 0 horas, 1 minutos, o que el suyo estÃ¡ adelantado.\nTor requiere un reloj preciso para funcionar: por favor, comprueba tus ajustes de hora, zona horaria y fecha Si ves lÃneas como esta en tu registro Tor, significa que el reloj de tu sistema es incorrecto. AsegÃºrate de que tu reloj estÃ¡ ajustado correctamente, incluyendo la zona horaria. A continuaciÃ³n, reinicia Tor." + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Â¡No puedo conectar a X.onion!", + "description": "<p class=\"mb-3\">Si no puede alcanzar el servicio onion que desea, asegÃºrese de que ha introducido correctamente la direcciÃ³n onion de 16 caracteres: incluso un pequeÃ±o error evitarÃ¡ que el Navegador Tor logre alcanzar el sitio. Si aÃºn asÃ no puede conectar al servicio onion, por favor, intÃ©ntelo de nuevo mÃ¡s tarde. Puede haber un problema temporal con la conexiÃ³n, o los operadores del sitio pueden haberle permitido desconectar sin avisar.</p><p class=\"mb-3\">TambiÃ©n puede asegurarse de que es capaz de acceder a otros servicios onion conectando al servicio onion de <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/es_AR.json b/es_AR.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/es_AR.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/es_CL.json b/es_CL.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/es_CL.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/es_CO.json b/es_CO.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/es_CO.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/es_MX.json b/es_MX.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/es_MX.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/et.json b/et.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/et.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/eu.json b/eu.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/eu.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/fa.json b/fa.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/fa.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/fi.json b/fi.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/fi.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/fil.json b/fil.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/fil.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/fo.json b/fo.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/fo.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/fr.json b/fr.json new file mode 100644 index 000000000..4ed10c84e --- /dev/null +++ b/fr.json @@ -0,0 +1,20 @@ +{ + "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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">âguide du navigateur Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connexion-2", + "control": "connexion-2", + "title": "JâÃ©prouve des difficultÃ©s Ã me connecter Ã Tor et je nâarrive pas Ã comprendre ce qui ne va pas.", + "description": "<p class=\"mb-3\">Si vous Ã©prouvez des difficultÃ©s Ã vous connecter, veuillez sÃ©lectionner lâoption Â«Â Copier le journal de Tor dans le presse-papiersÂ Â». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver lâune de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor)Â : </p><h5>Erreur habituelle de journal noÂ 1 : Ã©chec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter Ã un mandataire SOCKS. Si un mandataire SOCKS est nÃ©cessaire Ã la configuration de rÃ©seau, veuillez alors vous assurer dâavoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS nâest pas nÃ©cessaire ou si vous ne savez pas, veuillez tenter de vous connecter au rÃ©seau Tor sans mandataire SOCKS.<p><h5>Erreur habituelle de journal noÂ 2 : impossible dâatteindre les relais gardes</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/ 2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter au premier nÅud du circuit Tor. Cela pourrait signifier que vous Ãªtes sur un rÃ©seau qui est censurÃ©. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5>Erreur habituelle de journal noÂ 3 : Ã©chec dâÃ©tablissement dâune liaison TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19 :53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas rÃ©ussi Ã Ã©tablir une liaison TLS avec les autoritÃ©s d'annuaire. Lâutilisation de ponts corrigera certainement cette situation.</p><h5>Erreur habituelle de journal noÂ 4 : dÃ©calage dâhorloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or t hat theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">\nSi vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge systÃšme nâest pas juste. Veuillez vous assurer que votre horloge est rÃ©glÃ©e avec prÃ©cision, fuseau horaire inclus, puis redÃ©marrez Tor. </p>" + }, + "connecting-3": { + "id": "#connexion-3", + "control": "connexion-3", + "title": "Je ne peux pas accÃ©der Ã X.onionâ!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">Vous pouvez aussi vous assurer que vous arrivez Ã accÃ©der Ã dâautres services oignon en vous connectant au service oignon de <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>\n\n" + } +} diff --git a/fr_CA.json b/fr_CA.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/fr_CA.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/fur.json b/fur.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/fur.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/fy.json b/fy.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/fy.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ga.json b/ga.json new file mode 100644 index 000000000..26d45c2d5 --- /dev/null +++ b/ga.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "NÃ fÃ©idir le BrabhsÃ¡laÃ Tor ceangal a bhunÃº, cÃ© nach mbaineann an fhadhb le cÃºrsaÃ cinsireachta.", + "description": "<p class=\"mb-3\">Is minic go mbÃonn fadhb le clog an chÃ³rais ina chÃºis le hearrÃ¡idÃ i mBrabhsÃ¡laÃ Tor. Ba chÃ³ir duit deimhniÃº go bhfuil clog an chÃ³rais agus an crios ama socraithe mar is ceart. Mura rÃ©itÃonn seo an fhadhb, fÃ©ach an leathanach FabhtcheartÃº i <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">LÃ¡mhleabhar BhrabhsÃ¡laÃ Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "NÃ fÃ©idir liom ceangal le lÃonra Tor, agus nÃ thuigim cad Ã© an fhadhb.", + "description": "<p class=\"mb-3\">MÃ¡ tÃ¡ fadhb agat ag ceangal le lÃonra Tor, ÃºsÃ¡id an rogha âcÃ³ipeÃ¡il logchomhad Tor go dtÃ an ghearrthaisce.â Ansin, greamaigh an logchomhad i dtÃ©acschomhad nÃ³ cÃ¡ipÃ©is eile. Is dÃ³cha go bhfeicfidh tÃº ceann de na hearrÃ¡idÃ coitianta seo (cuardaigh na lÃnte seo a leanas sa logchomhad):</p><h5>EarrÃ¡id choitianta #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to co nnect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn siad gur theip ort ceangal a bhunÃº le seachfhreastalaÃ SOCKS. MÃ¡ theastaÃonn seachfhreastalaÃ SOCKS uait ar do lÃonra, deimhnigh gur chuir tÃº mionsonraÃ an fhreastalaÃ isteach go ceart. Mura dteastaÃonn seachfhreastalaÃ SOCKS uair, nÃ³ mura bhfuil tÃº cinnte, dÃ©an iarracht ceangal a bhunÃº le lÃonra Tor gan seachfhreastalaÃ SOCKS.<p><h5>EarrÃ¡id choitianta #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] F ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ort ceangal a bhunÃº leis an chÃ©ad nÃ³d sa gciorcad Tor. Uaireanta, ciallaÃonn seo go bhfuil do lÃonra faoi chinsireacht. Bain triail as ceangal trÃ dhroichead; is dÃ³cha go rÃ©iteoidh sin an fhadhb.</p><h5>EarrÃ¡id choitianta #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 co nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ar Tor croitheadh lÃ¡imhe TLS leis na hÃºdarÃ¡is a chur i gcrÃch. Is dÃ³cha go rÃ©iteoidh droichead an fhadhb seo.</p><h5>EarrÃ¡id choitianta #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, c iallaÃonn sÃ© go bhfuil an clog i do rÃomhaire mÃcheart. Ba chÃ³ir duit socruithe an chloig a dheimhniÃº, an t-am, dÃ¡ta, agus crios ama san Ã¡ireamh. Ansin, atosaigh Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "NÃlim in ann teacht ar X.onion!", + "description": "<p class=\"mb-3\">Mura bhfuil tÃº in ann seirbhÃs .onion a shroicheadh, deimhnigh gur chuir tÃº an seoladh 16-carachtar isteach go ceart: mÃ¡ tÃ¡ aon bhotÃºn ann, fiÃº botÃºn an-bheag, nÃ bheidh BrabhsÃ¡laÃ Tor in ann an suÃomh a shroicheadh. MÃ¡ tÃ¡ tÃº cinnte gur chuir tÃº an seoladh ceart isteach, bain triail eile as ar ball. Seans go bhfuil fadhb shealadach leis an lÃonra, nÃ³ b'fhÃ©idir gur bhain riarthÃ³irÃ an tsuÃmh as lÃne Ã© gan rabhadh.</p><p class=\"mb-3\">B'fhiÃº freisin fÃ©achaint an fÃ©idir leat dul i dteagmhÃ¡il le seirbhÃsÃ .onion eile, mar shampla <a href=\"http://3g2upl4pq6kufc4m.onion\">seirbhÃs DuckDuckGo</a>.</p>" + } +} diff --git a/gd.json b/gd.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/gd.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/gl.json b/gl.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/gl.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/gu.json b/gu.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/gu.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/gu_IN.json b/gu_IN.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/gu_IN.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/gun.json b/gun.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/gun.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ha.json b/ha.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ha.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/he.json b/he.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/he.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/hi.json b/hi.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/hi.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/hr.json b/hr.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/hr.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/hr_HR.json b/hr_HR.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/hr_HR.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ht.json b/ht.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ht.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/hu.json b/hu.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/hu.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/hy.json b/hy.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/hy.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ia.json b/ia.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ia.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/id.json b/id.json new file mode 100644 index 000000000..0fdc118e3 --- /dev/null +++ b/id.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "Tor Browser tidak dapat tersambung, tapi ini tampaknya bukan akibat sensor oleh pihak lain.", + "description": "<p class=\"mb-3\">Salah satu masalah umum yang menyebabkan kegagalan koneksi di Tor Browser adalah jam sistem operasi yang tidak tepat. Silakan pastikan jam di sistem operasi dan zona waktu diatur dengan tepat di komputer Anda. Jika ini tidak memperbaiki masalah koneksi, lihat halaman Troubleshooting di <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", + "description": "<p class=\"mb-3\"> Jika Anda mendapat masalah dalam terhubung ke jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):\n\n</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS se rver failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.\n\n<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> Jika Anda melihat baris seperti ini, Tor gagal tersambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.\n\n</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.<h5>\n\nCommon log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. Tor memerlukan jam yang akurat supaya berfungsi dengan baik. Silakan periksa pengaturan waktu, zona waktu, dan tanggal. Pastikan jam di komputer Anda diatur dengan benar, termasuk zona waktu yang tepat. Lalu, restart Tor.\n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Tidak dapat terhubung ke X.onion!", + "description": "<p class=\"mb-3\">Jika Anda tidak dapat terhubung ke sebuah onion service yang diinginkan, pastikan Anda telah dengan tepat memasukkan 16-karakter alamat onion-nya. Bahkan kesalahan sedikit akan membuat Tor Browser tidak dapat terhubung ke situs yang dimaksud. Jika Anda tetap tidak dapat terhubung, silakan coba lagi nanti. Mungkin ada masalah sedikit di situsnya, atau operator situsnya sedang membuat situsnya menjadi offline tanpa pemberitahuan. </p><p class=\"mb-3\">Anda juga dapat memastikan jika Anda juga dapat terhubung ke situs onion service lain dengan mencoba terhubung ke <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>." + } +} diff --git a/is.json b/is.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/is.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/it.json b/it.json new file mode 100644 index 000000000..7a04f1284 --- /dev/null +++ b/it.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connessione-1", + "control": "connessione-1", + "title": "Tor Browser non si connette, ma non sembra che sia dovuto alla censura.", + "description": "<p class=\"mb-3\">Uno dei problemi piÃ¹ comuni che causano errori di connessione in Tor Browser Ãš un orologio di sistema errato. Assicurati che l'orologio di sistema e il fuso orario siano impostati correttamente. Se ciÃ² non risolve il problema, consultare la pagina Risoluzione dei problemi su <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manuale di Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connessione-2", + "control": "connessione-2", + "title": "Sto avendo problemi nella connessione a Tor e non riesco a capire quale sia la causa.", + "description": "<p class=\"mb-3\">Se stai avendo problemi a connetterti, per favore seleziona l'opzione \"copia i log di Tor sulla clipboard.\" Poi incolla il log di Tor su un file di testo o un altro tipo di documento. Dovresti vedere uno di questi errori di log comuni (cerca per le seguenti linee nei log di Tor):</p><h5>Errore di log comune #1: Errore di connessione Proxy </h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150\n2017-10-29 09:23:47.900 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n2017-10-29 09:23:47.900 [AVVISO] Progressione 10%: Completando l'handshake con l'elenco dei server\n2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\nÂ 2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\n2017-10-29 09:24:08.900 [ATTENZIONE] Prox y Client: impossibile connettersi a xx..xxx..xxx.xx:xxxxx (\"errore generale server SOCKS\")</code></pre></p><p class=\"mb-3\">Se vedi delle linee come queste nei log di Tor, significa che la connessione a un proxy SOCKS sta fallendo.Se un proxy SOCKS Ãš richiesto per la tua configurazione di rete, controlla di aver inserito i dettagli del proxy correttamente.Se un proxy SOCKS non Ãš richiesto, o non ne sei sicuro, prova a connetterti alla rete Tor senza un proxy SOCKS.<p><h5>Errore di log comune #2: Non Ãš possibile raggiungere i guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150 \n11/1/2017 21:11:44 PM.300 [AVVISO] Progressione 80%: Connessione alla rete Tor\n11/1/2017 21:11:44 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.\n11/1/2017 21:11:44 PM.500 [AVVISO] Progressione 85%: Terminando l'handshake con il primo hop\nÂ 11/1/2017 21:11:45 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.</code></pre></p><p class=\"mb-3\">Se vedi delle linee come questo nel tuo log di Tor, significa che Tor ha fallito la connesione al primo nodo del circuito Tor. Questo potrebbe significare che ti trovi su una rete censurata. Per favore prova a connetterti con i bridge, e questo dovrebbe risolvere il problema.</p><h5>Errore di log comune #3: Errore nel completare l'handshake TLS</h5><p class=\"mb-3\"><pre><code>13-11-17 19:52:24.300 [AVVISO] Progressione 10%: Handshake con l'elenco dei server completato\n13-11-17 19:53:49.300 [ATTENZIONE] Problema durante la progressione. Fermo al 10%: Completando l'handshake con l'elenco dei server (FATTO; FATTO; contatore 10; avviso di raccomandazione; host [host] a xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [ATTENZIONE] 10 connessioni hanno fallito:\n13-11-17 19:53:49.300 [ATTENZIONE] 9 connessioni sono scadute durante lo stato di handshaking (TLS) con lo stato SSL di SSLv2/v3 r isposta server hello A in HANDSHAKE \n13-11-17 19:53:49.300 [ATTENZIONE] 1 connessione Ãš scaduta nello stato di connessione con stato SSL (Nessun oggetto SSL)</code></pre></p><p class=\"mb-3\">Se vedi delle linee cosÃ¬ nel tuo log Tor, significa che Tor ha fallito il completamento dell'handshake TLS con le autoritÃ dell'elenco. Usare i bridge risolverÃ probabilmente il problema.</p><h5>Errore log comune #4: Distorsione orario</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [AVVISO] Apertura ascoltatore porte SOCKS su 127.0.0.1:9150\n19.11.2017 00:04:48.000 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n19.11.2017 00:04:48.200 [AVVISO] Progressione 10%: Terminando l'handshake con l'elenco dei server\n19.11.2017 00:04:48.800 [ATTENZONE] Ricevuta cella NETINFO con orario distorto (O:xxx.xx.x.xx:xxxx): Sembra che il tuo orologio sia indietro di 1 giorno, 0 ore, 1 minuto, o che il loro sia avanti.\nTor richiede un orologio accurato per funzionare: per favore con trolla l'ora, la tua zona temporale e le impostazioni sulla data.</code></pre></p><p class=\"mb-3\">Se vedi queste linee nel tuo log di Tor, significa che l'ora del sistema Ãš incorretta. Per favore controlla che il tuo orologio sia impostato accuratamente, inclusa la zona temporale. DopodichÃ© riavvia Tor.</p>" + }, + "connecting-3": { + "id": "#connessione-3", + "control": "connessione-3", + "title": "Non posso raggiungere X.onion!", + "description": "<p class=\"mb-3\">Se non riesci a raggiungere il sito che desideri, assicurati di aver inserito correttamente l'indirizzo a 16 caratteri: anche un piccolo errore puÃ² impedire al Tor Browser di raggiungere il sito. Se non riesci ancora a connetterti al sito, riprova piÃ¹ tardi. Potrebbe esserci un problema di connessione temporaneo, oppure gli operatori del sito lo hanno lasciato andare offline senza lasciare preavviso.</p><p class=\"mb-3\">Puoi anche provare a connetterti a <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a> per vedere se riesci ad accedere ad altri siti.</p>" + } +} diff --git a/ja.json b/ja.json new file mode 100644 index 000000000..24309f341 --- /dev/null +++ b/ja.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#æ¥ç¶-1", + "control": "æ¥ç¶-1", + "title": "Torãã©ãŠã¶ãŒã¯æ¥ç¶ããŸããããæ€é²ã®åé¡ã§ã¯ãªãããã§ãã", + "description": "Torãã©ãŠã¶ãŒã§æ¥ç¶ãšã©ãŒãçºçããæãäžè¬çãªåé¡ã®1ã€ã¯ãäžæ£ãªã·ã¹ãã ã¯ããã¯ã§ããã·ã¹ãã ã®æèšãšã¿ã€ã ãŸãŒã³ãæ£ç¢ºã«èšå®ãããŠããããšãç¢ºèªããŠãã ãããããã§åé¡ãè§£æ±ºããªãå Žåã¯ãTorãã©ãŠã¶ãŒã®ããã¥ã¢ã«ã®ãã©ãã«ã·ã¥ãŒãã£ã³ã°ã®ããŒãžãåç§ããŠãã ããã" + }, + "connecting-2": { + "id": "#æ¥ç¶-2", + "control": "æ¥ç¶-2", + "title": "Torã«ã¢ã¯ã»ã¹ã§ããªãããäœãåé¡ãªã®ãåãããŸããã", + "description": "<p class=\"mb-3\">Torã«ã¢ã¯ã»ã¹ã§ããªãå ŽåããTorãã°ãã¯ãªããããŒãã«ã³ããŒãããéžæè¢ãéžãã§ããã°ãã¡ã¢åž³ãããã¯ããã¥ã¡ã³ããã¡ã€ã«ã«è²Œãä»ããŠäžãããä»¥äžã®è¯ããããšã©ãŒã¡ãã»ãŒãžãèŠã€ããã¯ãã§ãïŒ</p><h5>ãããããã°ãšã©ãŒ#1: ãããã·æ¥ç¶å€±æ</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx.. xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãSOCKSãããã·ãšç¹ãããªããšããããšã§ãããããã¯ãŒã¯ã«ã¯SOCKSãããã·ãå¿èŠãªããèšå®ãç¢ºèªããŠäžãããSOCKSãããã·ãå¿èŠã§ã¯ãªãå Žåããããã¯ããåãããªãå ŽåãSOCKSãããã·ç¡ãã§Torã«ã¢ã¯ã»ã¹ããŠã¿ãŠäžããã<p><h5>ãããããã°ãšã©ãŒ#2: ã¬ãŒããªã¬ãŒãšæ¥ç¶ã§ããªã</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discardi ng this circuit.</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorã¯circuitã®æåã®ããŒããšæ¥ç¶ã§ããªãã£ããšããããšã§ããæ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ããããŸããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããã¯ãã§ãã</p><h5>ãããããã°ãšã©ãŒ#3: TLSãã³ãã·ã§ã€ã¯ã®å€±æ</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorããã£ã¬ã¯ããªãªãŒãœãªãã£ãšTLSãã³ãã·ã§ã€ã¯ãå®äºã§ããªãã£ããšããããšã§ããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããå¯èœæ§ãããã</p><h5>ãããããã°ãšã©ãŒ#4: ã¯ããã¯ã¹ãã¥ãŒ</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p clas s=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãã·ã¹ãã ã»ã¯ããã¯ã«ã¯ééã£ãæå»ãèšå®ãããŸããã·ã¹ãã ã»ã¯ããã¯ãæ£ããæå»ãšã¿ã€ã ãŸãŒã³ã«åãããŠããTorãåèµ·åããŠäžããã </p>" + }, + "connecting-3": { + "id": "#æ¥ç¶-3", + "control": "æ¥ç¶-3", + "title": "X.onionãååŸã§ããŸããïŒ", + "description": "ããªããæããªããªã³ã®ãµãŒãã¹ã«ã¢ã¯ã»ã¹ã§ããªãå Žåã¯ã16æåã®ãªããªã³ã¢ãã¬ã¹ãæ£ããå¥åããããšãç¢ºèªããŠãã ãããå°ããªééãã§ããTorãã©ãŠã¶ãŒããµã€ãã«ã¢ã¯ã»ã¹ã§ããªããªããŸãã" + } +} diff --git a/jv.json b/jv.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/jv.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ka.json b/ka.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ka.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/kk.json b/kk.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/kk.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/km.json b/km.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/km.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/kn.json b/kn.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/kn.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ko.json b/ko.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ko.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ko_KR.json b/ko_KR.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ko_KR.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ku.json b/ku.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ku.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ku_IQ.json b/ku_IQ.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ku_IQ.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/kw.json b/kw.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/kw.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ky.json b/ky.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ky.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/la.json b/la.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/la.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/lb.json b/lb.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/lb.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/lg.json b/lg.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/lg.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ln.json b/ln.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ln.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/lo.json b/lo.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/lo.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/lt.json b/lt.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/lt.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/lv.json b/lv.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/lv.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/mg.json b/mg.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/mg.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/mi.json b/mi.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/mi.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/mk.json b/mk.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/mk.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ml.json b/ml.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ml.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/mn.json b/mn.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/mn.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/mr.json b/mr.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/mr.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ms_MY.json b/ms_MY.json new file mode 100644 index 000000000..94afcb73e --- /dev/null +++ b/ms_MY.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#menyambung-1", + "control": "menyambung-1", + "title": "Pelayar Tor tidak dapat bersambung, tetapi ia bukanlah isu berkenaan penapisan.", + "description": "<p class=\"mb-3\">Salah satu masalah utama yang menyebabkan ralat sambungan dalam Pelayar Tor ialah jam sistem yang salah. Sila pastikan jam sistem dan zon waktu anda telah ditetapkan dengan betul. Jika masalah ini masih berlaku, sila rujuk laman Pencarisilapan di dalam <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âpanduan Pelayar Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#menyambung-2", + "control": "menyambung-2", + "title": "Saya menghadapi masalah ketika menyambung dengan Tor, dan saya tidak tahu apa masalah yang berlaku.", + "description": "<p class=\"mb-3\">Jika anda menghadapi masalah sambungan, pilih pilihan \"salin log Tor ke papan keratan.â Kemudian tampal log Tor ke dalam fail teks atau lain-lain fail dokumen. Anda akan dapati terdapat ralat log (lihat baris berikut di dalam log Tor anda):</p><h5>Ralat log umum #1: Kegagalan sambungan proksi</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\" )</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud anda gagal menyambung dengan proksi SOCKS. Jika proksi SOCKS diperlukan untuk persediaan rangkaian anda, maka sila pastikan anda telah memasukkan perincian proksi tersebut dengan betul. Jika proksi SOCKS tidak diperlukan, atau anda tidak pasti, cuba sambung ke rangkaian Tor tanpa proksi SOCKS.<p><h5>Ralat log umum #2: Tidak dapat capai geganti pengawal</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb- 3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud Tor anda gagal menyambung ke nod pertama dalam litar Tor. Ia bermaksud anda berada dalam rangkaian bertapis. Cuba menyambung dengan titi, dan sepatutnya ia masalah selesai.</p><h5>Ralat log umum #3: Gagal menyelesaikan jabat-tangan TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat ba ris seperti ini di dalam log Tor anda, ia bermaksud Tor gagal menyelesaikan jabat-tangan TLS dengan autoriti direktori. Penggunaan titi dapat menyelesaikan masalah ini.</p><h5>Ralat log umum #4: Pencong jam</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini dalam log Tor anda, ia bermaksud jam sistem anda salah. Sila pastikan jam anda telah ditetapkan dengan tepat, termasuklah zon waktu yang betul. Kemudian mulakan semula Tor. </p>" + }, + "connecting-3": { + "id": "#menyambung-3", + "control": "menyambung-3", + "title": "Saya tidak dapat mencapai X.onion!", + "description": "<p class=\"mb-3\">Jika anda masih tidak dapat mencapai servis onion yang dikehendaki, pastikan anda telah memasukkan alamat onion 16-aksara dengan betul: walaupun dengan kesilapan kecil akan menghentikan Pelayar Tor mencapai laman. Jika anda masih tidak dapat menyambung ke servis onion, cuba sekali lagi. Kadangkala ia merupakan masalah sambungan sementara, atau operator laman telah menjadi luar talian tanpa apa-apa amaran.</p><p class=\"mb-3\">Anda juga perlu pastikan dapat mencapai servis onion lain dengan menyambung ke Servis Onion <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/mt.json b/mt.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/mt.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/my.json b/my.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/my.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/nah.json b/nah.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/nah.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/nap.json b/nap.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/nap.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/nb.json b/nb.json new file mode 100644 index 000000000..66b233d46 --- /dev/null +++ b/nb.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "Tor-nettleseren kan ikke koble til, men det later ikke til Ã¥ vÃŠre et sensurproblem.", + "description": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/nds.json b/nds.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/nds.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ne.json b/ne.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ne.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/nl.json b/nl.json new file mode 100644 index 000000000..4fdd4e365 --- /dev/null +++ b/nl.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#verbinden-1", + "control": "verbinden-1", + "title": "Tor Browser maakt geen verbinding, maar het lijkt geen probleem te zijn met censuur.", + "description": "<p class=\"mb-3\">Een van de meest voorkomende problemen die verbindingsfouten in Tor Browser veroorzaken, is een onjuiste systeemklok. Zorg ervoor dat uw systeemklok en tijdzone nauwkeurig zijn ingesteld. Als dit het probleem niet oplost, zie de pagina Problemen oplossen op de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser manual</a></mark>.</p>" + }, + "connecting-2": { + "id": "#verbinden-2", + "control": "verbinden-2", + "title": "Ik ondervind problemen bij het verbinding maken met Tor, en ik vind maar niet wat er fout gaat.", + "description": "<p class=\"mb-3\">Als u problemen ondervindt bij het verbinden, selecteert u de optie om \"Tor log naar klembord te kopiÃ«ren\". Plak vervolgens het Tor-log in een tekstbestand of een ander document. U zou een van deze Vaak voorkomend logfouten moeten zien (kijk naar de volgende regels in uw Tor-logboek): </p><h5>Vaak voorkomend logboekfout # 1: Proxy-verbindingsfout</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09: 23: 40.800 [LET OP] Opening Socks luisteraar op 127.0.0.1 : 9150 \n 2017-10-29 09: 23: 47.900 [LET OP] Bootstrapped 5%: verbinden met directoryserver \n 2017-10-29 09: 23: 47.900 [LETICE] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-clie nt: kan toxx..xxx..xxx.xx: xxxxx niet verbinden (\"algemene SOCKS-serverstoring\") </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, is dit betekent dat u geen verbinding kunt maken met een SOCKS-proxy. Als een SOCKS-proxy vereist is voor uw netwerkconfiguratie, moet u ervoor zorgen dat u uw proxy-gegevens correct hebt ingevoerd. Als een SOCKS-proxy niet vereist is, of als u het niet zeker weet, probeer dan verbinding te maken met het Tor-netwerk zonder een SOCKS-proxy.<p><h5>Gebruikslog fout # 2: Kan relais niet bereiken</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM .500 [LET OP] Luisteraar luisterpositie openen op 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [LET OP] Bootstrapped 80%: Verbinding maken met het Tor-netwerk \n 11/1/2017 21:11:44 PM.300 [WARN] Kan knooppunt voor hop 0 van ons pad niet vinden. Dit circuit weggooien. \n 11/1/2017 21:11:44 PM.500 [LET OP] Bootstrap 85%: Handshake beÃ«indigen met eerste hop \n 11/1/2017 21:11:45 P M.300 [WARN] Kan knooppunt niet vinden voor hop 0 van ons pad. Dit circuit verwijderen.</code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dit dat uw Tor geen verbinding kon maken met het eerste knooppunt in het Tor-circuit. Dit kan betekenen dat u zich op een netwerk bevindt dat gecensureerd is. Probeer te verbinden met bruggen, en dat zou het probleem moeten verhelpen.</p><h5> Algemene logfout # 3: Kan TLS-handshake niet voltooien</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 13-11-17 19: 53: 49.300 [WARN] Probleem met bootstrappen. Vastgelopen met 10%: handshake beÃ«indigen met directoryserver. (GEDAAN, GEDAAN, aantal 10; advieswaarschuwing; host [host] op xxx.xxx.xxx.xx: xxx) \n 13-11-17 19: 53: 49.300 [WARN] 10 verbindingen zijn mislukt: \n 13-11-17 19: 53: 49.300 [WARN] 9 verbindingen stierven in staatshandshaking (TLS) met SSL-status SSLv2 / v3 lezen server hallo A in HANDSHAKE \n 13-11-17 19: 53: 49.300 [WARN] 1 verbindingen zijn overleden in state connect () ing met SSL-staat (No SSL-object) </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dat Tor een TLS-handshake niet kon voltooien met de directory-autoriteiten. Het gebruik van bruggen lost dit waarschijnlijk op.</p><h5>Veel logboekfout # 4: Klok skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00: 04: 47.400 [LET OP] Opening Socks luisteraar op 127.0.0.1:9150 \n 19.11.2017 00: 04: 48.000 [LET OP] Bootstrap 5%: verbinding maken met directoryserver \n 19.11.2017 00: 04: 48.200 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 19.11.2017 00: 04: 48.800 [WARN] NETINFO-cel ontvangen met scheve tijd (OF: xxx.xx.x.xx: xxxx): het lijkt erop dat onze klok 1 dag, 0 uur, 1 minuut achterloopt, of die van hen liggen voor de deur. \n Tor vereist een nauwkeurige klok om te werken: controleer uw tijd-, tijdzone- en datuminstellin gen.</code></pre></p><p class=\"mb-3\">Als u lijnen zoals deze in uw Tor-logboek ziet, betekent dit dat uw systeemklok onjuist is. Zorg ervoor dat uw klok correct is ingesteld, inclusief de juiste tijdzone. Start dan Tor opnieuw. </p>" + }, + "connecting-3": { + "id": "#verbinden-3", + "control": "verbinden-3", + "title": "Ik kan X.onion niet bereiken!", + "description": "<p class=\"mb-3\">Als u de gewenste onion service niet kunt bereiken, moet u ervoor zorgen dat u het onion adres van 16 tekens correct hebt ingevoerd: zelfs een kleine fout zal ervoor zorgen dat Tor Browser de site niet kan bereiken. Als u nog steeds geen verbinding kunt maken met de onion service, probeert u het later opnieuw. Er kan een tijdelijke verbinding probleem zijn, of de site exploitanten kunnen hebben toegestaan dat het offline gaan zonder waarschuwing.</p><p class=\"mb-3\"> U kunt er ook voor zorgen dat u in staat om toegang te krijgen tot andere diensten ui door verbinding te maken <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s Onion Service.</p>" + } +} diff --git a/nl_BE.json b/nl_BE.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/nl_BE.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/nn.json b/nn.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/nn.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/nso.json b/nso.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/nso.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/oc.json b/oc.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/oc.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/om.json b/om.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/om.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/or.json b/or.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/or.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/pa.json b/pa.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/pa.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/pap.json b/pap.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/pap.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/pl.json b/pl.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/pl.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/pms.json b/pms.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/pms.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ps.json b/ps.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ps.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/pt.json b/pt.json new file mode 100644 index 000000000..390ca5e6c --- /dev/null +++ b/pt.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "connecting-1", + "title": "O Tor Browser nÃ£o liga, mas nÃ£o parece ser um problema com a censura.", + "description": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Eu estou a ter problemas para ligar ao Tor, e eu nÃ£o consigo descobrir o que estÃ¡ errado.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Eu nÃ£o consigo alcanÃ§ar X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/pt_BR.json b/pt_BR.json new file mode 100644 index 000000000..a1bf886e7 --- /dev/null +++ b/pt_BR.json @@ -0,0 +1,20 @@ +{ + "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.", + "description": "<p class=\"mb-3\">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</a></mark>.</p>" + }, + "connecting-2": { + "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": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opÃ§Ã£o para \"copiar o log de Tor para a Ã¡rea de transferÃªncias\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. VocÃª deverÃ¡ ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexÃ£o de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretÃ³rio\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretÃ³rio\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0 8.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se vocÃª encontrar linhas como estas em seu log do Tor, isto significa que falhou em conectar-se Ã um SOCKS proxy. Se um SOCKS proxy Ã© obrigatÃ³rio para a sua configuraÃ§Ã£o de rede, por favor certifique-se que vocÃª digitou seus detalhes de proxy corretamente. Se um SOCKS proxy nÃ£o Ã© obrigatÃ³rio, ou vocÃª nÃ£o estÃ¡ certo sobre isso, por favor tente conectar-se Ã rede Tor sem um 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\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.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\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hand shake 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\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor 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": "#conectando-3", + "control": "conectando-3", + "title": "NÃ£o consigo conectar ao X.onion!", + "description": "<p class=\"mb-3\">Se vocÃª nÃ£o conseguir acessar o serviÃ§o onion desejado, certifique-se de ter digitado o endereÃ§o onion com 16 caracteres corretamente: atÃ© mesmo um pequeno erro impedirÃ¡ que o Navegador Tor alcance o site. Se vocÃª ainda nÃ£o conseguir se conectar ao serviÃ§o onion, tente novamente mais tarde. Pode haver um problema de conexÃ£o temporÃ¡ria ou os operadores do site podem ter permitido que ele fique offline sem aviso prÃ©vio.</p><p class=\"mb-3\"> VocÃª tambÃ©m pode garantir que poderÃ¡ acessar outros serviÃ§os onion conectando-se ao <a href=\"http://3g2upl4pq6kufc4m.onion\">ServiÃ§o Onion</a>do DuckDuckGo.</p>" + } +} diff --git a/ro.json b/ro.json new file mode 100644 index 000000000..2fe13067e --- /dev/null +++ b/ro.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#connecting-1", + "control": "conectare-1", + "title": "Tor Browser nu se conecteazÄ, dar nu pare a fi o problemÄ de cenzurÄ.", + "description": "<p class=\"mb-3\">Una din cele mai frecvente cauze pentru problemele de conectare ale Tor Browser este ora sistemului incorectÄ. VerificÄ dacÄ ora Èi fusul orar sunt setate corect. DacÄ aceasta nu rezolvÄ problema, urmeazÄ indicaÈiile de Depanare din <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âmanualul Tor Browser</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "conectare-2", + "title": "Am dificultÄÈi Ã®n conectarea la Tor Èi nu Ã®nÈeleg ce e greÈit.", + "description": "<p class=\"mb-3\">DacÄ ai probleme de conectare, selecteazÄ opÈiunea \"copiazÄ log-ul Tor Ã®n clipboard\". Apoi lipeÈte log-ul astfel copiat Ã®ntr-un fiÈier text sau alt document. Ar trebui sÄ vezi unul dintre aceste mesaje de eroare comune (cautÄ astfel de linii Ã®n log-ul Tor):</p><h5>Eroare comunÄ #1: Eroare de conectare la proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-ul Tor, Ã®nseamnÄ cÄ nu te poÈi conecta la un proxy SOCKS. DacÄ un proxy SOCKS este necesar pentru reÈeaua pe care o foloseÈti, atunci asigurÄ-te cÄ ai introdus setÄrile de proxy corecte. DacÄ un proxy SOCKS nu e necesar sau nu eÈti sigur, Ã®ncearcÄ sÄ te conectezi la reÈeaua Tor fÄrÄ un proxy SOCKS.<p><h5>Eroare comunÄ #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\" >DacÄ vezi astfel de linii in log-ul Tor Ã®nseamnÄ ca nu s-a reuÈit conectarea la primul nod din circuitul Tor. Aceasta ar putea Ã®nsemna cÄ te afli Ã®ntr-o reÈea cenzuratÄ. ÃncearcÄ conectarea prin punÈi, care ar trebui sÄ rezolve problema.</p><h5>Eroare comunÄ #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-u l Tor Ã®nseamnÄ cÄ nu s-a realizat o conexiune completÄ TLS cu serverele de directoare. Folosirea punÈilor va rezolva probabil acest lucru. </p><h5>Eroare comunÄ #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">DacÄ vezi astfel de linii in log-ul Tor Ã®nseamnÄ cÄ ceasul sistemului tÄu e incorect. AsigurÄ-te cÄ ceasul sistemului este corect, inclusiv fusul orar, apoi reporneÈte Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "conectare-3", + "title": "Nu pot ajunge la X.onion!", + "description": "<p class=\"mb-3\">DacÄ nu poÈi ajunge la serviciul onion dorit, asigurÄ-te cÄ ai introdus cele 16 caractere din adresa onion corect - chiar Èi cea mai micÄ eroare va Ã®mpiedica Tor Browser sÄ ajungÄ la site. DacÄ tot nu poÈi ajunge la serviciul onion, Ã®ncearcÄ mai tÃ¢rziu. E posibil sÄ fie o problemÄ temporarÄ de conexiune sau operatorii site-ului l-au deconectat fÄrÄ avertizare. </p><p class=\"mb-3\">PoÈi sÄ te asiguri cÄ alte servicii onion sunt accesibile conectÃ¢ndu-te la serviciul onion al <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>.</p>" + } +} diff --git a/ru.json b/ru.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ru.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ru(a)petr1708.json b/ru(a)petr1708.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ru(a)petr1708.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/scn.json b/scn.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/scn.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sco.json b/sco.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sco.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/si_LK.json b/si_LK.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/si_LK.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sk.json b/sk.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sk.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sk_SK.json b/sk_SK.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sk_SK.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sl.json b/sl.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sl.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sl_SI.json b/sl_SI.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sl_SI.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sn.json b/sn.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sn.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/so.json b/so.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/so.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/son.json b/son.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/son.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sq.json b/sq.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sq.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sr.json b/sr.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sr.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sr(a)latin.json b/sr(a)latin.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sr(a)latin.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/st.json b/st.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/st.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/su.json b/su.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/su.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/support-connecting.json b/support-connecting.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/support-connecting.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sv.json b/sv.json new file mode 100644 index 000000000..aab10f833 --- /dev/null +++ b/sv.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "connecting-2": { + "id": "#connecting-2", + "control": "connecting-2", + "title": "Jag har problem med att ansluta till Tor, och jag kan inte ta reda pÃ¥ vad som Ã€r fel.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "Jag kan inte nÃ¥ X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/sw.json b/sw.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/sw.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/szl.json b/szl.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/szl.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ta.json b/ta.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ta.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/te.json b/te.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/te.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/te_IN.json b/te_IN.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/te_IN.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/tg.json b/tg.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/tg.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/th.json b/th.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/th.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ti.json b/ti.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ti.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/tk.json b/tk.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/tk.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/tr.json b/tr.json new file mode 100644 index 000000000..5764bebf6 --- /dev/null +++ b/tr.json @@ -0,0 +1,20 @@ +{ + "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.", + "description": "<p class=\"mb-3\">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Ä±na<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser KÄ±lavuzu</a></mark> sayfasÄ±ndan ulaÅÄ±n.</p>" + }, + "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", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/tzm.json b/tzm.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/tzm.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ug(a)Arab.json b/ug(a)Arab.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ug(a)Arab.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/uk.json b/uk.json new file mode 100644 index 000000000..32a35f4fc --- /dev/null +++ b/uk.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-1", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-1", + "title": "ÐÑÐ°ÑÐ·ÐµÑ Tor ÐœÐµ Ð±ÑÐŽÐµ Ð¿ÑÐŽ'ÑÐŽÐœÑÐ²Ð°ÑÐžÑÑ, Ð°Ð»Ðµ ÑÐµ, Ð·ÐŽÐ°ÑÑÑÑÑ, ÐœÐµ Ñ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐŸÑ Ð· ÑÐµÐœÐ·ÑÑÐŸÑ.", + "description": "<p class=\"mb-3\">ÐÐŽÐœÑÑÑ Ð· ÐœÐ°Ð¹Ð±ÑÐ»ÑÑ Ð¿ÐŸÑÐžÑÐµÐœÐžÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒ, ÑÐŸ Ð¿ÑÐžÐ·Ð²ÐŸÐŽÑÑÑ ÐŽÐŸ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ñ Ð±ÑÐ°ÑÐ·ÐµÑÑ Tor, Ñ ÐœÐµÐ¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐ¹ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº. ÐÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÑ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÑÐ° ÑÐ°ÑÐŸÐ²ÐžÐ¹ Ð¿ÐŸÑÑ Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÑ ÑÐŸÑÐœÐŸ. Ð¯ÐºÑÐŸ ÑÐµ ÐœÐµ Ð²ÐžÑÑÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ, Ð¿ÐµÑÐµÐ³Ð»ÑÐœÑÑÐµ ÑÑÐŸÑÑÐœÐºÑ ÑÑÑÐœÐµÐœÐœÑ ÐœÐµÐ¿ÐŸÐ»Ð°ÐŽÐŸÐº Ñ <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Ð¿ÐŸÑÑÐ±ÐœÐžÐºÑ ÐºÐŸÑÐžÑÑÑÐ²Ð°ÑÐ° Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor</a></mark>.</p>" + }, + "connecting-2": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-2", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-2", + "title": "Ð£ ÐŒÐµÐœÐµ Ð²ÐžÐœÐžÐºÐ»Ð° Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ ÐŽÐŸ Tor, Ñ Ñ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÑÐŸÐ·ÑÐŒÑÑÐž, ÑÐŸ ÐœÐµ ÑÐ°Ðº.", + "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð²Ð°Ñ Ð²ÐžÐœÐžÐºÐ»Ðž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐž Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ, Ð²ÐžÐ±ÐµÑÑÑÑ ÐŸÐ¿ÑÑÑ Â«ÐºÐŸÐ¿ÑÑÐ²Ð°ÑÐž Ð¶ÑÑÐœÐ°Ð» Tor Ñ Ð±ÑÑÐµÑ ÐŸÐ±ÐŒÑÐœÑÂ». ÐÐŸÑÑÐŒ Ð²ÑÑÐ°Ð²ÑÐµ Ð¶ÑÑÐœÐ°Ð» Tor Ñ ÑÐµÐºÑÑÐŸÐ²ÐžÐ¹ ÑÐ°Ð¹Ð» Ð°Ð±ÐŸ ÑÐœÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. ÐÐž ÐŒÐ°ÑÑÐµ Ð¿ÐŸÐ±Ð°ÑÐžÑÐž ÐŸÐŽÐœÑ Ð· ÑÐžÑ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ (ÑÑÐºÐ°Ð¹ÑÐµ ÐœÐ°ÑÑÑÐ¿ÐœÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor):</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â1: ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ð· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐŸÐŒ</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p> <p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS. Ð¯ÐºÑÐŸ ÐŽÐ»Ñ ÐœÐ°Ð»Ð°ÑÑÑÐ²Ð°ÐœÐœÑ ÐŒÐµÑÐµÐ¶Ñ Ð¿ÐŸÑÑÑÐ±ÐµÐœ Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑ SOCKS, Ð±ÑÐŽÑ Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž ÑÐœÑÐŸÑÐŒÐ°ÑÑÑ Ð¿ÑÐŸ Ð¿ÑÐŸÐºÑÑ. Ð¯ÐºÑÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS ÐœÐµ Ð¿ÐŸÑÑÑÐ±ÐœÐžÐ¹, Ð°Ð±ÐŸ Ð²Ðž ÐœÐµ Ð²Ð¿ÐµÐ²ÐœÐµÐœÑ, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÐŒÐµÑÐµÐ¶Ñ Tor Ð±ÐµÐ· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐ° SOCKS.<p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â2: ÐÐµ Ð²ÐŽÐ°ÑÑÑÑÑ Ð ŽÑÑÑÐ°ÑÐžÑÑ Ð±ÐµÐ·Ð¿ÐµÑÐœÐžÑ Ð¿ÐµÑÐµÐŽÐ°Ð²Ð°ÑÑÐ²</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð¶ÑÑÐœÐ°Ð»Ñ Tor Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž, ÑÐŸ ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°ÑÐŸÐŒÑ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÐµÑÑÐŸÐ³ÐŸ Ð²ÑÐ·Ð»Ð° Ð² Ð»Ð°ÐœÑÑÐ·Ñ Tor. ÐŠÐµ ÐŒÐŸÐ¶Ðµ ÐŸÐ·ÐœÐ°ÑÐ°ÑÐž, ÑÐŸ Ð²Ðž Ð¿ÐµÑÐµÐ±ÑÐ²Ð°ÑÑÐµ Ñ ÐŒÐµÑÐµÐ¶Ñ, ÑÐºÐ° Ð¿ÑÐŽÐŽÐ°ÑÑÑÑÑ ÑÐµÐœÐ·ÑÑÑ. ÐÑÐŽÑ Ð»Ð°ÑÐºÐ°, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽÐºÐ»ÑÑÐžÑÐžÑÑ ÐŽÐŸ ÐŒÐŸÑ ÑÑÐ², Ñ ÑÐµ ÐŒÐ°Ñ Ð²ÐžÑÑÑÐžÑÐž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ.</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â3: ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð·Ð°Ð²ÐµÑÑÐžÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð²ÐžÐºÐŸÐœÐ°ÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS Ð·Ð° ÐŽÐŸÐ¿ÐŸÐŒÐŸÐ³ÐŸÑ ÑÐ»ÑÐ¶Ð± ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ñ. ÐÐžÐºÐŸÑÐžÑÑÐ°ÐœÐœÑ ÐŒÐŸÑÑÑÐ², ÑÐ²ÐžÐŽÑÐµ Ð·Ð° Ð²ÑÐµ, Ð±ÑÐŽÐµ Ð²ÐžÐ¿ÑÐ°Ð²Ð»ÑÑÐž ÑÐµ.</p><h5> ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â4: Ð·Ð±ÐžÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°Ñ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÐœÐµÐ¿Ñ Ð°Ð²ÐžÐ»ÑÐœÐžÐ¹. ÐÑÐŽÑ-Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÐ¹ ÑÐŸÑÐœÐŸ, Ð²ÐºÐ»ÑÑÐœÐŸ Ð· Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐŒ ÑÐ°ÑÐŸÐ²ÐžÐŒ Ð¿ÐŸÑÑÐŸÐŒ. ÐÐŸÑÑÐŒ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÑÑÑ Tor.</p>" + }, + "connecting-3": { + "id": "#Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-3", + "control": "Ð·'ÑÐŽÐœÐ°ÐœÐœÑ-3", + "title": "Ð¯ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÐœÐ°Ð¹ÑÐž X.onion!", + "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð·ÐœÐ°Ð¹ÑÐž ÑÐ»ÑÐ¶Ð±Ñ onion, ÑÐºÑ Ð²Ðž Ð±Ð°Ð¶Ð°ÑÑÐµ, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž 16-ÑÐžÐŒÐ²ÐŸÐ»ÑÐœÑ onion-Ð°ÐŽÑÐµÑÑ: ÐœÐ°Ð²ÑÑÑ ÐœÐµÐ²ÐµÐ»ÐžÐºÐ° Ð¿ÐŸÐŒÐžÐ»ÐºÐ° ÐœÐµ ÐŽÐŸÐ·Ð²ÐŸÐ»ÐžÑÑ Tor Browser Ð·Ð°Ð¹ÑÐž ÐœÐ° ÑÐ°Ð¹Ñ. Ð¯ÐºÑÐŸ Ð²Ðž Ð²ÑÐµ Ð¶ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÑÐ»ÑÐ¶Ð± onion, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐ·ÐœÑÑÐµ. ÐÐŸÐ¶Ðµ ÑÑÐ°Ð¿ÐžÑÐžÑÑ Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° ÑÐžÐŒÑÐ°ÑÐŸÐ²ÐŸÐ³ÐŸ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑ, Ð°Ð±ÐŸ ÐŸÐ¿ÐµÑÐ°ÑÐŸÑÐž ÑÐ°Ð¹ÑÑ ÐŒÐŸÐ¶ÑÑÑ ÐŽÐŸÐ·Ð²ÐŸÐ»ÐžÑÐž Ð¹ÐŸÐŒÑ Ð²ÐžÑÐŸÐŽÐžÑÐž Ð² Ð°Ð²ÑÐŸÐœÐŸÐŒÐœÐžÐ¹ ÑÐµÐ¶ÐžÐŒ Ð±ÐµÐ· Ð¿ÐŸÐ¿ÐµÑÐµÐŽÐ¶ÐµÐœÐœÑ.</p><p class=\"mb-3\">ÐÐž ÑÐ°ÐºÐŸÐ¶ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐµÑÐµÐºÐŸÐœÐ°ÑÐžÑÑ, ÑÐŸ Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐžÐŒÐ°ÑÐž ÐŽÐŸÑÑÑÐ¿ ÐŽÐŸ ÑÐœÑÐžÑ Ð¿ÐŸÑÐ»ÑÐ³ onion, Ð¿ÑÐŽ'ÑÐŽÐœÐ°Ð²ÑÐžÑÑ ÐŽÐŸ ÑÐ»ÑÐ¶Ð±Ðž Onion ÐœÐ° <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</ a>.</p>" + } +} diff --git a/ur.json b/ur.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ur.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ur_PK.json b/ur_PK.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ur_PK.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/uz.json b/uz.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/uz.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/ve.json b/ve.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/ve.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/vi.json b/vi.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/vi.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/wa.json b/wa.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/wa.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/wo.json b/wo.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/wo.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/zh_CN.json b/zh_CN.json new file mode 100644 index 000000000..d2f692083 --- /dev/null +++ b/zh_CN.json @@ -0,0 +1,20 @@ +{ + "connecting-1": { + "id": "#è¿æ¥-1", + "control": "è¿æ¥-1", + "title": "Toræµè§åšæ²¡æè¿æ¥äžäºèçœïŒäœè¿äŒŒä¹å¹¶äžæ¯å äžºçœç»ç®¡æ§é æçé®é¢ã", + "description": "<p class=\"mb-3\">é æTorè¿æ¥å€±èŽ¥çæåžžè§çé®é¢ä¹äžæ¯ç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçç³»ç»æ¶éŽä»¥åæ¶åºè®Ÿçœ®æ£ç¡®ãåŠæè¿äžªé®é¢è¿æ²¡æè¢«è§£å³ïŒè¯·æ¥çäœäº<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Toræµè§åšæå</a></mark>çæéææ¥çé¢ã</p>" + }, + "connecting-2": { + "id": "#è¿æ¥-2", + "control": "è¿æ¥-2", + "title": "æ æ³è¿æ¥å° TorïŒæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", + "description": "<p class=\"mb-3\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥ </h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæ šçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§éè¯¯#3: TLSæ¡æå€±èŽ¥ </h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor äžäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿ çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5>åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯ <pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n ToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœã</code></pre></p><p class=\"mb-3\">è¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ãåŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" + }, + "connecting-3": { + "id": "#è¿æ¥-3", + "control": "è¿æ¥-3", + "title": "ææ æ³è®¿é®X.onionïŒ", + "description": "<p class=\"mb-3\">åŠææšæ æ³è®¿é®æŽè±ç«ç¹ïŒè¯·ç¡®è®€æšèŸå¥äºæ£ç¡®çïŒ16äœççœåïŒå³äœ¿äžäžªåŸ®å°çéè¯¯ä¹äŒé»æ¢Toræµè§åšè®¿é®è¿äžªç«ç¹ãåŠææšè¿æ¯æ æ³è®¿é®è¿äžªçœç«ïŒè¯·çšåéè¯ãè¿å¯èœæ¯ææ¶æ§çé®é¢ïŒæèçœç«ç®¡çåæªç»åºæ ç€ºå°±äžçº¿äºçœç«ã</p><p class=\"mb-3\">æšä¹å¯ä»¥éè¿è®¿é®<a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>çæŽè±ç«ç¹æ¥ç¡®è®€æšçæµè§åšéçœ®æ£ç¡®ã" + } +} diff --git a/zh_HK.json b/zh_HK.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/zh_HK.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/zh_TW.json b/zh_TW.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/zh_TW.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +} diff --git a/zu.json b/zu.json new file mode 100644 index 000000000..cac143183 --- /dev/null +++ b/zu.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": "<p class=\"mb-3\">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 <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "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": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "connecting-3": { + "id": "#connecting-3", + "control": "connecting-3", + "title": "I cannot reach X.onion!", + "description": "<p class=\"mb-3\">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.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\">DuckDuckGo</a>'s âOnion Service.</p>" + } +}

1 0

[translation-tools/master] Add support-censorship
by colin＠torproject.org 06 Apr '18

06 Apr '18

commit 10cfa1e0bcdedb8b8ac59b5588525dc4d6d49de4 Author: Colin Childs <colin(a)torproject.org> Date: Fri Apr 6 18:32:03 2018 -0500 Add support-censorship --- config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config b/config index dd9a27f..064aa29 100644 --- a/config +++ b/config @@ -36,7 +36,7 @@ tor-messenger-privproperties tor-messenger-privproperties_completed tor-messenger-uiproperties tor-messenger-uiproperties_completed tails-greeter-2 tails-greeter-2_completed exoneratorproperties exoneratorproperties_completed tor-browser-manual -tor-browser-manual_completed" +tor-browser-manual_completed support-censorship support-censorship_completed" PIDFILE=/srv/translation.torproject.org/run/update_translations.pid

1 0

[translation/support-censorship_completed] pulling translations from transifex
by translation＠torproject.org 06 Apr '18

06 Apr '18

commit 9042cd7d2912bb6861743ee6f9ca781f4726df29 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Apr 6 23:30:07 2018 +0000 pulling translations from transifex --- bn_BD.json | 40 ++++++++++++++++++++++++++++++++++++++++ de.json | 40 ++++++++++++++++++++++++++++++++++++++++ es.json | 40 ++++++++++++++++++++++++++++++++++++++++ fr.json | 40 ++++++++++++++++++++++++++++++++++++++++ id.json | 40 ++++++++++++++++++++++++++++++++++++++++ ja.json | 40 ++++++++++++++++++++++++++++++++++++++++ nl.json | 40 ++++++++++++++++++++++++++++++++++++++++ pt_BR.json | 40 ++++++++++++++++++++++++++++++++++++++++ support-censorship.json | 40 ++++++++++++++++++++++++++++++++++++++++ zh_CN.json | 40 ++++++++++++++++++++++++++++++++++++++++ 10 files changed, 400 insertions(+) diff --git a/bn_BD.json b/bn_BD.json new file mode 100644 index 000000000..d5005ce06 --- /dev/null +++ b/bn_BD.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-1", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-1", + "title": "àŠàŠ®àŠŸàŠŠà§àŠ° àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠ àŠàŠàŠàŠ¿ àŠžà§àŠšà§àŠžàŠ° àŠŠà§àŠ¬àŠŸàŠ°àŠŸ àŠàŠ¬àŠ°à§àŠŠà§àŠ§ àŠ¹àŠ¯àŠŒà¥€ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠ¿ àŠàŠ®àŠŸàŠŠà§àŠ° àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠžàŠŸàŠ¹àŠŸàŠ¯à§àŠ¯ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§àŠš?", + "description": "<p class=\"mb-3\">àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠ¬àŠ¶à§àŠ¯àŠ àŠ®àŠŸàŠšà§àŠ·àŠà§ àŠžàŠŸàŠ¹àŠŸàŠ¯à§àŠ¯ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§ àŠàŠªàŠšàŠŸàŠ° àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠà§ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°àŠ€à§ àŠ¯à§àŠàŠŸàŠšà§ àŠàŠàŠ¿ àŠàŠ¬àŠ°à§àŠŠà§àŠ§ àŠ°àŠ¯àŠŒà§àŠà§à¥€àŠ¬à§àŠ¶àŠ¿àŠ°àŠàŠŸàŠ àŠžàŠ®àŠ¯àŠŒ,<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\"> àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠ¡àŠŸàŠàŠšàŠ²à§àŠ¡ àŠàŠ°àŠŸ </a></mark>àŠàŠ¬àŠ àŠ€àŠŸàŠ°àŠªàŠ° àŠàŠàŠ¿ àŠ¬à§àŠ²àŠ àŠàŠ°àŠŸ àŠžàŠŸàŠàŠà§ àŠšà§àŠàŠ¿àŠà§àŠ àŠàŠ°àŠŸàŠ° àŠàŠšà§àŠ¯ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠžà§àŠ° àŠàŠšà§àŠ®àŠ€àŠ¿ àŠŠà§àŠ¬à§à¥€ àŠ¯à§ àŠàŠŸàŠ¯àŠŒàŠàŠŸàŠ¯àŠŒ àŠªà§àŠ°àŠà§àŠ° àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª àŠ°àŠ¯àŠŒà§àŠà§, àŠ€àŠŸ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠžà§àŠ° àŠàŠšà§àŠ¯ àŠàŠ®àŠŸàŠŠà§àŠ° àŠàŠŸàŠà§ àŠªà§àŠ°àŠà§àŠ° àŠªàŠ°àŠ¿àŠ®àŠŸàŠ£à§ àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª àŠªà§àŠ°àŠ€àŠŸàŠ°àŠ£àŠŸ àŠ¬àŠ¿àŠàŠ²à§à Šª àŠàŠà§, <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">àŠªà§àŠ²à§àŠ¯àŠŸàŠà§àŠ¬àŠ² àŠà§àŠ°àŠŸàŠšà§àŠžàŠªà§àŠ°à§àŠàŠà§àŠ²àŠ¿ àŠžàŠ¹ àŠàŠ®àŠš</a></mark>à¥€àŠàŠ°à§ àŠ€àŠ¥à§àŠ¯à§àŠ° àŠàŠšà§àŠ¯, àŠŠà§àŠà§àŠš àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠàŠàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ²<a href=\"https://tb-manual.torproject.org/en-US/\"><mark> àŠ¬àŠ¿àŠàŠŸàŠ<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\"> àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠªà§àŠ° àŠàŠªàŠ°</a></mark>à¥€</p>" + }, + "censorship-2": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-2", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-2", + "title": "àŠàŠ®àŠŸàŠ° àŠªà§àŠ°àŠ¿àŠ¯àŠŒ àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠ àŠàŠ° àŠªàŠ°à§àŠ¯àŠšà§àŠ€ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ¬àŠ°à§àŠŠà§àŠ§ àŠàŠ°àŠà§", + "description": "<p class=\"mb-3\">àŠ¶à§àŠšà§ àŠŠà§àŠàŠàŠ¿àŠ€ àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠ¯à§ àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠàŠàŠ¿ àŠàŠŸàŠš àŠ€àŠŸ àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠ°àŠ¬à§àŠš àŠšàŠŸ! àŠàŠàŠšàŠ àŠàŠàŠšàŠ àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠàŠ¬àŠ°à§àŠ§ àŠàŠ°àŠ¬à§ àŠàŠŸàŠ°àŠ£ àŠ€àŠŸàŠ°àŠŸ àŠàŠ¡àŠŒ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§ àŠàŠ¬àŠ àŠžà§àŠ¬àŠ¯àŠŒàŠàŠà§àŠ°àŠ¿àŠ¯àŠŒ àŠà§àŠ°à§àŠ¯àŠŸàŠ«àŠ¿àŠà§àŠ° àŠ®àŠ§à§àŠ¯à§ àŠªàŠŸàŠ°à§àŠ¥àŠà§àŠ¯ àŠ¬àŠ²àŠ€à§ àŠªàŠŸàŠ°à§ àŠšàŠŸà¥€ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠàŠ¬àŠ°à§àŠ§ àŠàŠ°àŠŸ àŠžàŠŸàŠàŠàŠà§àŠ²à§àŠ€à§ àŠàŠ®àŠ°àŠŸ àŠ¯à§ àŠžàŠ«àŠ²àŠ€àŠŸ àŠªà§àŠ¯àŠŒà§àŠàŠ¿ àŠ€àŠŸ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠžàŠŸàŠàŠà§ àŠžàŠ°àŠŸàŠžàŠ°àŠ¿ àŠªà§àŠ°àŠ¶àŠŸàŠžàŠà§àŠ° àŠžàŠŸàŠ¥à§ àŠ¯à§àŠàŠŸàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§à¥€ àŠàŠ àŠ§àŠ°àŠ£à§àŠ° àŠàŠ¿àŠà§ àŠ¹àŠ¯àŠŒàŠ€à§ àŠàŠ àŠà§àŠ¶àŠ²àŠàŠ¿ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ °à§: \"àŠ¹àŠŸàŠ! àŠàŠ®àŠ¿ àŠàŠŸàŠ¯àŠŒàŠŸàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°àŠŸàŠ° àŠžàŠ®àŠ¯àŠŒ àŠàŠªàŠšàŠŸàŠ° àŠžàŠŸàŠàŠ xyz.com àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°àŠŸàŠ° àŠà§àŠ·à§àŠàŠŸ àŠàŠ°à§àŠàŠ¿ àŠàŠ¬àŠ àŠàŠ¬àŠ¿àŠ·à§àŠàŠŸàŠ° àŠàŠ°à§àŠàŠ¿ àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠàŠªàŠšàŠŸàŠ° àŠžàŠŸàŠàŠ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°àŠŸàŠ° àŠàŠšà§àŠ®àŠ€àŠ¿ àŠŠàŠ¿àŠà§àŠà§àŠš àŠšàŠŸà¥€ àŠàŠ®àŠ¿ àŠàŠªàŠšàŠŸàŠà§ àŠàŠ àŠžàŠ¿àŠŠà§àŠ§àŠŸàŠšà§àŠ€à§àŠ° àŠªà§àŠšàŠ°à§àŠ¬àŠ¿àŠ¬à§àŠàŠšàŠŸ àŠàŠ°àŠŸàŠ° àŠàŠšà§àŠ°à§àŠ§ àŠàŠ°àŠàŠ¿; àŠžàŠŸàŠ°àŠŸ àŠ¬àŠ¿àŠ¶à§àŠ¬à§àŠ° àŠ®àŠŸàŠšà§àŠ· àŠ€àŠŸàŠŠà§àŠ° àŠà§àŠªàŠšà§àŠ¯àŠŒàŠ€àŠŸ àŠ°àŠà§àŠ·àŠŸ àŠàŠ¬àŠ àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠªà§àŠ° àŠ¬àŠ¿àŠ°à§àŠŠà§àŠ§à§ àŠ²àŠ¡àŠŒàŠŸàŠ àŠàŠ°à§à¥€ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠ¬à§àŠ²àŠ àŠàŠ°à§, àŠàŠªàŠšàŠ¿ àŠžàŠ®à§àŠàŠ¬àŠ€ àŠŠàŠ®àŠšàŠ®à§àŠ²àŠ àŠŠà§àŠ¶àŠà§àŠ²àŠ¿àŠ€à§ àŠ² à§àŠà§àŠŠà§àŠ°àŠà§ àŠ¬à§àŠ²àŠ àŠàŠ°à§ àŠŠàŠ¿àŠà§àŠà§àŠš àŠ¯àŠŸàŠ°àŠŸ àŠàŠàŠàŠ¿ àŠ«à§àŠ°àŠ¿ àŠàŠšà§àŠàŠŸàŠ°àŠšà§àŠ, àŠžàŠŸàŠàŠ¬àŠŸàŠŠàŠ¿àŠ àŠàŠ¬àŠ àŠàŠ¬à§àŠ·àŠ àŠ¯àŠŸàŠ°àŠŸ àŠšàŠ¿àŠà§àŠŠà§àŠ° àŠàŠ¬àŠ¿àŠ·à§àŠàŠŸàŠ°, àŠ¹à§àŠàŠžàŠ² àŠ¬à§àŠ²à§àŠ¯àŠŒàŠŸàŠ°, àŠà§àŠ¯àŠŸàŠà§àŠàŠ¿àŠàŠ¿àŠžà§àŠ, àŠàŠ¬àŠ àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ®àŠŸàŠšà§àŠ· àŠ¯àŠŸàŠ°àŠŸ àŠàŠà§àŠ°àŠ®àŠ£àŠŸàŠ€à§àŠ®àŠ àŠ€à§àŠ€à§àŠ¯àŠŒ àŠªàŠà§àŠ·à§àŠ° àŠà§àŠ°à§àŠ¯àŠŸàŠàŠ¿àŠ àŠ¥à§àŠà§ àŠàŠªà§àŠ àŠàŠàŠ àŠàŠ°àŠ€à§ àŠàŠŸàŠš àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠ¡àŠ¿àŠàŠ¿àŠàŠŸàŠ² àŠà§àŠªàŠšà§àŠ¯àŠŒàŠ€àŠŸ àŠàŠ¬àŠ àŠàŠšà§àŠàŠŸàŠ°àŠšà§àŠ àŠžà§àŠ¬àŠŸàŠ§à§àŠšàŠ€àŠŸàŠ° àŠªàŠà§àŠ·à§ àŠŠà§àŠ¢àŠŒ àŠàŠ¬àŠžà§àŠ¥àŠŸàŠš àŠšàŠ¿àŠš àŠàŠ¬àŠ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° xyz.com àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠžà§àŠ° àŠàŠšà§àŠ®àŠ€àŠ¿ àŠŠàŠ¿àŠšà¥€ àŠ§àŠšà§àŠ¯àŠ¬àŠŸàŠŠà¥€ \"àŠ¬à§àŠ¯àŠŸàŠàŠàŠà§àŠ²àŠ¿àŠ° àŠà§àŠ·à§àŠ€à§àŠ°à§ àŠàŠ¬àŠ àŠàŠšà§àŠ¯àŠ ŸàŠšà§àŠ¯ àŠžàŠàŠ¬à§àŠŠàŠšàŠ¶à§àŠ² àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠàŠà§àŠ²àŠ¿, àŠàŠàŠ¿ àŠà§àŠà§àŠ²-àŠàŠ¿àŠ€à§àŠ€àŠ¿àŠ àŠ¬à§àŠ²àŠàŠ¿àŠ àŠŠà§àŠàŠ€à§ àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ (àŠ¯àŠŠàŠ¿ àŠàŠàŠàŠ¿ àŠ¬à§àŠ¯àŠŸàŠàŠ àŠàŠŸàŠšà§ àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠžàŠŸàŠ§àŠŸàŠ°àŠ£àŠ€ àŠàŠ àŠŠà§àŠ¶ àŠ¥à§àŠà§ àŠ€àŠŸàŠŠà§àŠ° àŠªàŠ°àŠ¿àŠ·à§àŠ¬àŠŸàŠà§àŠ²àŠ¿ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°à§àŠš, àŠàŠ¬àŠ àŠ¹àŠ àŠŸà§ àŠàŠªàŠšàŠ¿ àŠ¬àŠ¿àŠ¶à§àŠ¬à§àŠ° àŠàŠšà§àŠ¯ àŠªà§àŠ°àŠŸàŠšà§àŠ€à§ àŠàŠàŠàŠ¿ àŠªà§àŠ°àŠžà§àŠ¥àŠŸàŠš àŠ°àŠ¿àŠ²à§ àŠ¥à§àŠà§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠà§àŠš, àŠàŠªàŠšàŠŸàŠ° àŠà§àŠ¯àŠŸàŠàŠŸàŠàŠšà§àŠ àŠ²àŠ àŠàŠ°àŠŸ àŠ¹àŠ€à§ àŠªàŠŸàŠ°à§ àŠ¬àŠŸàŠžà§àŠ¥àŠàŠ¿àŠ€). àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠàŠàŠ¿ àŠªà§àŠàŠ¯àŠŒàŠŸàŠ àŠªàŠ°àŠ¿àŠ·à§àŠ¬àŠŸ àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠàŠà§àŠ·àŠ® àŠ¹àŠš, àŠ€àŠ¬à§ àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠŠà§àŠà§àŠš àŠàŠ®àŠ¿ X.onion àŠ€à§ àŠªà§àŠàŠàŠŸàŠ€à§ àŠªàŠŸàŠ°àŠ¿ àŠšàŠŸ!" + }, + "censorship-3": { + "id": "#àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-3", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-3", + "title": "Torproject.org àŠ¬à§àŠ²àŠ àŠàŠ°àŠ²à§ àŠàŠ®àŠ¿ àŠàŠ¿àŠàŠŸàŠ¬à§ àŠàŠ° àŠ¡àŠŸàŠàŠšàŠ²à§àŠ¡ àŠàŠ°àŠ¬?", + "description": "<p class=\"mb-3\">àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠ®àŠŸàŠŠà§àŠ°<mark><a href=\"https://www.torproject.org\"> àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠà§àŠ° àŠ®àŠŸàŠ§à§àŠ¯àŠ®à§</a></mark> àŠàŠ° àŠ¡àŠŸàŠàŠšàŠ²à§àŠ¡ àŠàŠ°àŠ€à§ àŠšàŠŸ àŠªàŠŸàŠ°à§àŠš, àŠàŠªàŠšàŠ¿ GetTor àŠàŠ° àŠ®àŠŸàŠ§à§àŠ¯àŠ®à§ àŠàŠªàŠšàŠŸàŠà§ àŠ¬àŠ¿àŠ€àŠ°àŠ£ àŠàŠ°àŠŸ àŠàŠ° àŠàŠàŠàŠ¿ àŠàŠªàŠ¿ àŠªà§àŠ€à§ àŠªàŠŸàŠ°à§àŠšà¥€ GetTor àŠ¹àŠ² àŠàŠàŠàŠ¿ àŠªàŠ°àŠ¿àŠ·à§àŠ¬àŠŸ àŠ¯àŠŸ àŠžà§àŠ¬àŠ¯àŠŒàŠàŠà§àŠ°àŠ¿àŠ¯àŠŒàŠàŠŸàŠ¬à§ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ°à§àŠ° àŠžàŠ°à§àŠ¬àŠ¶à§àŠ· àŠžàŠàŠžà§àŠàŠ°àŠ£à§ àŠ²àŠ¿àŠàŠàŠ¯à§àŠà§àŠ€ àŠ¬àŠŸàŠ°à§àŠ€àŠŸàŠà§àŠ²àŠ¿àŠ€à§ àŠªà§àŠ°àŠ€àŠ¿àŠà§àŠ°àŠ¿àŠ¯àŠŒàŠŸ àŠŠà§àŠ¯àŠŒ, àŠ¬àŠ¿àŠàŠ¿àŠšà§àŠš àŠžà§àŠ¥àŠŸàŠšà§ àŠàŠ¬àŠžà§àŠ¥àŠŸàŠš àŠšà§àŠ¯àŠŒ àŠ¯àŠŸ àŠžà§àŠšà§àŠžàŠ° àŠ¹àŠàŠ¯àŠŒàŠŸàŠ° àŠžàŠ®à§àŠàŠŸàŠ¬àŠšàŠŸ àŠàŠ® àŠ¥àŠŸàŠà§, àŠ¯à§àŠ®àŠš àŠ¡à§àŠ°àŠªàŠ¬àŠà§àŠž, Google àŠ¡à§àŠ°àŠŸàŠàŠ, àŠàŠ¬àŠ àŠàŠ¿àŠ¥àŠŸàŠ¬à¥€</p>" + }, + "censorship-4": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª -4", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª -4", + "title": "àŠàŠ®àŠ¿ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ°à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°àŠàŠ¿ àŠšàŠŸ, àŠàŠ®àŠŸàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠ àŠžà§àŠšà§àŠžàŠ° àŠàŠ°àŠŸ àŠ¹àŠ¯àŠŒà§àŠà§?", + "description": "<p class=\"mb-3\">àŠàŠªàŠšàŠ¿ àŠàŠàŠàŠ¿ àŠžà§àŠšà§àŠžàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§ àŠ¹àŠ€à§ àŠªàŠŸàŠ°à§àŠš, àŠàŠ¬àŠ àŠ€àŠŸàŠ àŠàŠªàŠšàŠŸàŠ° àŠžà§àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°à§ àŠà§àŠ·à§àŠàŠŸ àŠàŠ°àŠŸ àŠàŠàŠ¿àŠ€à¥€ àŠàŠ¿àŠà§ àŠ¬à§àŠ°àŠ¿àŠ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠ° àŠ®àŠ§à§àŠ¯à§ àŠšàŠ¿àŠ°à§àŠ®àŠ¿àŠ€ àŠ¹àŠ¯àŠŒ, àŠàŠ¬àŠ àŠàŠªàŠšàŠ¿ àŠàŠ° àŠ²àŠà§àŠàŠŸàŠ° àŠàŠàŠšà§àŠ¡à§àŠ€à§ \"àŠàŠšàŠ«àŠ¿àŠàŠŸàŠ°\" (àŠ€àŠŸàŠ°àŠªàŠ° àŠªà§àŠ°àŠ®à§àŠªàŠ àŠàŠšà§àŠžàŠ°àŠ£) àŠšàŠ¿àŠ°à§àŠ¬àŠŸàŠàŠš àŠàŠ°à§ àŠžà§àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§àŠš àŠ¯àŠŸ àŠàŠªàŠšàŠ¿ àŠ¯àŠàŠš àŠªà§àŠ°àŠ¥àŠ®àŠ¬àŠŸàŠ°à§àŠ° àŠàŠšà§àŠ¯ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠà§àŠ²à§àŠš àŠ€àŠàŠš àŠªàŠª-àŠàŠª àŠ¹àŠ¿àŠžà§àŠ¬à§ àŠàŠžà§à¥€ àŠàŠªàŠšàŠŸàŠ° àŠ¯àŠŠàŠ¿ àŠàŠšà§àŠ¯àŠŸàŠšà§àŠ¯ àŠžà§àŠ€à§àŠ° àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš àŠ¹àŠ¯àŠŒ, àŠ€àŠŸàŠ¹àŠ²à§ àŠàŠªàŠšàŠ¿ <mark><a href=\"https://bridges.torproject.or g/\">àŠàŠ®àŠŸàŠŠà§àŠ° àŠ¬à§àŠ°àŠ¿àŠà§àŠž àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠà§ </a></mark>àŠ€àŠŸàŠŠà§àŠ° àŠªà§àŠ€à§ àŠªàŠŸàŠ°à§àŠšà¥€ àŠžà§àŠ€à§ àŠžàŠ®à§àŠªàŠ°à§àŠà§ àŠàŠ°àŠ àŠ€àŠ¥à§àŠ¯à§àŠ° àŠàŠšà§àŠ¯, <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ² àŠŠà§àŠà§àŠš</a></mark>à¥€</p>" + }, + "censorship-5": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-5", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-5", + "title": "àŠàŠ®àŠ¿ àŠàŠ° àŠžàŠàŠ¯à§àŠà§ àŠžàŠ®àŠžà§àŠ¯àŠŸ àŠ¹àŠà§àŠà§, àŠàŠ¬àŠ àŠàŠ®àŠ¿ àŠàŠ¿ àŠà§àŠ² àŠ¬à§àŠàŠ€à§ àŠªàŠŸàŠ°àŠàŠ¿ àŠšàŠŸà¥€", + "description": "<p class=\"mb-3\">àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠžàŠàŠ¯à§àŠà§àŠ° àŠžàŠ®àŠžà§àŠ¯àŠŸ àŠ¹àŠ¯àŠŒ àŠ€àŠ¬à§ àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ \"àŠàŠ° àŠ²àŠ àŠà§àŠ²àŠ¿àŠªàŠ¬à§àŠ°à§àŠ¡à§ àŠàŠªàŠ¿ àŠàŠ°à§àŠš\" àŠ¬àŠ¿àŠàŠ²à§àŠªàŠàŠ¿ àŠšàŠ¿àŠ°à§àŠ¬àŠŸàŠàŠš àŠàŠ°à§àŠšà¥€ àŠàŠ°àŠªàŠ° àŠàŠ° àŠ²àŠ àŠàŠàŠàŠ¿ àŠªàŠŸàŠ à§àŠ¯ àŠ«àŠŸàŠàŠ² àŠ¬àŠŸ àŠàŠšà§àŠ¯ àŠšàŠ¥àŠ¿àŠ€à§ àŠªà§àŠžà§àŠ àŠàŠ°à§àŠšà¥€ àŠàŠªàŠšàŠ¿ àŠàŠ àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿àŠà§àŠ²àŠ¿àŠ° àŠàŠàŠàŠ¿ àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠ¬à§àŠš (àŠàŠªàŠšàŠŸàŠ° àŠàŠ° àŠ²àŠàŠà§àŠ²àŠ¿àŠ€à§ àŠšàŠ¿àŠ®à§àŠšàŠ²àŠ¿àŠàŠ¿àŠ€ àŠ²àŠŸàŠàŠšàŠà§àŠ²àŠ¿ àŠŠà§àŠà§àŠš): <h5>àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿ # 1: àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠžàŠàŠ¯à§àŠ àŠ¬à§àŠ¯àŠ°à§àŠ¥àŠ€àŠŸ 2017-10-29 09:23:40.800 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] 127.0.0.1:9150 àŠàŠ° àŠàŠªàŠ° àŠžàŠà§àŠž àŠ²àŠ¿àŠžà§àŠšàŠŸàŠ° àŠàŠ°àŠ®à§àŠ àŠàŠ°à§àŠš\n2017-10-29 09: 23: 47.900 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] à Š¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 5%: àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠ¹àŠà§àŠà§\n 2017-10-29 09: 23: 47.900 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª àŠàŠ°àŠŸ 10%: àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠžàŠŸàŠ¥à§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠàŠ¿àŠ àŠžàŠ®àŠŸàŠªà§àŠ€ àŠàŠ°àŠŸ \n2017- 10-29 09: 24: 08.900 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠà§àŠ²àŠŸàŠ¯àŠŒà§àŠšà§àŠ: xx..xxx..xxx.xx: xxxxx (\"àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠžàŠàŠž àŠžàŠŸàŠ°à§àŠàŠŸàŠ° àŠ¬à§àŠ¯àŠ°à§àŠ¥àŠ€àŠŸ\") àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠàŠ°àŠ€à§ àŠàŠà§àŠ·àŠ®à¥€ 2017-10-29 09: 24: 08.900 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠ¡ ] àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠà§àŠ²àŠŸàŠ¯àŠŒà§àŠšà§àŠ: xx..xxx..xxx.xx: XXXxx àŠàŠ°(\"àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ SOCKS àŠžàŠŸàŠ°à§àŠàŠŸàŠ° àŠ¬à§àŠ¯àŠ°à§àŠ¥àŠ€àŠŸ\")àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠàŠ°àŠ€à§ àŠàŠà§àŠ·àŠ®à¥€\n2017-10-29 09: 24: 08.900 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠªà§àŠ°àŠà §àŠžàŠ¿ àŠà§àŠ²àŠŸàŠ¯àŠŒà§àŠšà§àŠ: xxx..xxx.xx: xxxxx (\"àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ SOCKS àŠžàŠŸàŠ°à§àŠàŠŸàŠ° àŠ¬à§àŠ¯àŠ°à§àŠ¥àŠ€àŠŸ\")<code><pre><p class=\"mb-3\"><p class=\"mb-3\">àŠàŠ° àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠàŠ°àŠ€à§ àŠàŠà§àŠ·àŠ®à¥€ àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° ââàŠ²àŠà§ àŠàŠ°àŠàŠ® àŠ²àŠŸàŠàŠš àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠš àŠ€àŠ¬à§ àŠàŠ° àŠ®àŠŸàŠšà§ àŠ¹àŠ² àŠàŠªàŠšàŠ¿ àŠàŠàŠàŠ¿ SOCKS àŠªà§àŠ°àŠà§àŠžàŠ¿àŠ€à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ°à§àŠ¥à¥€ àŠàŠªàŠšàŠŸàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠ àŠžà§àŠàŠàŠªà§àŠ° àŠàŠšà§àŠ¯ àŠàŠàŠàŠ¿ àŠžàŠà§àŠž àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš àŠ¹àŠ²à§, àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠšàŠ¿àŠ¶à§àŠàŠ¿àŠ€ àŠàŠ°à§àŠš àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠ¬àŠ¿àŠ¶àŠŠàŠà§àŠ²àŠ¿ àŠžàŠ àŠ¿àŠàŠàŠŸàŠ¬à§ àŠ²àŠ¿àŠà§àŠà§àŠšà¥€ àŠ¯àŠŠàŠ¿ àŠàŠàŠàŠ¿ àŠžàŠà§àŠž àŠªà§àŠ°àŠà§àŠžàŠ¿àŠ° àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš àŠšàŠŸ àŠ¹àŠ¯àŠŒ , àŠàŠ¥àŠ¬àŠŸ àŠ àŠªàŠšàŠ¿ àŠšàŠ¿àŠ¶à§àŠàŠ¿àŠ€ àŠšàŠš, àŠ€àŠ¬à§ àŠžàŠà§àŠž àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠàŠŸàŠ¡àŠŒàŠŸ àŠàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§ àŠžàŠàŠ¯à§àŠà§àŠ° àŠà§àŠ·à§àŠàŠŸ àŠàŠ°à§àŠšà¥€ <p><h5>àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿ # 2: àŠàŠŸàŠ°à§àŠ¡ àŠ°àŠ¿àŠ²à§ àŠªà§àŠàŠàŠ€à§ àŠªàŠŸàŠ°à§ àŠšàŠŸ</h5><p class=\"mb-3\"><pre><code> 11/1/2011 21:11:43 PM .500 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] 127.0.0.1:9150 àŠàŠ° àŠàŠªàŠ° àŠžàŠà§àŠž àŠ²àŠ¿àŠžà§àŠšàŠŸàŠ° àŠàŠ°àŠ®à§àŠ àŠàŠ°à§àŠš\n11/1/2017 21:11:44 PM.300 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 80%: àŠàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠ¹àŠà§àŠà§ 11/1/2011 21:11: 44 PM.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠàŠ®àŠŸàŠŠà§àŠ° àŠªàŠ¥à§àŠ° àŠ¹àŠª 0 àŠàŠ° àŠàŠšà§àŠ¯ àŠšà§àŠ¡ àŠà§àŠàŠà§ àŠªàŠŸàŠàŠ¯àŠŒàŠŸ àŠ¬à§àŠ¯àŠ°à§àŠ¥ àŠ¹àŠ¯àŠŒà§àŠà§à¥€ àŠàŠ àŠžàŠŸàŠ°à§àŠàŠ¿àŠàŠàŠ¿ àŠàŠŸàŠ°àŠ¿àŠà¥€\n11/1/2017 21:11:44 PM.500 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 85%: àŠªà§àŠ°àŠ¥àŠ® àŠ¹àŠª àŠšàŠ¿àŠ¯àŠŒà§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠžàŠ®à§àŠªàŠšà§àŠš àŠ¹àŠ¯àŠŒà§àŠà§\n11/1/2017 21:11:45 PM300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠªàŠ¥à§àŠ° àŠ¹àŠª 0 àŠàŠ° àŠàŠšà§àŠ¯ àŠšà§àŠ¡ àŠà§àŠàŠà§ àŠªàŠŸàŠàŠ¯àŠŒàŠŸ àŠ¬à§àŠ¯àŠ°à§àŠ¥ àŠ¹àŠ¯àŠŒà§àŠà§à¥€àŠàŠ àŠžàŠŸàŠ°à§àŠàŠ¿àŠàŠàŠ¿ àŠàŠŸàŠ°àŠ¿àŠà¥€</code></pre></p><p class=\"mb-3\">àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° ââàŠ²àŠà§ àŠàŠ°àŠàŠ® àŠ²àŠŸàŠàŠš àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠš àŠ€àŠ¬à§ àŠàŠàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° àŠžàŠŸàŠ°à§àŠàŠ¿àŠà§àŠ° àŠªà§àŠ°àŠ¥àŠ® àŠšà§àŠ¡à§àŠ° àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ°à§àŠ¥à¥€ àŠàŠ° àŠ®àŠŸàŠšà§ àŠ¹àŠ² àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠžà§àŠšà§àŠžàŠ° àŠàŠ°àŠŸ àŠàŠàŠàŠ¿ àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§àŠ° àŠàŠªàŠ° àŠàŠà§àŠšà¥€ àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠžà§àŠ€à§àŠà§àŠ²àŠ¿àŠ° àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠ àŠžà§àŠ¥àŠŸàŠªàŠš àŠàŠ°àŠŸàŠ° àŠà§àŠ·à§àŠàŠŸ àŠàŠ°à§àŠš , àŠàŠ¬àŠ àŠàŠàŠ¿ àŠžàŠ®àŠžà§àŠ¯àŠŸàŠ° àŠžàŠ®àŠŸàŠ§àŠŸàŠš àŠàŠ°àŠŸ àŠàŠàŠ¿àŠ€à¥€</p><h5> àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿ # 3: TLS àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠžàŠ®à§àŠªà§àŠ°à§àŠ£ àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ°à§àŠ¥</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 10%: àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠžàŠŸàŠ¥à§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠžàŠ®àŠŸàŠªà§àŠ€ à¥€(àŠžàŠ®à§àŠªàŠšà§àŠš àŠ¹àŠ¯àŠŒà§ àŠà§àŠà§; àŠžàŠ®à§àŠªàŠšà§àŠš àŠ¹àŠ¯àŠŒà§ àŠà§àŠà§ ; àŠàŠ£àŠšàŠŸ 10; àŠžà§àŠªàŠŸàŠ°àŠ¿àŠ¶ àŠžàŠ€àŠ°à§àŠàŠ€àŠŸ; àŠ¹à§àŠžà§àŠ [àŠ¹à§àŠžà§àŠ] xxx.xxx.xxx.xx: xxx-àŠ)\n13-11 -17 19: 53: 49.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠžàŠ®àŠžà§àŠ¯àŠŸ àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠªàŠ¿àŠà¥€ 10% àŠ àŠàŠàŠà§ àŠàŠà§: àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠžàŠŸàŠ¥à§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠ¶à§àŠ· àŠ¹àŠà§àŠà§à¥€\n13-11-17 19: 53: 49.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] 10 àŠžàŠàŠ¯à§àŠ àŠ¬à§àŠ¯àŠ°à§àŠ¥ àŠ¹àŠ¯àŠŒà§àŠà§: 13-11- 17 19: 53: 49.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] 9 àŠàŠ¿ àŠžàŠàŠ¯à§àŠà§àŠ° àŠ®à§àŠ€à§àŠ¯à§ àŠàŠà§ àŠžà§àŠà§àŠ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠžà§àŠàŠ¿àŠ-àŠ (TLS) àŠàŠžàŠàŠžàŠàŠ² àŠžà§àŠà§àŠ SSLv2 / v3 àŠ¹à§àŠ¯àŠŸàŠ²à§ A àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠªàŠ¡àŠŒà§àŠš \n13-11-17 19: 53: 49.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠžà§àŠà§àŠ àŠžàŠàŠ¯à§àŠà§ 1 àŠàŠ¿ àŠžàŠàŠ¯à§àŠà§àŠ° àŠ®à§àŠ€à§àŠ¯à§ () àŠàŠžàŠàŠžàŠàŠ² àŠžà§àŠà§àŠ (àŠà§àŠš SSL àŠàŠ¬àŠà§àŠà§àŠ àŠšà§) </code></pre></p><p class=\"mb-3\">\nàŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° àŠ²àŠà§ àŠàŠ°àŠàŠ® àŠ²àŠŸàŠàŠš àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠš, àŠ€àŠŸàŠ° àŠ®àŠŸàŠšà§ àŠàŠ° àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°à§ àŠàŠ°à§àŠ€à§àŠªàŠà§àŠ·à§àŠ° àŠžàŠà§àŠà§ TLS àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠžàŠ®à§àŠªàŠšà§àŠš àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ°à§àŠ¥ à¥€ àŠ¬à§àŠ°àŠ¿àŠàŠà§ àŠ²àŠ¿ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°à§ àŠžàŠ®à§àŠàŠ¬àŠ€ àŠàŠàŠ¿ àŠ àŠ¿àŠ àŠ¹àŠ¬à§à¥€ </p><h5>àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿ # 4 : àŠà§àŠ²àŠ àŠžà§àŠà§</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] 127.0.0.1:9150 àŠàŠ° àŠàŠªàŠ° àŠžàŠà§àŠž àŠ²àŠ¿àŠžà§àŠšàŠŸàŠ° àŠàŠ°àŠ®à§àŠ àŠàŠ°à§àŠš\n19.11.2017 00:04:48.000 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 5%: àŠ¡àŠŸàŠàŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠ¹àŠà§àŠà§\n19.11.2017 00:04:48.200 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 10%: àŠ¡àŠŸàŠàŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠžàŠŸàŠ¥à§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠ¶à§àŠ· àŠ¹àŠà§àŠà§\n19.11.2017 00:04:48.800 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠžà§àŠàŠ¿àŠàŠ¡ àŠžàŠ®àŠ¯àŠŒà§àŠ° àŠžàŠŸàŠ¥à§ àŠà§àŠ¹à§àŠ€ NETINFO àŠžà§àŠ² (OR: xxx.xx.x.xx.xxxx: àŠ¹àŠŸàŠ€à§àŠ°):\nàŠ®àŠšà§ àŠ¹àŠà§àŠà§ àŠàŠ®àŠŸàŠŠà§àŠ° àŠàŠ¡àŠŒàŠ¿àŠàŠŸ 1 àŠŠàŠ¿àŠš, 0 àŠàŠšà§àŠàŠŸ, 1 àŠ®àŠ¿àŠšàŠ¿àŠ àŠ¬àŠŸ àŠªàŠ¿àŠàŠšà§àŠ° àŠŠàŠ¿àŠà§ àŠàŠ²à§ àŠà§àŠà§ àŠ¬àŠŸ àŠ€àŠŸàŠŠà§àŠ°àŠàŠ¿ àŠàŠàŠ¿àŠ¯àŠŒà§ àŠàŠà§à¥€\nàŠàŠ° àŠàŠŸàŠ àŠàŠ°àŠŸàŠ° àŠàŠšà§àŠ¯ àŠàŠàŠàŠ¿ àŠžàŠ àŠ¿àŠ àŠàŠ¡àŠŒàŠ¿ àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš: àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠàŠªàŠšàŠŸàŠ° àŠžàŠ®àŠ¯àŠŒ, àŠžàŠ®àŠ¯àŠŒàŠà§àŠš àŠàŠ¬àŠ àŠ€àŠŸàŠ°àŠ¿àŠ àŠžà§àŠàŠ¿àŠàŠž àŠà§àŠ àŠàŠ°à§àŠšà¥€ </code></pre></p><p class=\"mb-3\">àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° ââàŠ²àŠà§ àŠàŠ°àŠàŠ® àŠ²àŠŸàŠàŠš àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠš àŠ€àŠ¬à§ àŠàŠªàŠšàŠŸàŠ° àŠžàŠ¿àŠžà§àŠà§àŠ® àŠàŠ¡àŠŒàŠ¿àŠàŠ¿ àŠà§àŠ²à¥€ àŠàŠšà§àŠà§àŠ°àŠ¹ àŠàŠ°à§ àŠšàŠ¿àŠ¶à§àŠàŠ¿àŠ€ àŠàŠ°à§àŠš àŠ¯à§ àŠàŠªàŠšàŠŸàŠ° àŠàŠ¡àŠŒàŠ¿àŠ° àŠžàŠ àŠ¿àŠ àŠžàŠ®àŠ¯àŠŒ àŠšàŠ¿àŠ°à§àŠ§àŠŸàŠ°àŠ£ àŠàŠ°àŠŸ àŠ¹àŠ¯àŠŒà§àŠà§, àŠžàŠ àŠ¿àŠ àŠàŠŸàŠàŠ®àŠà§àŠš àŠžàŠ¹à¥€ àŠ€àŠŸàŠ°àŠªàŠ° àŠàŠ°à§àŠ àŠªà§àŠšàŠ°àŠŸàŠ¯àŠŒ àŠàŠ°àŠ®à§àŠ àŠàŠ°à§àŠšà¥€</p>" + }, + "censorship-6": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª -6", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª -6", + "title": "àŠàŠ®àŠ¿ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ°à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°àŠàŠ¿ àŠšàŠŸ, àŠàŠ®àŠŸàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠ àŠžà§àŠšà§àŠžàŠ° àŠàŠ°àŠŸ àŠ¹àŠ¯àŠŒà§àŠà§?", + "description": "<p class=\"mb-3\">àŠàŠªàŠšàŠ¿ àŠàŠàŠàŠ¿ àŠžà§àŠšà§àŠžàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§ àŠ¹àŠ€à§ àŠªàŠŸàŠ°à§àŠš, àŠàŠ¬àŠ àŠ€àŠŸàŠ àŠàŠªàŠšàŠŸàŠ° àŠžà§àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°à§ àŠà§àŠ·à§àŠàŠŸ àŠàŠ°àŠŸ àŠàŠàŠ¿àŠ€à¥€ àŠàŠ¿àŠà§ àŠ¬à§àŠ°àŠ¿àŠ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠ° àŠ®àŠ§à§àŠ¯à§ àŠšàŠ¿àŠ°à§àŠ®àŠ¿àŠ€ àŠ¹àŠ¯àŠŒ, àŠàŠ¬àŠ àŠàŠªàŠšàŠ¿ àŠàŠ° àŠ²àŠà§àŠàŠŸàŠ° àŠàŠàŠšà§àŠ¡à§àŠ€à§ \"àŠàŠšàŠ«àŠ¿àŠàŠŸàŠ°\" (àŠ€àŠŸàŠ°àŠªàŠ° àŠªà§àŠ°àŠ®à§àŠªàŠ àŠàŠšà§àŠžàŠ°àŠ£) àŠšàŠ¿àŠ°à§àŠ¬àŠŸàŠàŠš àŠàŠ°à§ àŠžà§àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§àŠš àŠ¯àŠŸ àŠàŠªàŠšàŠ¿ àŠ¯àŠàŠš àŠªà§àŠ°àŠ¥àŠ®àŠ¬àŠŸàŠ°à§àŠ° àŠàŠšà§àŠ¯ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠà§àŠ²à§àŠš àŠ€àŠàŠš àŠªàŠª-àŠàŠª àŠ¹àŠ¿àŠžà§àŠ¬à§ àŠàŠžà§à¥€ àŠàŠªàŠšàŠŸàŠ° àŠ¯àŠŠàŠ¿ àŠàŠšà§àŠ¯àŠŸàŠšà§àŠ¯ àŠžà§àŠ€à§àŠ° àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš àŠ¹àŠ¯àŠŒ, àŠ€àŠŸàŠ¹àŠ²à§ àŠàŠªàŠšàŠ¿ àŠàŠ®àŠŸàŠŠà§àŠ° <mark><a href=\"https://br idges.torproject.org/\">àŠ¬à§àŠ°àŠ¿àŠà§àŠž àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠà§ </a></mark>àŠ€àŠŸàŠŠà§àŠ° àŠªà§àŠ€à§ àŠªàŠŸàŠ°à§àŠšà¥€ àŠžà§àŠ€à§ àŠžàŠ®à§àŠªàŠ°à§àŠà§ àŠàŠ°àŠ àŠ€àŠ¥à§àŠ¯à§àŠ° àŠàŠšà§àŠ¯, <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ² àŠŠà§àŠà§àŠš</a></mark>à¥€Â </p>" + } + + +} diff --git a/de.json b/de.json new file mode 100644 index 000000000..a188d9d51 --- /dev/null +++ b/de.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Unsere Website wird blockiert. Kann Tor Browser den Benutzern helfen, die Website trotzdem zu erreichen?", + "description": "<p class=\"mb-3\">Tor Browser kann dabei helfen Menschen Zugang zu deiner Webseite an Orten zu verschaffen, wo diese blockiert wird. In den meisten FÃ€llen genÃŒgt es <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> herunterzuladen und mit ihm zur blockierten Seite zu navigieren um Zugang zu erhalten. FÃŒr Orte mit aufwÃ€ndigen ZensurmaÃnahmen verfÃŒgen wir ÃŒber einen Satz an Zensurumgehungsoptionen, einschlieÃlich <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">austauschbarer Ãbertragungsarten</a></mark>. FÃŒr weitere Informationen dazu Ã¶ffne die <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser-Benutzeranleitung</a></mark> im Abschnitt <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">Zensur</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Meine Lieblingswebsite blockiert die Verbindung ÃŒber Tor.", + "description": "<p class=\"mb-3\">Schade, dass Sie die gewÃŒnschte Internetseite nicht besuchen kÃ¶nnen! Manchmal blockieren Webseiten Tor-Nutzer weil sie den Unterschied zwischen regulÃ€ren Tor-Nutzern und automatisierten Besuchern nicht erkennen kÃ¶nnen. Den meisten Erfolg hatten wir indem wir die Webseitenbetreiber direkt kontaktieren um die Blockade aufzuheben. Manchmal hilft dies:<br />\"Hallo! Ich habe versucht Ihre Webseite xyz.com mit dem Tor Browser zu besuchen und habe festgestellt, dass Sie Tor-Nutzern nicht erlauben Ihre Webseite zu besuchen. I bitte Sie diese Entscheidung zu ÃŒberdenken; Tor wird von Menschen auf der ganzen Welt genutzt um deren PrivatsphÃ€re zu beschÃŒtzen und Zensur zu bekÃ€mpfen. Indem Sie Tor-Nutzer blockieren, blockieren Sie auch Nutzer in repressiven Staaten, die ein freies Internet nutzen wollen, Journalisten und Wissenschaftler die sich vor einer Erkennung schÃŒtzen wollen, Whistleblowers, Aktivisten, und gewÃ¶hnliche Menschen die invasives Tra cking durch Dritte nicht akzeptieren. Bitte beziehen Sie Stellung fÃŒr digitale BÃŒrgerrechte und Internetfreiheit, und erlauben Sie Tor-Nutzern den Zugriff auf xyz.com. Vielen Dank\"<br />Im Falle von Banken und anderen sensitiven Webseiten sind auch ortsbasierte Blockaden ÃŒblich (wenn eine Bank weiÃ, dass Sie ÃŒblicherweise von einem bestimmen Land aus zugreifen, und plÃ¶tzlich von einem Exit-Server auf der anderen Seite der Welt zugreifen, kÃ¶nnte Ihre Konto (zeitweilig) gesperrt werden). Wenn Sie einen Onion-Dienst nicht erreichen kÃ¶nnen, sehen Sie hier nach: <a href=\"http://127.0.0.1:5000/#onionservices-3\">Ich kann X.onion nicht erreichen!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Wie kann ich Tor herunterladen, wenn torproject.org blockiert ist?", + "description": "<p class=\"mb-3\">Wenn du Tor ÃŒber unsere <mark><a href=\"https://www.torproject.org\">Website</a></mark> nicht herunterladen kannst, ist es mÃ¶glich sich einen alternativen Download-Link von Tor ÃŒber GetTor zusenden zu lassen. GetTor ist ein Dienst der automatisch auf Nachrichten mit Links zur aktuellsten Version des Tor Browsers antwortet, die an verschiedenen Orten wie Dropbox, Google Drive und GitHub gehostet werden.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "Ich kann mich nicht mit Tor Browser verbinden, ist mein Netzwerk zensiert?", + "description": "<p class=\"mb-3\">Du befindest dich mÃ¶glicherweise in einem zensierten Netzwerk und solltes daher versuchen BrÃŒcken zu verwenden. Einige BrÃŒcken sind in Tor Browser eingebaut und du kannst sie im Tor Browser-Startfenster, das erscheint, wenn du Tor Browser das erste Mal startest, ÃŒber \"Konfigurieren\" (und die folgende Dialoge) auswÃ€hlen. Wenn du andere BrÃŒcken benÃ¶tigst, kannst du diese auf unserer <mark><a href=\"https://bridges.torproject.org/\">BrÃŒcken-Website</a></mark> erhalten. FÃŒr weitere Informationen ÃŒber BrÃŒcken, lies den Abschnitt in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser-Anleitung</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Ich habe Probleme mich mit Tor zu verbinden und kann die Ursache nicht finden.", + "description": "<p class=\"mb-3\">Wenn du Verbindungsprobleme hast, wÃ€hle bitte die Option \"Tor-Protokoll in die Zwischenablage kopieren\" aus. FÃŒge dann das Tor-Protokoll in eine Textdatei oder ein anderes Dokument ein. Du solltest nun einen der folgenden verbreiteten FehlereintrÃ€ge sehen (suche nach foldenden Zeilen in deinem Tor-Protokoll):</p><h5>Ãblicher Fehlereintrag #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "Ich kann mich nicht mit Tor Browser verbinden, ist mein Netzwerk zensiert?", + "description": "<p class=\"mb-3\">Du befindest dich mÃ¶glicherweise in einem zensierten Netzwerk und solltes daher versuchen BrÃŒcken zu verwenden. Einige BrÃŒcken sind in Tor Browser eingebaut und du kannst sie im Tor Browser-Startfenster, das erscheint, wenn du Tor Browser das erste Mal startest, ÃŒber \"Konfigurieren\" (und die folgende Dialoge) auswÃ€hlen. Wenn du andere BrÃŒcken benÃ¶tigst, kannst du diese auf unserer <mark><a href=\"https://bridges.torproject.org/\">BrÃŒcken-Website</a></mark> erhalten. FÃŒr weitere Informationen ÃŒber BrÃŒcken, lies den Abschnitt in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser-Anleitung</a></mark>.</p>" + } + + +} diff --git a/es.json b/es.json new file mode 100644 index 000000000..dc9ef431e --- /dev/null +++ b/es.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Nuestro sitio web estÃ¡ bloqueado por un censor. Â¿El Navegador Tor puede ayudar a los usuarios a acceder a nuestro sitio web?", + "description": "<p class=\\\"mb-3\\\">El Navegador Tor ciertamente puede ayudar a que la gente acceda a tu sitio web desde lugares donde estÃ¡ bloqueado. La mayorÃa de las veces se lograrÃ¡ el acceso simplemente descargando el Navegador Tor y luego usÃ¡ndolo para navegar hacia el sitio bloqueado. En lugares donde hay una fuerte censura, tenemos distintas opciones de elusiÃ³n disponibles, incluyendo transportes intercambiables. Para mÃ¡s informaciÃ³n, por favor lee la secciÃ³n sobre elusiÃ³n de la censura del Manual de Usuario del Navegador Tor.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Mi sitio web favorito estÃ¡ bloqueando el acceso a travÃ©s de Tor.", + "description": "<p class=\"mb-3\">Â¡Sentimos oÃr que no puede visitar el sitio web que querÃa! A veces los sitios web bloquearÃ¡n a los usuarios de Tor porque no puede diferenciar entre el usuario corriente de Tor y el trÃ¡fico automatizado. El mayor Ã©xito que hemos tenido en lograr que los sitios desbloqueen a los usuarios de Tor es hacer que los usuarios contacten con los administradores del sitio directamente. Algo como esto podrÃa funcionar:<br />\"Â¡Hola! TratÃ© de acceder a su sitio xyz.com mientras usaba el Navegador Tor, y descubrÃ que no permite que los usarios de Tor accedan a su sitio. Le insto a reconsiderar esta decisiÃ³n; Tor es usado por personas por todo el mundo para proteger su privacidad y luchar contra la censura. Al bloquear a los usuarios de Tor, probablemente estÃ¡ bloqueando a personas en paÃses represivos que quieren usar una Internet libre, periodistas e investigadores que quieren protegerse a si mismos de ser identificados, informantes, activistas, y gente ordinaria que quiere optar por evitar el rastreo invasivo de terceros. Por favor, adopte una postura fuerte en favor de la privacidad digital y la libertad en Internet, y permita a los usuarios de Tor acceder a xyz.com. Gracias.\"<br />Probablemente pueda evitar barreras idiomÃ¡ticas si lo hace en inglÃ©s:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital privacy and internet freedom, and allow Tor users access to xyz.com. Thank you.\ "<br />En el caso de bancos, y otros sitios web sensibles, tambiÃ©n es comÃºn ver bloqueos en base a la ubicaciÃ³n geogrÃ¡fica (si un banco sabe que generalmente accede a sus servicios desde un paÃs, y de repente estÃ¡ conectando desde un repetidor de salida de Tor en la otra parte del mundo, su cuenta puede ser bloqueada o suspendida). Si no puede conectar a un servicio onion, por favor, vea <a href=\"http://127.0.0.1:5000/#onionservices-3\">Â¡No puedo alcanzar X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Â¿CÃ³mo descargo Tor si torproject.org estÃ¡ bloqueada?", + "description": "<p class=\"mb-3\">Si no puedes descargar Tor a travÃ©s de nuestro â<mark><a href=\"https://www.torproject.org\">sitio web</a></mark>, puedes obtener una copia de Tor que se te entregarÃ¡ vÃa GetTor. GetTor es un servicio que responde automÃ¡ticamente a los mensajes con enlaces a la versiÃ³n mÃ¡s reciente del Navegador Tor, alojada en distintas ubicaciones, que es menos probable que estÃ©n censuradas, como Dropbox, Google Drive, y GitHub.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "No puedo conectar al Navegador Tor, Â¿estÃ¡ censurada mi red?", + "description": "<p class=\"mb-3\">PodrÃas estar en una red censurada, asÃ que deberÃas intentar usar puentes. Algunos puentes van incorporados al Navegador Tor, y puedes usar esos puentes seleccionando \"configurar\" (y luego siguiendo las instrucciones) en la ventana del Arranque de Tor que aparece cuando abres el Navegador Tor por primera vez. Si necesitas otros puentes, puedes obtenerlos en nuestro â<mark><a href=\"https://bridges.torproject.org/\">sitio web de puentes</a></mark>. Para mÃ¡s informaciÃ³n acerca de los puentes, lee el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">âmanual del Navegador Tor</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Estoy teniendo problemas conectando a Tor, y no logro averiguar quÃ© es lo que estÃ¡ mal.", + "description": "<p class=\"mb-3\"><p class=\"mb-3\">Si estÃ¡ teniendo problemas para conectar, por favor seleccione la opciÃ³n para \âcopiar registro de Tor al portapapeles\â. Luego pegue el registro de Tor en un fichero de texto u otro documento. DeberÃa ver uno de estos errores comunes de registro (busque las siguientes lÃneas en su registro de Tor):</p><h5>Error comÃºn de registro nÂº 1: Fallo de conexiÃ³n proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WA RN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si ve lÃneas como estas en su registro de Tor, significa que no estÃ¡ pudiendo conectar a un proxy SOCKS. Si se requiere un proxy SOCKS para la configuraciÃ³n de su red, entonces, por favor, asegÃºrese de que ha introducido los detalles de su proxy correctamente. Si no se requiere un proxy SOCKS o no estÃ¡ seguro, por favor, trate de conectar a la red Tor sin un proxy SOCKS.<p><h5>Error comÃºn de registro nÂº 2: No se puede conectar a los repetidores guardiÃ¡n</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/20 17 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si ve lÃneas como estas en su registro de Tor, significa que su Tor no pudo conectar al primer nodo en el circuito Tor. Esto podrÃa significar que se encuentra en una red que estÃ¡ censurada. Por favor, trate de conectar con puentes, y eso deberÃa corregir el problema.</p><h5>Error comÃºn de registro nÂº 3: No se pudo completar la negociaciÃ³n TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 1 3-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Si vÃ© lÃneas como estas en su registro de Tor, significa que Tor no pudo completar una negociaciÃ³n TLS con las autoridades de directorio. Usar puentes probablemente corregirÃ¡ esto.</p><h5>Error comÃºn de registro nÂº 4: Desfase de reloj</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Si ve lÃneas com o esta en su registro de Tor, significa que su reloj de sistema no estÃ¡ ajustado correctamente. Por favor, asegÃºrese de que su reloj estÃ¡ ajustado de forma precisa, incluyendo la zona horaria correcta. Luego reinicie Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "No puedo conectar al Navegador Tor, Â¿estÃ¡ censurada mi red?", + "description": "<p class=\"mb-3\">PodrÃa estar en una red censurada, y por tanto deberÃa intentar usar puentes. Algunos puentes estÃ¡n integrados en el Navegador Tor, y puede usarlos seleccionando \"configurar"\ (y siguiendo las instrucciones) en la ventana del Arranque de Tor que aparece cuando abre el Navegador Tor por primera vez. Si necesita otros puentes, puede obtenerlos en nuestro â<mark><a href=\"https://bridges.torproject.org/\">sitio web de puentes</a></mark>. Para mÃ¡s informaciÃ³n sobre los puentes, vea el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">Manual del Navegador âTor</a></mark>.</p>" + } + + +} diff --git a/fr.json b/fr.json new file mode 100644 index 000000000..8114facd9 --- /dev/null +++ b/fr.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censure-1", + "control": "censure-1", + "title": "Notre site Web est bloquÃ© par un censeur. Le navigateur Tor peut-il aider les utilisateurs Ã accÃ©der Ã notre site Webâ?", + "description": "<p class=\"mb-3\">Le navigateur Tor peut certainement aider les utilisateurs Ã accÃ©der Ã votre site Web oÃ¹ il est bloquÃ©. La plupart du temps, il suffira de tÃ©lÃ©charger le <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">navigateur Tor</a></mark>et de lâutiliser pour naviguer vers le site bloquÃ© pour y accÃ©der. Pour les endroits soumis Ã une censure forte, de nombreuses options de contournement sont offertes, dont les â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">transports enfichables</a></mark>. Pour de plus amples renseignements, veuillez consulter la rubrique sur la <mark><a href=\"https://tb-manual.torproject.org/fr/circumvention.html\">censure</a></mark> du <mark><a href=\"https://tb-manual.torproject.org/fr/\">âguide dâutilisation du navigateur Tor</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censure-2", + "control": "censure-2", + "title": "Mon site Web prÃ©fÃ©rÃ© bloque lâaccÃšs Ã partir de Tor.", + "description": "<p class=\"mb-3\">Nous sommes dÃ©solÃ©s dâapprendre que vous ne pouvez pas visiter le site Web que vous souhaitezâ! Un site Web bloquera parfois les utilisateurs de Tor parce quâils ne peuvent pas faire la diffÃ©rence entre lâutilisateur de Tor moyen et le trafic automatisÃ©. Les meilleurs rÃ©sultats pour dÃ©bloquer lâaccÃšs des utilisateurs de Tor Ã un site donnÃ© ont Ã©tÃ© obtenus en demandant aux utilisateurs de contacter directement les administrateurs dudit site. Ce qui suit pourrait suffireÂ :<br />Â«Â Bonjourâ! Jâai essayÃ© dâaccÃ©der Ã votre site xyz.com tout en utilisant le navigateur Tor et jâai dÃ©couvert que vous ne permettez pas aux utilisateurs de Tor dây accÃ©der. Je vous demande instamment de reconsidÃ©rer votre dÃ©cisionâ; Tor est utilisÃ© partout dans le monde par des personnes souhaitant protÃ©ger leurs renseignements personnels tout en combattant la censure. En bloquant les utilisateurs de Tor, vous bloquez vraisemblableme nt des personnes se trouvant dans des pays oÃ¹ rÃšgne la rÃ©pression et qui souhaitent utiliser un Internet libre, des journalistes et des chercheurs qui ne veulent pas Ãªtre dÃ©couverts, des lanceurs dâalerte, des activistes et des personnes ordinaires qui ne veulent pas Ãªtre suivies Ã la trace par des tiers invasifs. Veuillez adopter une position ferme privilÃ©giant la confidentialitÃ© numÃ©rique et la libertÃ© sur Internet, et permettre aussi aux utilisateurs de Tor dâaccÃ©der Ã xyz.com. Merci.<br />Voici le mÃªme message en anglaisÂ : <br />âHi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from di scovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital privacy and internet freedom, and allow Tor users access to xyz.com. Thank you.â<br />Dans le cas de banques ou autres sites Web dÃ©licats, il est aussi habituel de constater un blocage dâaprÃšs la position gÃ©ographique (si une banque sait que vous accÃ©dez habituellement Ã ses services Ã partir dâun pays et que vous vous connectez soudainement Ã partir dâun relais de sortie situÃ© de lâautre cÃŽtÃ© de la planÃšte, votre compte pourrait Ãªtre verrouillÃ© ou suspendu). Si vous ne pouvez pas vous connecter Ã un service oignon, veuillez consulter <a href=âhttp://127.0.0.1:5000/#onionservices-3â>Je ne peux pas accÃ©der Ã X.onionâ!</a></p>" + }, + "censorship-3": { + "id": "#censure-3", + "control": "censure-3", + "title": "Comment puis-je tÃ©lÃ©charger Tor si torproject.org est bloquÃ©â?", + "description": "<p class=\"mb-3\">Si vous ne pouvez pas tÃ©lÃ©charger Tor Ã partir de notre <mark><a href=\"https://www.torproject.org\">site Web</a></mark>, une exemplaire de Tor peut vous Ãªtre livrÃ© par GetTor. GetTor est un service qui rÃ©pond automatiquement aux messages en incluant des liens vers la derniÃšre version du navigateur Tor, hÃ©bergÃ©e en divers endroits tels que Dropbox, Google Disque et GitHub.</p>" + }, + "censorship-4": { + "id": "#censure-4", + "control": "censure-4", + "title": "Je n'arrive pas Ã me connecter au navigateur Tor, mon rÃ©seau est-il censurÃ© ?", + "description": "<p class=\"mb-3\">Il se peut que vous soyez sur un rÃ©seau censurÃ© et que vous deviez tenter dâutiliser des ponts. Des ponts sont intÃ©grÃ©s au navigateur Tor et vous pouvez utiliser ces ponts en choisissant Â«Â ConfigurerÂ Â» (puis en suivant les indications) dans la fenÃªtre du lanceur Tor qui surgit quand vous ouvrez le navigateur Tor pour la premiÃšre fois. Sâil vous faut dâautres ponts, vous pouvez en obtenir sur notre â<mark><a href=\"https://bridges.torproject.org/\">site Web BridgeDB</a></mark>. Pour de plus amples renseignements concernant les ponts, consulter le <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">âguide dâutilisation du navigateur Tor</a></mark>.</p>\n" + }, + "censorship-5": { + "id": "#censure-5", + "control": "censure-5", + "title": "JâÃ©prouve des difficultÃ©s Ã me connecter Ã Tor et je nâarrive pas Ã comprendre ce qui ne va pas.", + "description": "<p class=\"mb-3\">Si vous Ã©prouvez des difficultÃ©s Ã vous connecter, veuillez sÃ©lectionner lâoption Â«Â Copier le journal de Tor dans le presse-papiersÂ Â». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver lâune de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor)Â : </p><h5>Erreur habituelle de journal noÂ 1 : Ã©chec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter Ã un mandataire SOCKS. Si un mandataire SOCKS est nÃ©cessaire Ã la configuration de rÃ©seau, veuillez alors vous assurer dâavoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS nâest pas nÃ©cessaire ou si vous ne savez pas, veuillez tenter de vous connecter au rÃ©seau Tor sans mandataire SOCKS.<p><h5>Erreur habituelle de journal noÂ 2 : impossible dâatteindre les relais gardes</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/ 2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter au premier nÅud du circuit Tor. Cela pourrait signifier que vous Ãªtes sur un rÃ©seau qui est censurÃ©. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5>Erreur habituelle de journal noÂ 3 : Ã©chec dâÃ©tablissement dâune liaison TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19 :53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas rÃ©ussi Ã Ã©tablir une liaison TLS avec les autoritÃ©s d'annuaire. Lâutilisation de ponts corrigera certainement cette situation.</p><h5>Erreur habituelle de journal noÂ 4 : dÃ©calage dâhorloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or t hat theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">\nSi vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge systÃšme nâest pas juste. Veuillez vous assurer que votre horloge est rÃ©glÃ©e avec prÃ©cision, fuseau horaire inclus, puis redÃ©marrez Tor. </p>" + }, + "censorship-6": { + "id": "#censure-6", + "control": "censure-6", + "title": "Je n'arrive pas Ã me connecter au navigateur Tor, mon rÃ©seau est-il censurÃ© ?", + "description": "<p class=\"mb-3\">Il se peut que vous soyez sur un rÃ©seau censurÃ© et que vous deviez tenter dâutiliser des ponts. Des ponts sont intÃ©grÃ©s au navigateur Tor et vous pouvez utiliser ces ponts en choisissant Â«Â ConfigurerÂ Â» (puis en suivant les indications) dans la fenÃªtre du lanceur Tor qui surgit quand vous ouvrez le navigateur Tor pour la premiÃšre fois. Sâil vous faut dâautres ponts, vous pouvez en obtenir sur notre â<mark><a href=\"https://bridges.torproject.org/\">site Web BridgeDB</a></mark>. Pour de plus amples renseignements concernant les ponts, consulter le <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">âguide dâutilisation du navigateur Tor</a></mark>.</p>" + } + + +} diff --git a/id.json b/id.json new file mode 100644 index 000000000..55c318a59 --- /dev/null +++ b/id.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Situs kami diblokir sensor. Apakah Tor Browser dapat membantu pengguna kami dalam mengakses situs kami?", + "description": "<p class=\"mb-3\">Tor Browser dapat membantu dalam akses situs web Anda dari tempat yang terblokir. Umumnya hanya unduh <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser </a></mark>dan gunakannya untuk membuka akses situs yang terblokir. Di tempat-tempat yang mengalami sensor berat, tersedia beberapa pilihan yang mengatasinya, termasuk <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transport </a></mark>. Untuk info lebih lanjut, silakan baca bagian <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser Manual </a></mark>di bagian <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Situs web favorit saya memblokir akses melalui Tor.", + "description": "<p class=\"mb-3\">Kami turut prihatin atas Anda tidak dapat melakukan akses ke situs web yang Anda inginkan! Kadang beberapa situs web memblokir pengguna Tor karena tidak dapat membedakan pengguna Tor biasa dan lalu-lintas otomatos. Hal terbaik yang dapat dilakukan adalah pengguna menghubungi langsung admin situsnya. Ini mungkin dapat menjadi contoh: <br />\"Halo! Saya berusaha melakukan akses terhadap situs xyz.com Anda melalui Tor Browser dan ternyata Anda tidak mengizinkan pengguna Tor untuk melakukan akses terhadap situs Anda. Saya mohon dengan sangat untuk mempertimbangkan hal ini; Tor digunakan orang-orang di seluruh dunia untuk melindungi privasi mereka dan melawan sensor. Dengan memblokir pengguna Tor, Anda akan memblokir orang-orang di negara-negara represif yang ingin menggunakan Internet secara bebas, wartawan, dan peneliti yang ingin melindungi diri sendiri dari penemuan, termasuk whistleblower, aktivis, dan orang-orang biasa yang ingin terbebas dari pel acakan menyeluruh yang dilakukan pihak lain. Mohon dukungan penuh terhadap privasi digital dan kebebasan Internet, dan izinkan pengguna Tor untuk melakukan akses ke xyz.com. Terima kasih.\"<br />Untuk situs web perbankan dan situs web lain yang sensitif, umumnya ada pemblokiran berdasarkan wilayah geografis (jika bank Anda mengetahui Anda biasanya melakukan akses terhadap jasa mereka dari suatu negara dan jika tiba-tiba Anda membuka situs web mereka dari exit relay di negara lain, akun Anda mungkin akan dikunci atau dibekukan). Jika Anda tidak dapat terhubung ke sebuah onion service, silakan lihat <a href=\"http://127.0.0.1:5000/#onionservices-3\">Saya tidak dapat menghubungi X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Bagaimana cara mengunduh Tor jika torproject.org diblokir?", + "description": "<p class=\"mb-3\">Jika Anda tidak dapat mengunduh Tor dari <mark><a href=\"https://www.torproject.org\">situs kami</a></mark>, Tor dapat dikirim kepada Anda melalui GetTor. GetTor adalah service yang yang otomatis merespon pesan berisi tautan ke versi terakhir Tor Browser, yang dihosting di lokasi beragam sehingga kemungkinan kecil disensor, seperti Dropbox, Google Drive, dan Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "Saya tidak bisa terhubung ke Tor Browser, apakah jaringan saya terkena sensor?", + "description": "<p class=\"mb-3\">Anda mungkin berada di jaringan yang terdampak sensor, sehingga Anda seharusnya menggunakan bridge yang terintegrasi di Tor Browser. Anda dapat menggunakannya dengan memilih \"configure\" (lalu setelah beberapa pemberitahuan) di jendela launcher Tor yang muncul setelah Anda menjalankan Tor Browser. Jika Anda memerlukan bridge lain, Anda dapat memperolehnya di <mark><a href=\"https://bridges.torproject.org/\">situs web bridge kami </a></mark>. Untuk info lebih lanjut tentang bridge, silakan baca <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser </a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", + "description": "<p class=\"mb-3\">Jika Anda mendapat masalah dalam terhubung ke Jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Jaringan Tor \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Tor gagal ter sambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.< /p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "Saya tidak bisa terhubung ke Tor Browser, apakah jaringan saya terkena sensor?", + "description": "<p class=\"mb-3\">Anda mungkin berada di jaringan yang terdampak sensor, sehingga Anda seharusnya menggunakan bridge yang terintegrasi di Tor Browser. Anda dapat menggunakannya dengan memilih \"configure\" (lalu setelah beberapa pemberitahuan) di jendela launcher Tor yang muncul setelah Anda buka Tor Browser. Jika Anda memerlukan bridge lain, Anda dapat memperolehnya di <mark><a href=\"https://bridges.torproject.org/\">situs web bridge kami </a></mark>. Untuk info lebih lanjut tentang bridge, silakan baca <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser </a></mark>.</p>" + } + + +} diff --git a/ja.json b/ja.json new file mode 100644 index 000000000..a8465c9e6 --- /dev/null +++ b/ja.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#æ€é²-1", + "control": "æ€é²-1", + "title": "ç§ãã¡ã®WEBãµã€ãã¯æ€é²ã«ãããããã¯ãããŸãããTorãã©ãŠã¶ãŒã¯ãŠãŒã¶ãŒã®WEBãµã€ããžã®ã¢ã¯ã»ã¹ãå©ããŠãããŸããïŒ", + "description": "<p class=\"mb-3\">ããªãã®ãµã€ãããããã¯ãããå ŽåãTorãã©ãŠã¶ãŒãäººã¯ç¢ºå®ã«ã¢ã¯ã»ã¹ã§ããããå©ãããå€§æµã®å Žåã<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Torãã©ãŠã¶ãŒ</a></mark>ãå©çšããŠãµã€ãã®ã¢ãã¬ã¹ã«ã¢ã¯ã»ã¹ããã ãã§ååã§ããããå³ããæ€é²ãããå Žåã<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">Pluggable Transport</a></mark>ãªã©æ§ããªè¿åæ¹æ³ããããŸããè©³çŽ°ã«ã€ããŠã¯ã<mark><a href=\"https://tb-manual.torproject.org/en-US/\">Torãã©ãŠã¶ãŒã®ãŠãŒã¶ãŒããã¥ã¢ã«</a></mark>ã«<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">æ€é²</a></mark>ã«é¢ããç« ãèª¿ã¹ãŠäžããã</p>" + }, + "censorship-2": { + "id": "#æ€é²-2", + "control": "æ€é²-2", + "title": "ãæ°ã«å¥ãã®WEBãµã€ããžã®ã¢ã¯ã»ã¹ãTorã«ãããããã¯ãããŸããã", + "description": "<p class=\"mb-3\">ããªãã®æããµã€ãã«ã¢ã¯ã»ã¹ã§ããªãããšã¯ç³ãèš³ãããŸããïŒãµã€ãã¯ãã°ãã°TorãŠãŒã¶ãŒããããã¯ããŸããåœŒãã¯éåžžã®TorãŠãŒã¶ãŒãšèªåãã©ãã£ãã¯ã®éããèŠåããããšãã§ããªãããã§ãããããã¯ãè§£é€ããµã€ããååŸããã®ã«ãã£ãšãé©ããææ®µã¯ãTOAãŠãŒã¶ãŒããµã€ãç®¡çèã«å¯ŸããŠçŽæ¥çã«ã³ã³ã¿ã¯ããåãããšã§ãããã®ãããªããªãã¯ãäœ¿ãããããããŸãã:<br />âããïŒç§ã¯ããªãã®ãµã€ãxyz.comã«Torãã©ãŠã¶ãŒã§ã¢ã¯ã»ã¹ããããšããã®ã ããã©ãããªãã®ãµã€ãã¯TorãŠãŒã¶ãŒãžã®ã¢ã¯ã»ã¹ãèš±å¯ããŠããªãã¿ãããªãã ããã®æ±ºå®ã¯åæ€èšããããšããå§ãããããTorã¯ãã©ã€ãã·ãŒä¿è·ãšæ€é²ãžã®å¯Ÿæã®çºã«äžçäžã®äººãã«ãã£ãŠäœ¿ãããŠãããã ãTorãŠãŒã¶ãŒããããã¯ãã ããšã¯ãèªç±ãªã€ã³ã¿ãŒããããæãæå§çãªåœã®äººãããé²åºããå®ãããã¹ããžã£ãŒããªã¹ããèª¿æ»å¡ãåéšåçºèãæŽ»åå®¶ãåã³äŸµç¥çãªãµãŒãããŒãã£ã®ãã©ããã³ã°ããéãããæ®éã®äººããããããã¯ããŠããŸããã ãã©ãããããžã¿ã«ãã©ã€ãã·ãŒãšã€ã³ã¿ãŒãããã®èªç±ãå°éããŠãTorãŠãŒã¶ãŒãxyz.comã«ã¢ã¯ã»ã¹ã§ããããã«ããŠã»ãããããããšããâ<br />éè¡ããã®ä»ã®å³å¯ãªWEBãµã€ãã®å Žåããã®å°åã®å°ççãªé®ææå ±ãèŠãŸãããïŒéè¡ãããªããæ®æ®µããåœããã¢ã¯ã»ã¹ããŠããããšãç¥ã£ãŠããã°ãããªãã®ã¢ã«ãŠã³ãã¯çªç¶ããã¯ããããäžæãããå¯èœæ§ããããŸãïŒãããããªãããªããªã³ãµãŒãã¹ã«æ¥ç¶ã§ããªãå Žåã¯ã<a href=\"http://127.0.0.1:5000/#onionservices-3\">X.onionã«ã¢ã¯ã»ã¹ã§ããŸãã</a>ãåç§ã ãŠãã ããã</p>" + }, + "censorship-3": { + "id": "#æ€é²-3", + "control": "æ€é²-3", + "title": "torproject.orgããããã¯ãããŠããå Žåãã©ã®ããã«TorãããŠã³ããŒãã§ããŸããïŒ", + "description": "<p class=\"mb-3\">ç§ãã¡ã®<mark><a href=\"https://www.torproject.org\">WEBãµã€ã</a></a>ããTorãããŠã³ããŒãã§ããªãå ŽåãGetTorã«ãã£ãŠTorãããŠã³ããŒãã§ããŸããGetTor ã¯ææ°ããŒãžã§ã³ã® Torãã©ãŠã¶ãŒ ãžã®ãªã³ã¯ãã¡ãã»ãŒãžã§èªåçã«è¿ä¿¡ãããµãŒãã¹ã§ãããã¡ã€ã«ã¯ DropboxïŒGoogle Drive ããã³ GitHub ãšãã£ãããŸããŸãªæ€é²ãããå¯èœæ§ãäœãå Žæã§ãã¹ããããŠããŸãã </p>" + }, + "censorship-4": { + "id": "#æ€é²-4", + "control": "æ€é²-4", + "title": "Torãã©ãŠã¶ãŒã«æ¥ç¶ã§ããŸãããç§ã®ãããã¯ãŒã¯ã¯æ€é²ãããŠããŸããïŒ", + "description": "<p class=\"mb-3\">æ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ãããã®ã§ãããªããžãäœ¿ã£ãŠè©ŠããŠã¿ãŠäžãããããããªããžã¯Torãã©ãŠã¶ãŒã«çµã¿èŸŒãŸãããããåããŠTorãã©ãŠã¶ãŒãéãæã«è¡šç€ºãããTor LauncherãŠã£ã³ããŠã«ãããèšå®ããéžæããŠäžããïŒãããŠããã³ããã«åŸã£ãŠäžããïŒãä»ã®ããªããžãå¿èŠãªããç§ãã¡ã®<mark><a href=\"https://bridges.torproject.org/\">ããªããžWEBãµã€ã</a></mark>ããæã«å¥ããããšãã§ããŸããè©³çŽ°ã«ã€ããŠã¯ã<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Torãã©ãŠã¶ãŒã®ãŠãŒã¶ãŒããã¥ã¢ã«</a></mark>ã«ããªããžã«é¢ããç« ãèª¿ã¹ãŠäžããã</p>" + }, + "censorship-5": { + "id": "#æ€é²-5", + "control": "æ€é²-5", + "title": "Torã«ã¢ã¯ã»ã¹ã§ããªãããäœãåé¡ãªã®ãåãããŸããã", + "description": "<p class=\"mb-3\">Torã«ã¢ã¯ã»ã¹ã§ããªãå ŽåããTorãã°ãã¯ãªããããŒãã«ã³ããŒãããéžæè¢ãéžãã§ããã°ãã¡ã¢åž³ãããã¯ããã¥ã¡ã³ããã¡ã€ã«ã«è²Œãä»ããŠäžãããä»¥äžã®è¯ããããšã©ãŒã¡ãã»ãŒãžãèŠã€ããã¯ãã§ãïŒ</p><h5>ãããããã°ãšã©ãŒ#1: ãããã·æ¥ç¶å€±æ</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx.. xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãSOCKSãããã·ãšç¹ãããªããšããããšã§ãããããã¯ãŒã¯ã«ã¯SOCKSãããã·ãå¿èŠãªããèšå®ãç¢ºèªããŠäžãããSOCKSãããã·ãå¿èŠã§ã¯ãªãå Žåããããã¯ããåãããªãå ŽåãSOCKSãããã·ç¡ãã§Torã«ã¢ã¯ã»ã¹ããŠã¿ãŠäžããã<p><h5>ãããããã°ãšã©ãŒ#2: ã¬ãŒããªã¬ãŒãšæ¥ç¶ã§ããªã</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discardi ng this circuit.</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorã¯circuitã®æåã®ããŒããšæ¥ç¶ã§ããªãã£ããšããããšã§ããæ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ããããŸããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããã¯ãã§ãã</p><h5>ãããããã°ãšã©ãŒ#3: TLSãã³ãã·ã§ã€ã¯ã®å€±æ</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorããã£ã¬ã¯ããªãªãŒãœãªãã£ãšTLSãã³ãã·ã§ã€ã¯ãå®äºã§ããªãã£ããšããããšã§ããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããå¯èœæ§ãããã</p><h5>ãããããã°ãšã©ãŒ#4: ã¯ããã¯ã¹ãã¥ãŒ</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p clas s=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãã·ã¹ãã ã»ã¯ããã¯ã«ã¯ééã£ãæå»ãèšå®ãããŸããã·ã¹ãã ã»ã¯ããã¯ãæ£ããæå»ãšã¿ã€ã ãŸãŒã³ã«åãããŠããTorãåèµ·åããŠäžããã </p>" + }, + "censorship-6": { + "id": "#æ€é²-6", + "control": "æ€é²-6", + "title": "Torãã©ãŠã¶ãŒã«æ¥ç¶ã§ããŸãããç§ã®ãããã¯ãŒã¯ã¯æ€é²ãããŠããŸããïŒ", + "description": "<p class=\"mb-3\">æ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ãããã®ã§ãããªããžãäœ¿ã£ãŠè©ŠããŠã¿ãŠäžãããããããªããžã¯Torãã©ãŠã¶ãŒã«çµã¿èŸŒãŸãããããåããŠTorãã©ãŠã¶ãŒãéãæã«è¡šç€ºãããTor LauncherãŠã£ã³ããŠã«ãããèšå®ããéžæããŠäžããïŒãããŠããã³ããã«åŸã£ãŠäžããïŒãä»ã®ããªããžãå¿èŠãªããç§ãã¡ã®<mark><a href=\"https://bridges.torproject.org/\">ããªããžWEBãµã€ã</a></mark>ããæã«å¥ããããšãã§ããŸããè©³çŽ°ã«ã€ããŠã¯ã<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Torãã©ãŠã¶ãŒã®ãŠãŒã¶ãŒããã¥ã¢ã«</a></mark>ã«ããªããžã«é¢ããç« ãèª¿ã¹ãŠäžããã</p>" + } + + +} diff --git a/nl.json b/nl.json new file mode 100644 index 000000000..9f96969e7 --- /dev/null +++ b/nl.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censuur-1", + "control": "censuur-1", + "title": "Onze website wordt geblokkeerd door een censor. Kan Tor Browser gebruikers helpen toegang tot onze website te krijgen?", + "description": "<p class=\"mb-3\">Tor Browser kan mensen zeker helpen toegang te krijgen tot uw website op plaatsen waar deze is geblokkeerd. Meestal gewoon downloaden van de <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> en dan gebruik het om te navigeren naar de geblokkeerde site en zal toegang toestaan. Op plaatsen waar sprake is van zware censuur hebben we een aantal opties voor censuurontwijking beschikbaar, waaronder <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">inplugbare transports</a></mark>. Voor meer informatie, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/\"> Tor Browser Gebruiker Manual</a></mark> hoofdstuk over <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censuur-2", + "control": "censuur-2", + "title": "Mijn favoriete website blokkeert de toegang via Tor.", + "description": "<p class=\"mb-3\">Sorry om te horen dat je de website die je wilde niet kunt bezoeken! Soms blokkeren websites Tor-gebruikers omdat ze niet het verschil kunnen zien tussen de gemiddelde Tor-gebruiker en automatisch verkeer. Het beste succes dat we hebben gehad bij het ontgrendelen van Tor-gebruikers, is ervoor te zorgen dat gebruikers rechtstreeks contact opnemen met de sitebeheerders. Zoiets zou de slag kunnen slaan: <br /> \"Hallo! Ik probeerde toegang tot uw site xyz.com te krijgen tijdens het gebruik van Tor Browser en ontdekte dat u Tor gebruikers geen toegang tot uw site verleent. Ik dring er bij u op aan om deze beslissing opnieuw te overwegen; gebruikt door mensen over de hele wereld om hun privacy te beschermen en censuur te bestrijden. Door Tor-gebruikers te blokkeren, blokkeert u waarschijnlijk mensen in repressieve landen die een gratis internet willen gebruiken, journalisten en onderzoekers die zichzelf willen beschermen tegen ontdekking, klokkenluiders , activisten en gewone mensen die willen opteren voor invasieve tracking door derden. Stel u ten stelligste voor ten gunste van digitale privacy en internetvrijheid en geef Tor-gebruikers toegang tot xyz.com. Dank u. \"<br />In het geval van banken en andere gevoelige websites, is het ook gebruikelijk om op geografie gebaseerde blokkering te zien (als een bank weet dat u over het algemeen toegang hebt tot hun services vanuit het ene land en plotseling verbinding maakt via een uitgaande relais aan de andere kant van de wereld, is uw account mogelijk vergrendeld Of geschorst). Als u geen verbinding kunt maken met een onion service, raadpleegt u <a href=\"http://127.0.0.1:5000/#onionservices-3\">Ik kan X.onion niet bereiken! </a></p>" + }, + "censorship-3": { + "id": "#censuur-3", + "control": "censuur-3", + "title": "Hoe kan ik Tor downloaden als het torproject.org is geblokkeerd?", + "description": "<p class=\"mb-3\">Als u Tor niet via onze <mark><a href=\"https://www.torproject.org\">website</a></mark> kunt downloaden, kunt u via GetTor een exemplaar van Tor aan u laten bezorgen. GetTor is een service die automatisch reageert op berichten met links naar de nieuwste versie van Tor Browser, gehost op verschillende locaties die minder vaak worden gecensureerd, zoals Dropbox, Google Drive en Github.</p>" + }, + "censorship-4": { + "id": "#censuur-4", + "control": "censuur-4", + "title": "Ik kan geen verbinding maken met de Tor-browser, wordt mijn netwerk gecensureerd?", + "description": "<p class=\"mb-3\">Mogelijk bevindt u zich op een gecensureerd netwerk en moet u dus proberen bruggen te gebruiken. Sommige bruggen zijn ingebouwd in Tor Browser en u kunt die bruggen gebruiken door \"configure\" te kiezen (gevolgd door de aanwijzingen) in het Tor Launcher-venster dat verschijnt wanneer u Tor Browser voor de eerste keer opent. Als u andere bruggen nodig heeft, kunt u ze vinden op onze <mark><a href=\"https://bridges.torproject.org/\">Bridges-website</a></mark>.Voor meer informatie over bruggen, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser-handleiding</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censuur-5", + "control": "censuur-5", + "title": "Ik ondervind problemen bij het verbinding maken met Tor, en ik vind maar niet wat er fout gaat.", + "description": "<p class=\"mb-3\">Als u problemen ondervindt bij het verbinden, selecteert u de optie om \"Tor log naar klembord te kopiÃ«ren\". Plak vervolgens het Tor-log in een tekstbestand of een ander document. U zou een van deze Vaak voorkomend logfouten moeten zien (kijk naar de volgende regels in uw Tor-logboek): </p><h5>Vaak voorkomend logboekfout # 1: Proxy-verbindingsfout</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09: 23: 40.800 [LET OP] Opening Socks luisteraar op 127.0.0.1 : 9150 \n 2017-10-29 09: 23: 47.900 [LET OP] Bootstrapped 5%: verbinden met directoryserver \n 2017-10-29 09: 23: 47.900 [LETICE] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-clie nt: kan toxx..xxx..xxx.xx: xxxxx niet verbinden (\"algemene SOCKS-serverstoring\") </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, is dit betekent dat u geen verbinding kunt maken met een SOCKS-proxy. Als een SOCKS-proxy vereist is voor uw netwerkconfiguratie, moet u ervoor zorgen dat u uw proxy-gegevens correct hebt ingevoerd. Als een SOCKS-proxy niet vereist is, of als u het niet zeker weet, probeer dan verbinding te maken met het Tor-netwerk zonder een SOCKS-proxy.<p><h5>Gebruikslog fout # 2: Kan relais niet bereiken</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM .500 [LET OP] Luisteraar luisterpositie openen op 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [LET OP] Bootstrapped 80%: Verbinding maken met het Tor-netwerk \n 11/1/2017 21:11:44 PM.300 [WARN] Kan knooppunt voor hop 0 van ons pad niet vinden. Dit circuit weggooien. \n 11/1/2017 21:11:44 PM.500 [LET OP] Bootstrap 85%: Handshake beÃ«indigen met eerste hop \n 11/1/2017 21:11:45 P M.300 [WARN] Kan knooppunt niet vinden voor hop 0 van ons pad. Dit circuit verwijderen.</code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dit dat uw Tor geen verbinding kon maken met het eerste knooppunt in het Tor-circuit. Dit kan betekenen dat u zich op een netwerk bevindt dat gecensureerd is. Probeer te verbinden met bruggen, en dat zou het probleem moeten verhelpen.</p><h5> Algemene logfout # 3: Kan TLS-handshake niet voltooien</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 13-11-17 19: 53: 49.300 [WARN] Probleem met bootstrappen. Vastgelopen met 10%: handshake beÃ«indigen met directoryserver. (GEDAAN, GEDAAN, aantal 10; advieswaarschuwing; host [host] op xxx.xxx.xxx.xx: xxx) \n 13-11-17 19: 53: 49.300 [WARN] 10 verbindingen zijn mislukt: \n 13-11-17 19: 53: 49.300 [WARN] 9 verbindingen stierven in staatshandshaking (TLS) met SSL-status SSLv2 / v3 lezen server hallo A in HANDSHAKE \n 13-11-17 19: 53: 49.300 [WARN] 1 verbindingen zijn overleden in state connect () ing met SSL-staat (No SSL-object) </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dat Tor een TLS-handshake niet kon voltooien met de directory-autoriteiten. Het gebruik van bruggen lost dit waarschijnlijk op.</p><h5>Veel logboekfout # 4: Klok skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00: 04: 47.400 [LET OP] Opening Socks luisteraar op 127.0.0.1:9150 \n 19.11.2017 00: 04: 48.000 [LET OP] Bootstrap 5%: verbinding maken met directoryserver \n 19.11.2017 00: 04: 48.200 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 19.11.2017 00: 04: 48.800 [WARN] NETINFO-cel ontvangen met scheve tijd (OF: xxx.xx.x.xx: xxxx): het lijkt erop dat onze klok 1 dag, 0 uur, 1 minuut achterloopt, of die van hen liggen voor de deur. \n Tor vereist een nauwkeurige klok om te werken: controleer uw tijd-, tijdzone- en datuminstellin gen.</code></pre></p><p class=\"mb-3\">Als u lijnen zoals deze in uw Tor-logboek ziet, betekent dit dat uw systeemklok onjuist is. Zorg ervoor dat uw klok correct is ingesteld, inclusief de juiste tijdzone. Start dan Tor opnieuw. </p>" + }, + "censorship-6": { + "id": "#censuur-6", + "control": "censuur-6", + "title": "Ik kan geen verbinding maken met de Tor-browser, wordt mijn netwerk gecensureerd?", + "description": "<p class=\"mb-3\">Mogelijk bevindt u zich op een gecensureerd netwerk en moet u dus proberen bruggen te gebruiken. Sommige bruggen zijn ingebouwd in Tor Browser en u kunt die bruggen gebruiken door \"configure\" te kiezen (gevolgd door de aanwijzingen) in het Tor Launcher-venster dat verschijnt wanneer u Tor Browser voor de eerste keer opent. Als u andere bruggen nodig heeft, kunt u ze vinden op onze <mark><a href=\"https://bridges.torproject.org/\">Bridges-website</a></mark>.Voor meer informatie over bruggen, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser-handleiding</a></mark>.</p>" + } + + +} diff --git a/pt_BR.json b/pt_BR.json new file mode 100644 index 000000000..75c340dd5 --- /dev/null +++ b/pt_BR.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censura-1", + "control": "censura-1", + "title": "Nosso site estÃ¡ bloqueado por um censor. O Navegador Tor pode ajudar aos usuÃ¡rios a acessar nosso site?", + "description": "<p class=\"mb-3\">O Navegador Tor pode certamente ajudar as pessoas a acessarem seu site em lugares onde ele Ã© bloqueado. Na maioria das vezes, basta baixar oâ<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Navegador Tor</a></mark> e usÃ¡-lo para navegar atÃ© o site bloqueado para permitir o acesso. Em locais onde hÃ¡ uma forte censura, temos vÃ¡rias opÃ§Ãµes de contornar a censura disponÃveis, incluindo â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">transportes plugÃ¡veis</a></mark>. Para mais informaÃ§Ãµes, consulte o<mark>Manual do UsuÃ¡rio do Navegador Tor</a>sobre censura</mark>.</p>" + }, + "censorship-2": { + "id": "#censura-2", + "control": "censura-2", + "title": "Meu website favorito estÃ¡ bloqueando o acesso via Tor.", + "description": "<p class=\"mb-3\"> Lamentamos saber que vocÃª nÃ£o pode visitar o website que quer! Ãs vezes, os websites bloqueam os usuÃ¡rios do Tor porque nÃ£o sabem a diferenÃ§a entre o usuÃ¡rio mÃ©dio e o trÃ¡fego automatizado. Uma estratÃ©gia na qual temos obtido sucesso para fazer os websites desbloquearem os usuÃ¡rios do Tor Ã© fazer com que os prÃ³prios usuÃ¡rios contatem os administradores do site diretamente. Algo assim deve funcionar: <br /> \"OlÃ¡! Eu tentei acessar seu website xyz.com enquanto utilizando o Tor Browser e descobri que nÃ£o hÃ¡ permissÃ£o de acesso para usuÃ¡rios do Tor. Eu peÃ§o que reconsiderem essa decisÃ£o; o Tor Ã© utilizado por pessoas de todo o mundo que querem proteger sua privacidade e lutar contra a censura. Ao bloquear os usuÃ¡rios do Tor, vocÃªs estÃ£o provavelmente bloqueando pessoas que querem usar uma internet livre em paÃses opressores, jornalistas e pesquisadores que querem se proteger, ativistas e pessoas comuns que querem se livrar d o rastreamento de terceiros invasivos. Por favor, tomem uma posiÃ§Ã£o forte em favor da privacidade digital e da liberdade na internet e permitam os usuÃ¡rios do Tor o acesso ao xyz.com. Obrigado.\" <br />No caso dos bancos, e outros sensitive websites, Ã© tambÃ©m comum que apareÃ§am bloqueios baseados na localizaÃ§Ã£o geogrÃ¡fica (se um banco sabe que vocÃª geralmente acessa seus serviÃ§os de um paÃs, e de repente vocÃª estÃ¡ conectando de uma exit relay no outro lado do mundo, sua conta pode ser trancada ou suspensa). Se vocÃª nÃ£o consegue se conectar a um onion service, por favor ver <a href=\"http://127.0.0.1:5000/#onionservices-3\">NÃ£o consigo acessar X.onion! </a> </p>" + }, + "censorship-3": { + "id": "#censura-3", + "control": "censura-3", + "title": "Como eu baixo Tor caso torproject.org esteja bloqueado?", + "description": "<p class=\"mb-3\">Se nÃ£o conseguir fazer o download usando o <mark><a href=\"https://www.torproject.org\"> website </a></mark>, vocÃª pode obter uma cÃ³pia do Tor via GetTor. GetTor Ã© um serviÃ§o que automaticamente responde Ã s mensagens com links para a Ãºltima versÃ£o do Navegador Tor, hospedado em uma variedade de locais menos propensos a serem censurados, como Dropbox, Google Drive e GitHub. </p>" + }, + "censorship-4": { + "id": "#censura-4", + "control": "censura-4", + "title": "Eu nÃ£o consigo conectar ao Tor Browser, a minha rede estÃ¡ censurada?", + "description": "<p class=\"mb-3\">VocÃª pode estar em uma rede censurada e, assim, vocÃª deveria tentar usar bridges. Algumas bridges sÃ£o construÃdas no Tor Browser e vocÃª pode usÃ¡-las escolhendo \"configure\" (e seguir as instruÃ§Ãµes) na janela Tor Launcher que aparece quando vocÃª abre o Tor Browser pela primeira vez. Se vocÃª precisar de outras bridges, vocÃª pode consegui-las em nosso <mark><a href=\"https://bridges.torproject.org/\">Bridges website </a></mark>. Para mais informaÃ§Ãµes sobre bridges, veja o <a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manual do Tor Browser </a><mark>.</mark>" + }, + "censorship-5": { + "id": "#censura-5", + "control": "censura-5", + "title": "Estou tendo problemas para conectar ao Tor e nÃ£o consigo descobrir o que estÃ¡ dando errado.", + "description": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opÃ§Ã£o para \"copiar o log de Tor para a Ã¡rea de transferÃªncias\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. VocÃª deverÃ¡ ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexÃ£o de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretÃ³rio\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretÃ³rio\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0 8.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se vocÃª encontrar linhas como estas em seu log do Tor, isto significa que falhou em conectar-se Ã um SOCKS proxy. Se um SOCKS proxy Ã© obrigatÃ³rio para a sua configuraÃ§Ã£o de rede, por favor certifique-se que vocÃª digitou seus detalhes de proxy corretamente. Se um SOCKS proxy nÃ£o Ã© obrigatÃ³rio, ou vocÃª nÃ£o estÃ¡ certo sobre isso, por favor tente conectar-se Ã rede Tor sem um SOCKS proxy. Erro de log comum #2: Canât reach guard relays 11/1/2017 21:11:43 PM.500 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [OBSERVE] Bootstrapped 80%: Conectando Ã rede Tor\n11/1/2017 21:11:44 PM.300 [AVISO] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [OBSERVE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [AVISO] 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\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hands hake 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\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor 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. " + }, + "censorship-6": { + "id": "#censura-6", + "control": "censura-6", + "title": "Eu nÃ£o consigo me conectar ao Navegador Tor, minha rede estÃ¡ censurada?", + "description": "<p class=\"mb-3\">VocÃª deve estar em uma internet censurada, e por isso vocÃª deve tentar usar pontes. Algumas pontes jÃ¡ sÃ£o feitas para o Navegador Tor, e vocÃª pode usar estas pontes selecionando \"configurar\" (e seguir os passos) na janela de inicializaÃ§Ã£o do Tor que aparece quando vocÃª abre o Navegador Tor pela primeira vez. Se vocÃª precisar de outras pontes, vocÃª pode consegui-las em nosso <mark><a href=\"https://bridges.torproject.org/\">website de Pontes</a></mark>. Para mais informaÃ§Ãµes sobre pontes, veja o <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manual do Navegador Tor</a></mark>.</p>" + } + + +} diff --git a/support-censorship.json b/support-censorship.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/support-censorship.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/zh_CN.json b/zh_CN.json new file mode 100644 index 000000000..69f34533c --- /dev/null +++ b/zh_CN.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#å®¡æ¥-1", + "control": "å®¡æ¥-1", + "title": "æççœç«è¢«å®¡æ¥æºæå±èœäºïŒTor Browser èœåž®å©çšæ·è®¿é®æççœç«åïŒ", + "description": "<p class=\"mb-3\">Tor Browser åœç¶å¯ä»¥åž®å©äººä»¬åšçœç»åå®¡æ¥çå°åºè®¿é®è¢«å±èœççœç«ãå€§å€æ°æ¶ååªéèŠäžèœœ<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser </a></mark>å¹¶äœ¿çšå®è¿è¡æµè§å³å¯ãåšçœç»å®¡æ¥ååäž¥æ Œçå°åºïŒæä»¬è¿æäŸäºè®žå€è§é¿æªæœïŒäŸåŠ<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>ãè¯·åé<mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser çšæ·æå</a></mark>ç<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">å®¡æ¥</a></mark>ç« èä»¥è·åŸæŽå€ä¿¡æ¯ã</p>" + }, + "censorship-2": { + "id": "#å®¡æ¥-2", + "control": "å®¡æ¥-2", + "title": "ææç±ççœç«å±èœæ¥èª Tor çè®¿é®ã", + "description": "<p class=\"mb-3\">äžèœè®¿é®äœ æ³èŠççœç«çæ¯éæŸå¢ïŒæäºçœç«å±èœäº Tor å äžºä»ä»¬æ æ³åèŸšåºæ®é Tor çšæ·åæºåšäººçåºå«ãæ ¹æ®è¿å»çç»éªïŒæ³èŠè®©çœç«è§£å°æ¥èª Tor çè®¿é®æææçæ¹æ³æ¯ç±çšæ·çŽæ¥èç³»çœç«ç®¡çåãä¹è®žè¿æ ·çæ¶æ¯å°±å¯ä»¥æåïŒ<br />âåšïŒåšçš Tor Browser çæ¶ååç°äœ ççœç« xyz.com äžåè®žæ¥èª Tor çè®¿é®ïŒåžæäœ å¯ä»¥éæ°èèè¿äžªå³å®ãåšçåå°åŸå€äººéœåšäœ¿çš Tor æ¥ä¿æ€éç§åå¯¹æå®¡æ¥ïŒå±èœ Tor çåæ¶äœ ä¹å±èœäºåŒºæåœå®¶äžæ³èªç±è®¿é®äºèçœççšæ·ãéèŠéèèªå·±çè®°èåæ£äžŸèãæ³èº²é¿çœç»è·èžªçç ç©¶èåæ®éçšæ·ãè¯·ç«åšæ¯æåšçº¿éç§åçœç»èªç±çç«åºäžïŒåè®ž Tor çšæ·è®¿é® xyz.comïŒè°¢è°¢ïŒâ<br />åŠå€ïŒé¶è¡è¿ç±»æ¯èŸææççœç«ç»åžžè¿è¡å°åºèåŽçå±èœãåŠæäœ å¹³æ¶åªåšæäžªç¹å®çåœå®¶äœ¿çšä»ä»¬çæå¡ïŒä»äœäº å¶ä»åœå®¶çåºå£èç¹è¿è¡è®¿é®æ¶äœ çèŽŠå·å¯èœå°±äŒè¢«å»ç»ãåŠæ æ³è¿æ¥ onion æå¡ïŒè¯·åé <a href=\"http://127.0.0.1:5000/#onionservices-3\">æ æ³è¿æ¥ x.onionïŒ</a></p>" + }, + "censorship-3": { + "id": "#å®¡æ¥-3", + "control": "å®¡æ¥-3", + "title": "torproject.org è¢«å±èœäºïŒæä¹äžèœœ TorïŒ", + "description": "<p class=\"mb-3\">åŠææ æ³éè¿æä»¬ç<mark><a href=\"https://www.torproject.org\">çœç«</a></mark>äžèœœ TorïŒäœ å¯ä»¥éè¿ GetTor è·å TorãGetTor äŒèªåšåéäžèœœ Tor Browser ææ°çæ¬çéŸæ¥ïŒç± DropboxãGoogle DriveãGitHub çæŽéŸåå°å®¡æ¥ççœç«è¿è¡ååã</p>" + }, + "censorship-4": { + "id": "#å®¡æ¥-4", + "control": "å®¡æ¥-4", + "title": "æ æ³è¿æ¥ TorïŒæççœç»è¢«å®¡æ¥äºåïŒ", + "description": "<p class=\"mb-3\">äœ å¯èœåšäœ¿çšåå®¡æ¥ççœç»ïŒè¯·å°è¯çœæ¡¥æ¥è¿è¡åºå¯¹ãTor Browser äžåçœ®äºäžäºçœæ¡¥ïŒäœ å¯ä»¥åš Tor Browser éŠæ¬¡å¯åšæ¶åŒ¹åºç Tor Launcher çªå£äžéæ©âè®Ÿçœ®âïŒç¶åè·éæç€ºïŒæ¥å¯çšãåŠæéèŠå¶ä»çœæ¡¥ïŒæä»¬ç<mark><a href=\"https://bridges.torproject.org/\">çœæ¡¥ç«ç¹</a></mark>å¯ä»¥æäŸå®ä»¬ãå³äºçœæ¡¥çæŽå€ä¿¡æ¯è¯·åé<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser çšæ·æå</a></mark>ã</p>" + }, + "censorship-5": { + "id": "#å®¡æ¥-5", + "control": "å®¡æ¥-5", + "title": "æ æ³è¿æ¥å° TorïŒäœæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", + "description": "<p class=\"mb-3\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæ šçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§æ¥å¿éè¯¯#3: TLSæ¡æå€±èŽ¥</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor äžäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5> åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \nToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœãè¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ã</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" + }, + "censorship-6": { + "id": "#å®¡æ¥-6", + "control": "å®¡æ¥-6", + "title": "æ æ³è¿æ¥ TorïŒæççœç»è¢«å®¡æ¥äºåïŒ", + "description": "<p class=\"mb-3\">äœ å¯èœåšäœ¿çšåå®¡æ¥ççœç»ïŒè¯·å°è¯çœæ¡¥æ¥è¿è¡åºå¯¹ãTor Browser äžåçœ®äºäžäºçœæ¡¥ïŒäœ å¯ä»¥åš Tor Browser éŠæ¬¡å¯åšæ¶åŒ¹åºç Tor Launcher çªå£äžéæ©âè®Ÿçœ®âïŒç¶åè·éæç€ºïŒæ¥å¯çšãåŠæéèŠå¶ä»çœæ¡¥ïŒæä»¬ç<mark><a href=\"https://bridges.torproject.org/\">çœæ¡¥ç«ç¹</a></mark>å¯ä»¥æäŸå®ä»¬ãå³äºçœæ¡¥çæŽå€ä¿¡æ¯è¯·åé<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser çšæ·æå</a></mark>ã</p>" + } + + +}

1 0

[translation/support-censorship] pulling translations from transifex
by translation＠torproject.org 06 Apr '18

06 Apr '18

commit f0b627c73ebe13e1d5b9ce9f0e0d3af38bc505c8 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Apr 6 23:28:00 2018 +0000 pulling translations from transifex --- ach.json | 40 ++++++++++++++++++++++++++++++++++++++++ ady.json | 40 ++++++++++++++++++++++++++++++++++++++++ af.json | 40 ++++++++++++++++++++++++++++++++++++++++ ak.json | 40 ++++++++++++++++++++++++++++++++++++++++ am.json | 40 ++++++++++++++++++++++++++++++++++++++++ ar.json | 40 ++++++++++++++++++++++++++++++++++++++++ arn.json | 40 ++++++++++++++++++++++++++++++++++++++++ ast.json | 40 ++++++++++++++++++++++++++++++++++++++++ az.json | 40 ++++++++++++++++++++++++++++++++++++++++ ba.json | 40 ++++++++++++++++++++++++++++++++++++++++ be.json | 40 ++++++++++++++++++++++++++++++++++++++++ bg.json | 40 ++++++++++++++++++++++++++++++++++++++++ bn.json | 40 ++++++++++++++++++++++++++++++++++++++++ bn_BD.json | 40 ++++++++++++++++++++++++++++++++++++++++ bn_IN.json | 40 ++++++++++++++++++++++++++++++++++++++++ bo.json | 40 ++++++++++++++++++++++++++++++++++++++++ br.json | 40 ++++++++++++++++++++++++++++++++++++++++ brx.json | 40 ++++++++++++++++++++++++++++++++++++++++ bs.json | 40 ++++++++++++++++++++++++++++++++++++++++ ca.json | 40 ++++++++++++++++++++++++++++++++++++++++ ceb.json | 40 ++++++++++++++++++++++++++++++++++++++++ cs.json | 40 ++++++++++++++++++++++++++++++++++++++++ csb.json | 40 ++++++++++++++++++++++++++++++++++++++++ cv.json | 40 ++++++++++++++++++++++++++++++++++++++++ cy.json | 40 ++++++++++++++++++++++++++++++++++++++++ da.json | 40 ++++++++++++++++++++++++++++++++++++++++ de.json | 40 ++++++++++++++++++++++++++++++++++++++++ dz.json | 40 ++++++++++++++++++++++++++++++++++++++++ el.json | 40 ++++++++++++++++++++++++++++++++++++++++ en_GB.json | 40 ++++++++++++++++++++++++++++++++++++++++ eo.json | 40 ++++++++++++++++++++++++++++++++++++++++ es.json | 40 ++++++++++++++++++++++++++++++++++++++++ es_AR.json | 40 ++++++++++++++++++++++++++++++++++++++++ es_CL.json | 40 ++++++++++++++++++++++++++++++++++++++++ es_CO.json | 40 ++++++++++++++++++++++++++++++++++++++++ es_MX.json | 40 ++++++++++++++++++++++++++++++++++++++++ et.json | 40 ++++++++++++++++++++++++++++++++++++++++ eu.json | 40 ++++++++++++++++++++++++++++++++++++++++ fa.json | 40 ++++++++++++++++++++++++++++++++++++++++ fi.json | 40 ++++++++++++++++++++++++++++++++++++++++ fil.json | 40 ++++++++++++++++++++++++++++++++++++++++ fo.json | 40 ++++++++++++++++++++++++++++++++++++++++ fr.json | 40 ++++++++++++++++++++++++++++++++++++++++ fr_CA.json | 40 ++++++++++++++++++++++++++++++++++++++++ fur.json | 40 ++++++++++++++++++++++++++++++++++++++++ fy.json | 40 ++++++++++++++++++++++++++++++++++++++++ ga.json | 40 ++++++++++++++++++++++++++++++++++++++++ gd.json | 40 ++++++++++++++++++++++++++++++++++++++++ gl.json | 40 ++++++++++++++++++++++++++++++++++++++++ gu.json | 40 ++++++++++++++++++++++++++++++++++++++++ gu_IN.json | 40 ++++++++++++++++++++++++++++++++++++++++ gun.json | 40 ++++++++++++++++++++++++++++++++++++++++ ha.json | 40 ++++++++++++++++++++++++++++++++++++++++ he.json | 40 ++++++++++++++++++++++++++++++++++++++++ hi.json | 40 ++++++++++++++++++++++++++++++++++++++++ hr.json | 40 ++++++++++++++++++++++++++++++++++++++++ hr_HR.json | 40 ++++++++++++++++++++++++++++++++++++++++ ht.json | 40 ++++++++++++++++++++++++++++++++++++++++ hu.json | 40 ++++++++++++++++++++++++++++++++++++++++ hy.json | 40 ++++++++++++++++++++++++++++++++++++++++ ia.json | 40 ++++++++++++++++++++++++++++++++++++++++ id.json | 40 ++++++++++++++++++++++++++++++++++++++++ is.json | 40 ++++++++++++++++++++++++++++++++++++++++ it.json | 40 ++++++++++++++++++++++++++++++++++++++++ ja.json | 40 ++++++++++++++++++++++++++++++++++++++++ jv.json | 40 ++++++++++++++++++++++++++++++++++++++++ ka.json | 40 ++++++++++++++++++++++++++++++++++++++++ kk.json | 40 ++++++++++++++++++++++++++++++++++++++++ km.json | 40 ++++++++++++++++++++++++++++++++++++++++ kn.json | 40 ++++++++++++++++++++++++++++++++++++++++ ko.json | 40 ++++++++++++++++++++++++++++++++++++++++ ko_KR.json | 40 ++++++++++++++++++++++++++++++++++++++++ ku.json | 40 ++++++++++++++++++++++++++++++++++++++++ ku_IQ.json | 40 ++++++++++++++++++++++++++++++++++++++++ kw.json | 40 ++++++++++++++++++++++++++++++++++++++++ ky.json | 40 ++++++++++++++++++++++++++++++++++++++++ la.json | 40 ++++++++++++++++++++++++++++++++++++++++ lb.json | 40 ++++++++++++++++++++++++++++++++++++++++ lg.json | 40 ++++++++++++++++++++++++++++++++++++++++ ln.json | 40 ++++++++++++++++++++++++++++++++++++++++ lo.json | 40 ++++++++++++++++++++++++++++++++++++++++ lt.json | 40 ++++++++++++++++++++++++++++++++++++++++ lv.json | 40 ++++++++++++++++++++++++++++++++++++++++ mg.json | 40 ++++++++++++++++++++++++++++++++++++++++ mi.json | 40 ++++++++++++++++++++++++++++++++++++++++ mk.json | 40 ++++++++++++++++++++++++++++++++++++++++ ml.json | 40 ++++++++++++++++++++++++++++++++++++++++ mn.json | 40 ++++++++++++++++++++++++++++++++++++++++ mr.json | 40 ++++++++++++++++++++++++++++++++++++++++ ms_MY.json | 40 ++++++++++++++++++++++++++++++++++++++++ mt.json | 40 ++++++++++++++++++++++++++++++++++++++++ my.json | 40 ++++++++++++++++++++++++++++++++++++++++ nah.json | 40 ++++++++++++++++++++++++++++++++++++++++ nap.json | 40 ++++++++++++++++++++++++++++++++++++++++ nb.json | 40 ++++++++++++++++++++++++++++++++++++++++ nds.json | 40 ++++++++++++++++++++++++++++++++++++++++ ne.json | 40 ++++++++++++++++++++++++++++++++++++++++ nl.json | 40 ++++++++++++++++++++++++++++++++++++++++ nl_BE.json | 40 ++++++++++++++++++++++++++++++++++++++++ nn.json | 40 ++++++++++++++++++++++++++++++++++++++++ nso.json | 40 ++++++++++++++++++++++++++++++++++++++++ oc.json | 40 ++++++++++++++++++++++++++++++++++++++++ om.json | 40 ++++++++++++++++++++++++++++++++++++++++ or.json | 40 ++++++++++++++++++++++++++++++++++++++++ pa.json | 40 ++++++++++++++++++++++++++++++++++++++++ pap.json | 40 ++++++++++++++++++++++++++++++++++++++++ pl.json | 40 ++++++++++++++++++++++++++++++++++++++++ pms.json | 40 ++++++++++++++++++++++++++++++++++++++++ ps.json | 40 ++++++++++++++++++++++++++++++++++++++++ pt.json | 40 ++++++++++++++++++++++++++++++++++++++++ pt_BR.json | 40 ++++++++++++++++++++++++++++++++++++++++ ro.json | 40 ++++++++++++++++++++++++++++++++++++++++ ru.json | 40 ++++++++++++++++++++++++++++++++++++++++ ru(a)petr1708.json | 40 ++++++++++++++++++++++++++++++++++++++++ scn.json | 40 ++++++++++++++++++++++++++++++++++++++++ sco.json | 40 ++++++++++++++++++++++++++++++++++++++++ si_LK.json | 40 ++++++++++++++++++++++++++++++++++++++++ sk.json | 40 ++++++++++++++++++++++++++++++++++++++++ sk_SK.json | 40 ++++++++++++++++++++++++++++++++++++++++ sl.json | 40 ++++++++++++++++++++++++++++++++++++++++ sl_SI.json | 40 ++++++++++++++++++++++++++++++++++++++++ sn.json | 40 ++++++++++++++++++++++++++++++++++++++++ so.json | 40 ++++++++++++++++++++++++++++++++++++++++ son.json | 40 ++++++++++++++++++++++++++++++++++++++++ sq.json | 40 ++++++++++++++++++++++++++++++++++++++++ sr.json | 40 ++++++++++++++++++++++++++++++++++++++++ sr(a)latin.json | 40 ++++++++++++++++++++++++++++++++++++++++ st.json | 40 ++++++++++++++++++++++++++++++++++++++++ su.json | 40 ++++++++++++++++++++++++++++++++++++++++ support-censorship.json | 40 ++++++++++++++++++++++++++++++++++++++++ sv.json | 40 ++++++++++++++++++++++++++++++++++++++++ sw.json | 40 ++++++++++++++++++++++++++++++++++++++++ szl.json | 40 ++++++++++++++++++++++++++++++++++++++++ ta.json | 40 ++++++++++++++++++++++++++++++++++++++++ te.json | 40 ++++++++++++++++++++++++++++++++++++++++ te_IN.json | 40 ++++++++++++++++++++++++++++++++++++++++ tg.json | 40 ++++++++++++++++++++++++++++++++++++++++ th.json | 40 ++++++++++++++++++++++++++++++++++++++++ ti.json | 40 ++++++++++++++++++++++++++++++++++++++++ tk.json | 40 ++++++++++++++++++++++++++++++++++++++++ tr.json | 40 ++++++++++++++++++++++++++++++++++++++++ tzm.json | 40 ++++++++++++++++++++++++++++++++++++++++ ug(a)Arab.json | 40 ++++++++++++++++++++++++++++++++++++++++ uk.json | 40 ++++++++++++++++++++++++++++++++++++++++ ur.json | 40 ++++++++++++++++++++++++++++++++++++++++ ur_PK.json | 40 ++++++++++++++++++++++++++++++++++++++++ uz.json | 40 ++++++++++++++++++++++++++++++++++++++++ ve.json | 40 ++++++++++++++++++++++++++++++++++++++++ vi.json | 40 ++++++++++++++++++++++++++++++++++++++++ wa.json | 40 ++++++++++++++++++++++++++++++++++++++++ wo.json | 40 ++++++++++++++++++++++++++++++++++++++++ zh_CN.json | 40 ++++++++++++++++++++++++++++++++++++++++ zh_HK.json | 40 ++++++++++++++++++++++++++++++++++++++++ zh_TW.json | 40 ++++++++++++++++++++++++++++++++++++++++ zu.json | 40 ++++++++++++++++++++++++++++++++++++++++ 155 files changed, 6200 insertions(+) diff --git a/ach.json b/ach.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ach.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ady.json b/ady.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ady.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/af.json b/af.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/af.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ak.json b/ak.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ak.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/am.json b/am.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/am.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ar.json b/ar.json new file mode 100644 index 000000000..f8e8feb7f --- /dev/null +++ b/ar.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "ÙÙÙ ÙÙÙÙÙÙ ØªÙØ²ÙÙ ØªÙØ± Ø¥Ù ÙØ§Ù ÙÙÙØ¹ torproject.org ÙØØ¬ÙØšÙØ§ Ø", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Ø£ÙØ§Ø¬Ù ØµØ¹ÙØšØ© ÙÙ Ø§ÙØ¥ØªØµØ§Ù ØšØŽØšÙØ© ØªÙØ± ÙÙØ§ Ø£Ø¯Ø±Ù Ø£ÙÙ ØªÙÙÙ Ø§ÙÙÙØŽÙÙØ©.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/arn.json b/arn.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/arn.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ast.json b/ast.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ast.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/az.json b/az.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/az.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ba.json b/ba.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ba.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/be.json b/be.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/be.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/bg.json b/bg.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/bg.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/bn.json b/bn.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/bn.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/bn_BD.json b/bn_BD.json new file mode 100644 index 000000000..d5005ce06 --- /dev/null +++ b/bn_BD.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-1", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-1", + "title": "àŠàŠ®àŠŸàŠŠà§àŠ° àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠ àŠàŠàŠàŠ¿ àŠžà§àŠšà§àŠžàŠ° àŠŠà§àŠ¬àŠŸàŠ°àŠŸ àŠàŠ¬àŠ°à§àŠŠà§àŠ§ àŠ¹àŠ¯àŠŒà¥€ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠ¿ àŠàŠ®àŠŸàŠŠà§àŠ° àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠžàŠŸàŠ¹àŠŸàŠ¯à§àŠ¯ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§àŠš?", + "description": "<p class=\"mb-3\">àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠ¬àŠ¶à§àŠ¯àŠ àŠ®àŠŸàŠšà§àŠ·àŠà§ àŠžàŠŸàŠ¹àŠŸàŠ¯à§àŠ¯ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§ àŠàŠªàŠšàŠŸàŠ° àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠà§ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°àŠ€à§ àŠ¯à§àŠàŠŸàŠšà§ àŠàŠàŠ¿ àŠàŠ¬àŠ°à§àŠŠà§àŠ§ àŠ°àŠ¯àŠŒà§àŠà§à¥€àŠ¬à§àŠ¶àŠ¿àŠ°àŠàŠŸàŠ àŠžàŠ®àŠ¯àŠŒ,<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\"> àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠ¡àŠŸàŠàŠšàŠ²à§àŠ¡ àŠàŠ°àŠŸ </a></mark>àŠàŠ¬àŠ àŠ€àŠŸàŠ°àŠªàŠ° àŠàŠàŠ¿ àŠ¬à§àŠ²àŠ àŠàŠ°àŠŸ àŠžàŠŸàŠàŠà§ àŠšà§àŠàŠ¿àŠà§àŠ àŠàŠ°àŠŸàŠ° àŠàŠšà§àŠ¯ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠžà§àŠ° àŠàŠšà§àŠ®àŠ€àŠ¿ àŠŠà§àŠ¬à§à¥€ àŠ¯à§ àŠàŠŸàŠ¯àŠŒàŠàŠŸàŠ¯àŠŒ àŠªà§àŠ°àŠà§àŠ° àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª àŠ°àŠ¯àŠŒà§àŠà§, àŠ€àŠŸ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠžà§àŠ° àŠàŠšà§àŠ¯ àŠàŠ®àŠŸàŠŠà§àŠ° àŠàŠŸàŠà§ àŠªà§àŠ°àŠà§àŠ° àŠªàŠ°àŠ¿àŠ®àŠŸàŠ£à§ àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª àŠªà§àŠ°àŠ€àŠŸàŠ°àŠ£àŠŸ àŠ¬àŠ¿àŠàŠ²à§à Šª àŠàŠà§, <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">àŠªà§àŠ²à§àŠ¯àŠŸàŠà§àŠ¬àŠ² àŠà§àŠ°àŠŸàŠšà§àŠžàŠªà§àŠ°à§àŠàŠà§àŠ²àŠ¿ àŠžàŠ¹ àŠàŠ®àŠš</a></mark>à¥€àŠàŠ°à§ àŠ€àŠ¥à§àŠ¯à§àŠ° àŠàŠšà§àŠ¯, àŠŠà§àŠà§àŠš àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠàŠàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ²<a href=\"https://tb-manual.torproject.org/en-US/\"><mark> àŠ¬àŠ¿àŠàŠŸàŠ<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\"> àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠªà§àŠ° àŠàŠªàŠ°</a></mark>à¥€</p>" + }, + "censorship-2": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-2", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-2", + "title": "àŠàŠ®àŠŸàŠ° àŠªà§àŠ°àŠ¿àŠ¯àŠŒ àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠ àŠàŠ° àŠªàŠ°à§àŠ¯àŠšà§àŠ€ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ¬àŠ°à§àŠŠà§àŠ§ àŠàŠ°àŠà§", + "description": "<p class=\"mb-3\">àŠ¶à§àŠšà§ àŠŠà§àŠàŠàŠ¿àŠ€ àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠ¯à§ àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠàŠàŠ¿ àŠàŠŸàŠš àŠ€àŠŸ àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠ°àŠ¬à§àŠš àŠšàŠŸ! àŠàŠàŠšàŠ àŠàŠàŠšàŠ àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠàŠ¬àŠ°à§àŠ§ àŠàŠ°àŠ¬à§ àŠàŠŸàŠ°àŠ£ àŠ€àŠŸàŠ°àŠŸ àŠàŠ¡àŠŒ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§ àŠàŠ¬àŠ àŠžà§àŠ¬àŠ¯àŠŒàŠàŠà§àŠ°àŠ¿àŠ¯àŠŒ àŠà§àŠ°à§àŠ¯àŠŸàŠ«àŠ¿àŠà§àŠ° àŠ®àŠ§à§àŠ¯à§ àŠªàŠŸàŠ°à§àŠ¥àŠà§àŠ¯ àŠ¬àŠ²àŠ€à§ àŠªàŠŸàŠ°à§ àŠšàŠŸà¥€ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠàŠ¬àŠ°à§àŠ§ àŠàŠ°àŠŸ àŠžàŠŸàŠàŠàŠà§àŠ²à§àŠ€à§ àŠàŠ®àŠ°àŠŸ àŠ¯à§ àŠžàŠ«àŠ²àŠ€àŠŸ àŠªà§àŠ¯àŠŒà§àŠàŠ¿ àŠ€àŠŸ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠžàŠŸàŠàŠà§ àŠžàŠ°àŠŸàŠžàŠ°àŠ¿ àŠªà§àŠ°àŠ¶àŠŸàŠžàŠà§àŠ° àŠžàŠŸàŠ¥à§ àŠ¯à§àŠàŠŸàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§à¥€ àŠàŠ àŠ§àŠ°àŠ£à§àŠ° àŠàŠ¿àŠà§ àŠ¹àŠ¯àŠŒàŠ€à§ àŠàŠ àŠà§àŠ¶àŠ²àŠàŠ¿ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ °à§: \"àŠ¹àŠŸàŠ! àŠàŠ®àŠ¿ àŠàŠŸàŠ¯àŠŒàŠŸàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°àŠŸàŠ° àŠžàŠ®àŠ¯àŠŒ àŠàŠªàŠšàŠŸàŠ° àŠžàŠŸàŠàŠ xyz.com àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°àŠŸàŠ° àŠà§àŠ·à§àŠàŠŸ àŠàŠ°à§àŠàŠ¿ àŠàŠ¬àŠ àŠàŠ¬àŠ¿àŠ·à§àŠàŠŸàŠ° àŠàŠ°à§àŠàŠ¿ àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠàŠªàŠšàŠŸàŠ° àŠžàŠŸàŠàŠ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°àŠŸàŠ° àŠàŠšà§àŠ®àŠ€àŠ¿ àŠŠàŠ¿àŠà§àŠà§àŠš àŠšàŠŸà¥€ àŠàŠ®àŠ¿ àŠàŠªàŠšàŠŸàŠà§ àŠàŠ àŠžàŠ¿àŠŠà§àŠ§àŠŸàŠšà§àŠ€à§àŠ° àŠªà§àŠšàŠ°à§àŠ¬àŠ¿àŠ¬à§àŠàŠšàŠŸ àŠàŠ°àŠŸàŠ° àŠàŠšà§àŠ°à§àŠ§ àŠàŠ°àŠàŠ¿; àŠžàŠŸàŠ°àŠŸ àŠ¬àŠ¿àŠ¶à§àŠ¬à§àŠ° àŠ®àŠŸàŠšà§àŠ· àŠ€àŠŸàŠŠà§àŠ° àŠà§àŠªàŠšà§àŠ¯àŠŒàŠ€àŠŸ àŠ°àŠà§àŠ·àŠŸ àŠàŠ¬àŠ àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠªà§àŠ° àŠ¬àŠ¿àŠ°à§àŠŠà§àŠ§à§ àŠ²àŠ¡àŠŒàŠŸàŠ àŠàŠ°à§à¥€ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° àŠ¬à§àŠ²àŠ àŠàŠ°à§, àŠàŠªàŠšàŠ¿ àŠžàŠ®à§àŠàŠ¬àŠ€ àŠŠàŠ®àŠšàŠ®à§àŠ²àŠ àŠŠà§àŠ¶àŠà§àŠ²àŠ¿àŠ€à§ àŠ² à§àŠà§àŠŠà§àŠ°àŠà§ àŠ¬à§àŠ²àŠ àŠàŠ°à§ àŠŠàŠ¿àŠà§àŠà§àŠš àŠ¯àŠŸàŠ°àŠŸ àŠàŠàŠàŠ¿ àŠ«à§àŠ°àŠ¿ àŠàŠšà§àŠàŠŸàŠ°àŠšà§àŠ, àŠžàŠŸàŠàŠ¬àŠŸàŠŠàŠ¿àŠ àŠàŠ¬àŠ àŠàŠ¬à§àŠ·àŠ àŠ¯àŠŸàŠ°àŠŸ àŠšàŠ¿àŠà§àŠŠà§àŠ° àŠàŠ¬àŠ¿àŠ·à§àŠàŠŸàŠ°, àŠ¹à§àŠàŠžàŠ² àŠ¬à§àŠ²à§àŠ¯àŠŒàŠŸàŠ°, àŠà§àŠ¯àŠŸàŠà§àŠàŠ¿àŠàŠ¿àŠžà§àŠ, àŠàŠ¬àŠ àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ®àŠŸàŠšà§àŠ· àŠ¯àŠŸàŠ°àŠŸ àŠàŠà§àŠ°àŠ®àŠ£àŠŸàŠ€à§àŠ®àŠ àŠ€à§àŠ€à§àŠ¯àŠŒ àŠªàŠà§àŠ·à§àŠ° àŠà§àŠ°à§àŠ¯àŠŸàŠàŠ¿àŠ àŠ¥à§àŠà§ àŠàŠªà§àŠ àŠàŠàŠ àŠàŠ°àŠ€à§ àŠàŠŸàŠš àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠ¡àŠ¿àŠàŠ¿àŠàŠŸàŠ² àŠà§àŠªàŠšà§àŠ¯àŠŒàŠ€àŠŸ àŠàŠ¬àŠ àŠàŠšà§àŠàŠŸàŠ°àŠšà§àŠ àŠžà§àŠ¬àŠŸàŠ§à§àŠšàŠ€àŠŸàŠ° àŠªàŠà§àŠ·à§ àŠŠà§àŠ¢àŠŒ àŠàŠ¬àŠžà§àŠ¥àŠŸàŠš àŠšàŠ¿àŠš àŠàŠ¬àŠ àŠàŠ° àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ°àŠàŠŸàŠ°à§àŠŠà§àŠ° xyz.com àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠžà§àŠ° àŠàŠšà§àŠ®àŠ€àŠ¿ àŠŠàŠ¿àŠšà¥€ àŠ§àŠšà§àŠ¯àŠ¬àŠŸàŠŠà¥€ \"àŠ¬à§àŠ¯àŠŸàŠàŠàŠà§àŠ²àŠ¿àŠ° àŠà§àŠ·à§àŠ€à§àŠ°à§ àŠàŠ¬àŠ àŠàŠšà§àŠ¯àŠ ŸàŠšà§àŠ¯ àŠžàŠàŠ¬à§àŠŠàŠšàŠ¶à§àŠ² àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠàŠà§àŠ²àŠ¿, àŠàŠàŠ¿ àŠà§àŠà§àŠ²-àŠàŠ¿àŠ€à§àŠ€àŠ¿àŠ àŠ¬à§àŠ²àŠàŠ¿àŠ àŠŠà§àŠàŠ€à§ àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ (àŠ¯àŠŠàŠ¿ àŠàŠàŠàŠ¿ àŠ¬à§àŠ¯àŠŸàŠàŠ àŠàŠŸàŠšà§ àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠžàŠŸàŠ§àŠŸàŠ°àŠ£àŠ€ àŠàŠ àŠŠà§àŠ¶ àŠ¥à§àŠà§ àŠ€àŠŸàŠŠà§àŠ° àŠªàŠ°àŠ¿àŠ·à§àŠ¬àŠŸàŠà§àŠ²àŠ¿ àŠà§àŠ¯àŠŸàŠà§àŠžà§àŠž àŠàŠ°à§àŠš, àŠàŠ¬àŠ àŠ¹àŠ àŠŸà§ àŠàŠªàŠšàŠ¿ àŠ¬àŠ¿àŠ¶à§àŠ¬à§àŠ° àŠàŠšà§àŠ¯ àŠªà§àŠ°àŠŸàŠšà§àŠ€à§ àŠàŠàŠàŠ¿ àŠªà§àŠ°àŠžà§àŠ¥àŠŸàŠš àŠ°àŠ¿àŠ²à§ àŠ¥à§àŠà§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠà§àŠš, àŠàŠªàŠšàŠŸàŠ° àŠà§àŠ¯àŠŸàŠàŠŸàŠàŠšà§àŠ àŠ²àŠ àŠàŠ°àŠŸ àŠ¹àŠ€à§ àŠªàŠŸàŠ°à§ àŠ¬àŠŸàŠžà§àŠ¥àŠàŠ¿àŠ€). àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠàŠàŠ¿ àŠªà§àŠàŠ¯àŠŒàŠŸàŠ àŠªàŠ°àŠ¿àŠ·à§àŠ¬àŠŸ àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠàŠà§àŠ·àŠ® àŠ¹àŠš, àŠ€àŠ¬à§ àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠŠà§àŠà§àŠš àŠàŠ®àŠ¿ X.onion àŠ€à§ àŠªà§àŠàŠàŠŸàŠ€à§ àŠªàŠŸàŠ°àŠ¿ àŠšàŠŸ!" + }, + "censorship-3": { + "id": "#àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-3", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-3", + "title": "Torproject.org àŠ¬à§àŠ²àŠ àŠàŠ°àŠ²à§ àŠàŠ®àŠ¿ àŠàŠ¿àŠàŠŸàŠ¬à§ àŠàŠ° àŠ¡àŠŸàŠàŠšàŠ²à§àŠ¡ àŠàŠ°àŠ¬?", + "description": "<p class=\"mb-3\">àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠ®àŠŸàŠŠà§àŠ°<mark><a href=\"https://www.torproject.org\"> àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠà§àŠ° àŠ®àŠŸàŠ§à§àŠ¯àŠ®à§</a></mark> àŠàŠ° àŠ¡àŠŸàŠàŠšàŠ²à§àŠ¡ àŠàŠ°àŠ€à§ àŠšàŠŸ àŠªàŠŸàŠ°à§àŠš, àŠàŠªàŠšàŠ¿ GetTor àŠàŠ° àŠ®àŠŸàŠ§à§àŠ¯àŠ®à§ àŠàŠªàŠšàŠŸàŠà§ àŠ¬àŠ¿àŠ€àŠ°àŠ£ àŠàŠ°àŠŸ àŠàŠ° àŠàŠàŠàŠ¿ àŠàŠªàŠ¿ àŠªà§àŠ€à§ àŠªàŠŸàŠ°à§àŠšà¥€ GetTor àŠ¹àŠ² àŠàŠàŠàŠ¿ àŠªàŠ°àŠ¿àŠ·à§àŠ¬àŠŸ àŠ¯àŠŸ àŠžà§àŠ¬àŠ¯àŠŒàŠàŠà§àŠ°àŠ¿àŠ¯àŠŒàŠàŠŸàŠ¬à§ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ°à§àŠ° àŠžàŠ°à§àŠ¬àŠ¶à§àŠ· àŠžàŠàŠžà§àŠàŠ°àŠ£à§ àŠ²àŠ¿àŠàŠàŠ¯à§àŠà§àŠ€ àŠ¬àŠŸàŠ°à§àŠ€àŠŸàŠà§àŠ²àŠ¿àŠ€à§ àŠªà§àŠ°àŠ€àŠ¿àŠà§àŠ°àŠ¿àŠ¯àŠŒàŠŸ àŠŠà§àŠ¯àŠŒ, àŠ¬àŠ¿àŠàŠ¿àŠšà§àŠš àŠžà§àŠ¥àŠŸàŠšà§ àŠàŠ¬àŠžà§àŠ¥àŠŸàŠš àŠšà§àŠ¯àŠŒ àŠ¯àŠŸ àŠžà§àŠšà§àŠžàŠ° àŠ¹àŠàŠ¯àŠŒàŠŸàŠ° àŠžàŠ®à§àŠàŠŸàŠ¬àŠšàŠŸ àŠàŠ® àŠ¥àŠŸàŠà§, àŠ¯à§àŠ®àŠš àŠ¡à§àŠ°àŠªàŠ¬àŠà§àŠž, Google àŠ¡à§àŠ°àŠŸàŠàŠ, àŠàŠ¬àŠ àŠàŠ¿àŠ¥àŠŸàŠ¬à¥€</p>" + }, + "censorship-4": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª -4", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª -4", + "title": "àŠàŠ®àŠ¿ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ°à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°àŠàŠ¿ àŠšàŠŸ, àŠàŠ®àŠŸàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠ àŠžà§àŠšà§àŠžàŠ° àŠàŠ°àŠŸ àŠ¹àŠ¯àŠŒà§àŠà§?", + "description": "<p class=\"mb-3\">àŠàŠªàŠšàŠ¿ àŠàŠàŠàŠ¿ àŠžà§àŠšà§àŠžàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§ àŠ¹àŠ€à§ àŠªàŠŸàŠ°à§àŠš, àŠàŠ¬àŠ àŠ€àŠŸàŠ àŠàŠªàŠšàŠŸàŠ° àŠžà§àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°à§ àŠà§àŠ·à§àŠàŠŸ àŠàŠ°àŠŸ àŠàŠàŠ¿àŠ€à¥€ àŠàŠ¿àŠà§ àŠ¬à§àŠ°àŠ¿àŠ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠ° àŠ®àŠ§à§àŠ¯à§ àŠšàŠ¿àŠ°à§àŠ®àŠ¿àŠ€ àŠ¹àŠ¯àŠŒ, àŠàŠ¬àŠ àŠàŠªàŠšàŠ¿ àŠàŠ° àŠ²àŠà§àŠàŠŸàŠ° àŠàŠàŠšà§àŠ¡à§àŠ€à§ \"àŠàŠšàŠ«àŠ¿àŠàŠŸàŠ°\" (àŠ€àŠŸàŠ°àŠªàŠ° àŠªà§àŠ°àŠ®à§àŠªàŠ àŠàŠšà§àŠžàŠ°àŠ£) àŠšàŠ¿àŠ°à§àŠ¬àŠŸàŠàŠš àŠàŠ°à§ àŠžà§àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§àŠš àŠ¯àŠŸ àŠàŠªàŠšàŠ¿ àŠ¯àŠàŠš àŠªà§àŠ°àŠ¥àŠ®àŠ¬àŠŸàŠ°à§àŠ° àŠàŠšà§àŠ¯ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠà§àŠ²à§àŠš àŠ€àŠàŠš àŠªàŠª-àŠàŠª àŠ¹àŠ¿àŠžà§àŠ¬à§ àŠàŠžà§à¥€ àŠàŠªàŠšàŠŸàŠ° àŠ¯àŠŠàŠ¿ àŠàŠšà§àŠ¯àŠŸàŠšà§àŠ¯ àŠžà§àŠ€à§àŠ° àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš àŠ¹àŠ¯àŠŒ, àŠ€àŠŸàŠ¹àŠ²à§ àŠàŠªàŠšàŠ¿ <mark><a href=\"https://bridges.torproject.or g/\">àŠàŠ®àŠŸàŠŠà§àŠ° àŠ¬à§àŠ°àŠ¿àŠà§àŠž àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠà§ </a></mark>àŠ€àŠŸàŠŠà§àŠ° àŠªà§àŠ€à§ àŠªàŠŸàŠ°à§àŠšà¥€ àŠžà§àŠ€à§ àŠžàŠ®à§àŠªàŠ°à§àŠà§ àŠàŠ°àŠ àŠ€àŠ¥à§àŠ¯à§àŠ° àŠàŠšà§àŠ¯, <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ² àŠŠà§àŠà§àŠš</a></mark>à¥€</p>" + }, + "censorship-5": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-5", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª-5", + "title": "àŠàŠ®àŠ¿ àŠàŠ° àŠžàŠàŠ¯à§àŠà§ àŠžàŠ®àŠžà§àŠ¯àŠŸ àŠ¹àŠà§àŠà§, àŠàŠ¬àŠ àŠàŠ®àŠ¿ àŠàŠ¿ àŠà§àŠ² àŠ¬à§àŠàŠ€à§ àŠªàŠŸàŠ°àŠàŠ¿ àŠšàŠŸà¥€", + "description": "<p class=\"mb-3\">àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠžàŠàŠ¯à§àŠà§àŠ° àŠžàŠ®àŠžà§àŠ¯àŠŸ àŠ¹àŠ¯àŠŒ àŠ€àŠ¬à§ àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ \"àŠàŠ° àŠ²àŠ àŠà§àŠ²àŠ¿àŠªàŠ¬à§àŠ°à§àŠ¡à§ àŠàŠªàŠ¿ àŠàŠ°à§àŠš\" àŠ¬àŠ¿àŠàŠ²à§àŠªàŠàŠ¿ àŠšàŠ¿àŠ°à§àŠ¬àŠŸàŠàŠš àŠàŠ°à§àŠšà¥€ àŠàŠ°àŠªàŠ° àŠàŠ° àŠ²àŠ àŠàŠàŠàŠ¿ àŠªàŠŸàŠ à§àŠ¯ àŠ«àŠŸàŠàŠ² àŠ¬àŠŸ àŠàŠšà§àŠ¯ àŠšàŠ¥àŠ¿àŠ€à§ àŠªà§àŠžà§àŠ àŠàŠ°à§àŠšà¥€ àŠàŠªàŠšàŠ¿ àŠàŠ àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿àŠà§àŠ²àŠ¿àŠ° àŠàŠàŠàŠ¿ àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠ¬à§àŠš (àŠàŠªàŠšàŠŸàŠ° àŠàŠ° àŠ²àŠàŠà§àŠ²àŠ¿àŠ€à§ àŠšàŠ¿àŠ®à§àŠšàŠ²àŠ¿àŠàŠ¿àŠ€ àŠ²àŠŸàŠàŠšàŠà§àŠ²àŠ¿ àŠŠà§àŠà§àŠš): <h5>àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿ # 1: àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠžàŠàŠ¯à§àŠ àŠ¬à§àŠ¯àŠ°à§àŠ¥àŠ€àŠŸ 2017-10-29 09:23:40.800 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] 127.0.0.1:9150 àŠàŠ° àŠàŠªàŠ° àŠžàŠà§àŠž àŠ²àŠ¿àŠžà§àŠšàŠŸàŠ° àŠàŠ°àŠ®à§àŠ àŠàŠ°à§àŠš\n2017-10-29 09: 23: 47.900 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] à Š¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 5%: àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠ¹àŠà§àŠà§\n 2017-10-29 09: 23: 47.900 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª àŠàŠ°àŠŸ 10%: àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠžàŠŸàŠ¥à§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠàŠ¿àŠ àŠžàŠ®àŠŸàŠªà§àŠ€ àŠàŠ°àŠŸ \n2017- 10-29 09: 24: 08.900 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠà§àŠ²àŠŸàŠ¯àŠŒà§àŠšà§àŠ: xx..xxx..xxx.xx: xxxxx (\"àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠžàŠàŠž àŠžàŠŸàŠ°à§àŠàŠŸàŠ° àŠ¬à§àŠ¯àŠ°à§àŠ¥àŠ€àŠŸ\") àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠàŠ°àŠ€à§ àŠàŠà§àŠ·àŠ®à¥€ 2017-10-29 09: 24: 08.900 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠ¡ ] àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠà§àŠ²àŠŸàŠ¯àŠŒà§àŠšà§àŠ: xx..xxx..xxx.xx: XXXxx àŠàŠ°(\"àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ SOCKS àŠžàŠŸàŠ°à§àŠàŠŸàŠ° àŠ¬à§àŠ¯àŠ°à§àŠ¥àŠ€àŠŸ\")àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠàŠ°àŠ€à§ àŠàŠà§àŠ·àŠ®à¥€\n2017-10-29 09: 24: 08.900 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠªà§àŠ°àŠà §àŠžàŠ¿ àŠà§àŠ²àŠŸàŠ¯àŠŒà§àŠšà§àŠ: xxx..xxx.xx: xxxxx (\"àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ SOCKS àŠžàŠŸàŠ°à§àŠàŠŸàŠ° àŠ¬à§àŠ¯àŠ°à§àŠ¥àŠ€àŠŸ\")<code><pre><p class=\"mb-3\"><p class=\"mb-3\">àŠàŠ° àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠàŠ°àŠ€à§ àŠàŠà§àŠ·àŠ®à¥€ àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° ââàŠ²àŠà§ àŠàŠ°àŠàŠ® àŠ²àŠŸàŠàŠš àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠš àŠ€àŠ¬à§ àŠàŠ° àŠ®àŠŸàŠšà§ àŠ¹àŠ² àŠàŠªàŠšàŠ¿ àŠàŠàŠàŠ¿ SOCKS àŠªà§àŠ°àŠà§àŠžàŠ¿àŠ€à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ°à§àŠ¥à¥€ àŠàŠªàŠšàŠŸàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠ àŠžà§àŠàŠàŠªà§àŠ° àŠàŠšà§àŠ¯ àŠàŠàŠàŠ¿ àŠžàŠà§àŠž àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš àŠ¹àŠ²à§, àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠšàŠ¿àŠ¶à§àŠàŠ¿àŠ€ àŠàŠ°à§àŠš àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠ¬àŠ¿àŠ¶àŠŠàŠà§àŠ²àŠ¿ àŠžàŠ àŠ¿àŠàŠàŠŸàŠ¬à§ àŠ²àŠ¿àŠà§àŠà§àŠšà¥€ àŠ¯àŠŠàŠ¿ àŠàŠàŠàŠ¿ àŠžàŠà§àŠž àŠªà§àŠ°àŠà§àŠžàŠ¿àŠ° àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš àŠšàŠŸ àŠ¹àŠ¯àŠŒ , àŠàŠ¥àŠ¬àŠŸ àŠ àŠªàŠšàŠ¿ àŠšàŠ¿àŠ¶à§àŠàŠ¿àŠ€ àŠšàŠš, àŠ€àŠ¬à§ àŠžàŠà§àŠž àŠªà§àŠ°àŠà§àŠžàŠ¿ àŠàŠŸàŠ¡àŠŒàŠŸ àŠàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§ àŠžàŠàŠ¯à§àŠà§àŠ° àŠà§àŠ·à§àŠàŠŸ àŠàŠ°à§àŠšà¥€ <p><h5>àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿ # 2: àŠàŠŸàŠ°à§àŠ¡ àŠ°àŠ¿àŠ²à§ àŠªà§àŠàŠàŠ€à§ àŠªàŠŸàŠ°à§ àŠšàŠŸ</h5><p class=\"mb-3\"><pre><code> 11/1/2011 21:11:43 PM .500 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] 127.0.0.1:9150 àŠàŠ° àŠàŠªàŠ° àŠžàŠà§àŠž àŠ²àŠ¿àŠžà§àŠšàŠŸàŠ° àŠàŠ°àŠ®à§àŠ àŠàŠ°à§àŠš\n11/1/2017 21:11:44 PM.300 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 80%: àŠàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠ¹àŠà§àŠà§ 11/1/2011 21:11: 44 PM.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠàŠ®àŠŸàŠŠà§àŠ° àŠªàŠ¥à§àŠ° àŠ¹àŠª 0 àŠàŠ° àŠàŠšà§àŠ¯ àŠšà§àŠ¡ àŠà§àŠàŠà§ àŠªàŠŸàŠàŠ¯àŠŒàŠŸ àŠ¬à§àŠ¯àŠ°à§àŠ¥ àŠ¹àŠ¯àŠŒà§àŠà§à¥€ àŠàŠ àŠžàŠŸàŠ°à§àŠàŠ¿àŠàŠàŠ¿ àŠàŠŸàŠ°àŠ¿àŠà¥€\n11/1/2017 21:11:44 PM.500 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 85%: àŠªà§àŠ°àŠ¥àŠ® àŠ¹àŠª àŠšàŠ¿àŠ¯àŠŒà§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠžàŠ®à§àŠªàŠšà§àŠš àŠ¹àŠ¯àŠŒà§àŠà§\n11/1/2017 21:11:45 PM300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠªàŠ¥à§àŠ° àŠ¹àŠª 0 àŠàŠ° àŠàŠšà§àŠ¯ àŠšà§àŠ¡ àŠà§àŠàŠà§ àŠªàŠŸàŠàŠ¯àŠŒàŠŸ àŠ¬à§àŠ¯àŠ°à§àŠ¥ àŠ¹àŠ¯àŠŒà§àŠà§à¥€àŠàŠ àŠžàŠŸàŠ°à§àŠàŠ¿àŠàŠàŠ¿ àŠàŠŸàŠ°àŠ¿àŠà¥€</code></pre></p><p class=\"mb-3\">àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° ââàŠ²àŠà§ àŠàŠ°àŠàŠ® àŠ²àŠŸàŠàŠš àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠš àŠ€àŠ¬à§ àŠàŠàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° àŠžàŠŸàŠ°à§àŠàŠ¿àŠà§àŠ° àŠªà§àŠ°àŠ¥àŠ® àŠšà§àŠ¡à§àŠ° àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ°à§àŠ¥à¥€ àŠàŠ° àŠ®àŠŸàŠšà§ àŠ¹àŠ² àŠ¯à§ àŠàŠªàŠšàŠ¿ àŠžà§àŠšà§àŠžàŠ° àŠàŠ°àŠŸ àŠàŠàŠàŠ¿ àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§àŠ° àŠàŠªàŠ° àŠàŠà§àŠšà¥€ àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠžà§àŠ€à§àŠà§àŠ²àŠ¿àŠ° àŠžàŠŸàŠ¥à§ àŠžàŠàŠ¯à§àŠ àŠžà§àŠ¥àŠŸàŠªàŠš àŠàŠ°àŠŸàŠ° àŠà§àŠ·à§àŠàŠŸ àŠàŠ°à§àŠš , àŠàŠ¬àŠ àŠàŠàŠ¿ àŠžàŠ®àŠžà§àŠ¯àŠŸàŠ° àŠžàŠ®àŠŸàŠ§àŠŸàŠš àŠàŠ°àŠŸ àŠàŠàŠ¿àŠ€à¥€</p><h5> àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿ # 3: TLS àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠžàŠ®à§àŠªà§àŠ°à§àŠ£ àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ°à§àŠ¥</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 10%: àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠžàŠŸàŠ¥à§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠžàŠ®àŠŸàŠªà§àŠ€ à¥€(àŠžàŠ®à§àŠªàŠšà§àŠš àŠ¹àŠ¯àŠŒà§ àŠà§àŠà§; àŠžàŠ®à§àŠªàŠšà§àŠš àŠ¹àŠ¯àŠŒà§ àŠà§àŠà§ ; àŠàŠ£àŠšàŠŸ 10; àŠžà§àŠªàŠŸàŠ°àŠ¿àŠ¶ àŠžàŠ€àŠ°à§àŠàŠ€àŠŸ; àŠ¹à§àŠžà§àŠ [àŠ¹à§àŠžà§àŠ] xxx.xxx.xxx.xx: xxx-àŠ)\n13-11 -17 19: 53: 49.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠžàŠ®àŠžà§àŠ¯àŠŸ àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠªàŠ¿àŠà¥€ 10% àŠ àŠàŠàŠà§ àŠàŠà§: àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠžàŠŸàŠ¥à§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠ¶à§àŠ· àŠ¹àŠà§àŠà§à¥€\n13-11-17 19: 53: 49.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] 10 àŠžàŠàŠ¯à§àŠ àŠ¬à§àŠ¯àŠ°à§àŠ¥ àŠ¹àŠ¯àŠŒà§àŠà§: 13-11- 17 19: 53: 49.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] 9 àŠàŠ¿ àŠžàŠàŠ¯à§àŠà§àŠ° àŠ®à§àŠ€à§àŠ¯à§ àŠàŠà§ àŠžà§àŠà§àŠ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠžà§àŠàŠ¿àŠ-àŠ (TLS) àŠàŠžàŠàŠžàŠàŠ² àŠžà§àŠà§àŠ SSLv2 / v3 àŠ¹à§àŠ¯àŠŸàŠ²à§ A àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠªàŠ¡àŠŒà§àŠš \n13-11-17 19: 53: 49.300 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠžà§àŠà§àŠ àŠžàŠàŠ¯à§àŠà§ 1 àŠàŠ¿ àŠžàŠàŠ¯à§àŠà§àŠ° àŠ®à§àŠ€à§àŠ¯à§ () àŠàŠžàŠàŠžàŠàŠ² àŠžà§àŠà§àŠ (àŠà§àŠš SSL àŠàŠ¬àŠà§àŠà§àŠ àŠšà§) </code></pre></p><p class=\"mb-3\">\nàŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° àŠ²àŠà§ àŠàŠ°àŠàŠ® àŠ²àŠŸàŠàŠš àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠš, àŠ€àŠŸàŠ° àŠ®àŠŸàŠšà§ àŠàŠ° àŠ¡àŠ¿àŠ°à§àŠà§àŠàŠ°à§ àŠàŠ°à§àŠ€à§àŠªàŠà§àŠ·à§àŠ° àŠžàŠà§àŠà§ TLS àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠžàŠ®à§àŠªàŠšà§àŠš àŠàŠ°àŠ€à§ àŠ¬à§àŠ¯àŠ°à§àŠ¥ à¥€ àŠ¬à§àŠ°àŠ¿àŠàŠà§ àŠ²àŠ¿ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°à§ àŠžàŠ®à§àŠàŠ¬àŠ€ àŠàŠàŠ¿ àŠ àŠ¿àŠ àŠ¹àŠ¬à§à¥€ </p><h5>àŠžàŠŸàŠ§àŠŸàŠ°àŠ£ àŠ²àŠ àŠ€à§àŠ°à§àŠàŠ¿ # 4 : àŠà§àŠ²àŠ àŠžà§àŠà§</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] 127.0.0.1:9150 àŠàŠ° àŠàŠªàŠ° àŠžàŠà§àŠž àŠ²àŠ¿àŠžà§àŠšàŠŸàŠ° àŠàŠ°àŠ®à§àŠ àŠàŠ°à§àŠš\n19.11.2017 00:04:48.000 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 5%: àŠ¡àŠŸàŠàŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§ àŠžàŠàŠ¯à§àŠà§àŠ€ àŠ¹àŠà§àŠà§\n19.11.2017 00:04:48.200 [àŠ¬àŠ¿àŠà§àŠàŠªà§àŠ€àŠ¿] àŠ¬à§àŠàŠžà§àŠà§àŠ°à§àŠ¯àŠŸàŠª 10%: àŠ¡àŠŸàŠàŠ°à§àŠà§àŠàŠ°àŠ¿ àŠžàŠŸàŠ°à§àŠàŠŸàŠ°à§àŠ° àŠžàŠŸàŠ¥à§ àŠ¹à§àŠ¯àŠŸàŠšà§àŠ¡àŠ¶à§àŠ àŠ¶à§àŠ· àŠ¹àŠà§àŠà§\n19.11.2017 00:04:48.800 [àŠàŠ¯àŠŒàŠŸàŠ°à§àŠš] àŠžà§àŠàŠ¿àŠàŠ¡ àŠžàŠ®àŠ¯àŠŒà§àŠ° àŠžàŠŸàŠ¥à§ àŠà§àŠ¹à§àŠ€ NETINFO àŠžà§àŠ² (OR: xxx.xx.x.xx.xxxx: àŠ¹àŠŸàŠ€à§àŠ°):\nàŠ®àŠšà§ àŠ¹àŠà§àŠà§ àŠàŠ®àŠŸàŠŠà§àŠ° àŠàŠ¡àŠŒàŠ¿àŠàŠŸ 1 àŠŠàŠ¿àŠš, 0 àŠàŠšà§àŠàŠŸ, 1 àŠ®àŠ¿àŠšàŠ¿àŠ àŠ¬àŠŸ àŠªàŠ¿àŠàŠšà§àŠ° àŠŠàŠ¿àŠà§ àŠàŠ²à§ àŠà§àŠà§ àŠ¬àŠŸ àŠ€àŠŸàŠŠà§àŠ°àŠàŠ¿ àŠàŠàŠ¿àŠ¯àŠŒà§ àŠàŠà§à¥€\nàŠàŠ° àŠàŠŸàŠ àŠàŠ°àŠŸàŠ° àŠàŠšà§àŠ¯ àŠàŠàŠàŠ¿ àŠžàŠ àŠ¿àŠ àŠàŠ¡àŠŒàŠ¿ àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš: àŠŠàŠ¯àŠŒàŠŸ àŠàŠ°à§ àŠàŠªàŠšàŠŸàŠ° àŠžàŠ®àŠ¯àŠŒ, àŠžàŠ®àŠ¯àŠŒàŠà§àŠš àŠàŠ¬àŠ àŠ€àŠŸàŠ°àŠ¿àŠ àŠžà§àŠàŠ¿àŠàŠž àŠà§àŠ àŠàŠ°à§àŠšà¥€ </code></pre></p><p class=\"mb-3\">àŠ¯àŠŠàŠ¿ àŠàŠªàŠšàŠ¿ àŠàŠªàŠšàŠŸàŠ° àŠàŠ° ââàŠ²àŠà§ àŠàŠ°àŠàŠ® àŠ²àŠŸàŠàŠš àŠŠà§àŠàŠ€à§ àŠªàŠŸàŠš àŠ€àŠ¬à§ àŠàŠªàŠšàŠŸàŠ° àŠžàŠ¿àŠžà§àŠà§àŠ® àŠàŠ¡àŠŒàŠ¿àŠàŠ¿ àŠà§àŠ²à¥€ àŠàŠšà§àŠà§àŠ°àŠ¹ àŠàŠ°à§ àŠšàŠ¿àŠ¶à§àŠàŠ¿àŠ€ àŠàŠ°à§àŠš àŠ¯à§ àŠàŠªàŠšàŠŸàŠ° àŠàŠ¡àŠŒàŠ¿àŠ° àŠžàŠ àŠ¿àŠ àŠžàŠ®àŠ¯àŠŒ àŠšàŠ¿àŠ°à§àŠ§àŠŸàŠ°àŠ£ àŠàŠ°àŠŸ àŠ¹àŠ¯àŠŒà§àŠà§, àŠžàŠ àŠ¿àŠ àŠàŠŸàŠàŠ®àŠà§àŠš àŠžàŠ¹à¥€ àŠ€àŠŸàŠ°àŠªàŠ° àŠàŠ°à§àŠ àŠªà§àŠšàŠ°àŠŸàŠ¯àŠŒ àŠàŠ°àŠ®à§àŠ àŠàŠ°à§àŠšà¥€</p>" + }, + "censorship-6": { + "id": "# àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª -6", + "control": "àŠžà§àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª -6", + "title": "àŠàŠ®àŠ¿ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ°à§ àŠžàŠàŠ¯à§àŠ àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°àŠàŠ¿ àŠšàŠŸ, àŠàŠ®àŠŸàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠ àŠžà§àŠšà§àŠžàŠ° àŠàŠ°àŠŸ àŠ¹àŠ¯àŠŒà§àŠà§?", + "description": "<p class=\"mb-3\">àŠàŠªàŠšàŠ¿ àŠàŠàŠàŠ¿ àŠžà§àŠšà§àŠžàŠ° àŠšà§àŠàŠàŠ¯àŠŒàŠŸàŠ°à§àŠà§ àŠ¹àŠ€à§ àŠªàŠŸàŠ°à§àŠš, àŠàŠ¬àŠ àŠ€àŠŸàŠ àŠàŠªàŠšàŠŸàŠ° àŠžà§àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°à§ àŠà§àŠ·à§àŠàŠŸ àŠàŠ°àŠŸ àŠàŠàŠ¿àŠ€à¥€ àŠàŠ¿àŠà§ àŠ¬à§àŠ°àŠ¿àŠ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠàŠ° àŠ®àŠ§à§àŠ¯à§ àŠšàŠ¿àŠ°à§àŠ®àŠ¿àŠ€ àŠ¹àŠ¯àŠŒ, àŠàŠ¬àŠ àŠàŠªàŠšàŠ¿ àŠàŠ° àŠ²àŠà§àŠàŠŸàŠ° àŠàŠàŠšà§àŠ¡à§àŠ€à§ \"àŠàŠšàŠ«àŠ¿àŠàŠŸàŠ°\" (àŠ€àŠŸàŠ°àŠªàŠ° àŠªà§àŠ°àŠ®à§àŠªàŠ àŠàŠšà§àŠžàŠ°àŠ£) àŠšàŠ¿àŠ°à§àŠ¬àŠŸàŠàŠš àŠàŠ°à§ àŠžà§àŠ€à§ àŠ¬à§àŠ¯àŠ¬àŠ¹àŠŸàŠ° àŠàŠ°àŠ€à§ àŠªàŠŸàŠ°à§àŠš àŠ¯àŠŸ àŠàŠªàŠšàŠ¿ àŠ¯àŠàŠš àŠªà§àŠ°àŠ¥àŠ®àŠ¬àŠŸàŠ°à§àŠ° àŠàŠšà§àŠ¯ àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠà§àŠ²à§àŠš àŠ€àŠàŠš àŠªàŠª-àŠàŠª àŠ¹àŠ¿àŠžà§àŠ¬à§ àŠàŠžà§à¥€ àŠàŠªàŠšàŠŸàŠ° àŠ¯àŠŠàŠ¿ àŠàŠšà§àŠ¯àŠŸàŠšà§àŠ¯ àŠžà§àŠ€à§àŠ° àŠªà§àŠ°àŠ¯àŠŒà§àŠàŠš àŠ¹àŠ¯àŠŒ, àŠ€àŠŸàŠ¹àŠ²à§ àŠàŠªàŠšàŠ¿ àŠàŠ®àŠŸàŠŠà§àŠ° <mark><a href=\"https://br idges.torproject.org/\">àŠ¬à§àŠ°àŠ¿àŠà§àŠž àŠàŠ¯àŠŒà§àŠ¬àŠžàŠŸàŠàŠà§ </a></mark>àŠ€àŠŸàŠŠà§àŠ° àŠªà§àŠ€à§ àŠªàŠŸàŠ°à§àŠšà¥€ àŠžà§àŠ€à§ àŠžàŠ®à§àŠªàŠ°à§àŠà§ àŠàŠ°àŠ àŠ€àŠ¥à§àŠ¯à§àŠ° àŠàŠšà§àŠ¯, <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">àŠàŠ° àŠ¬à§àŠ°àŠŸàŠàŠàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ² àŠŠà§àŠà§àŠš</a></mark>à¥€Â </p>" + } + + +} diff --git a/bn_IN.json b/bn_IN.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/bn_IN.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/bo.json b/bo.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/bo.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/br.json b/br.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/br.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/brx.json b/brx.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/brx.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/bs.json b/bs.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/bs.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ca.json b/ca.json new file mode 100644 index 000000000..d9e7e21c5 --- /dev/null +++ b/ca.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "El nostre lloc Web l'han censurat. Pot el Tor ajudar als usuaris a accedir al nostre web?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "El meu lloc web favorit estÃ blocat a travÃ©s del Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Com puc baixar el Tor si torproject.org estÃ blocat?", + "description": "<p class=\"mb-3\">Si no podeu baixar el Tor a travÃ©s del nostre <mark><a href=\"https://www.torproject.org\">lloc web</a></mark>, podeu obtindre'n una copia a travÃ©s del GetTor. El GetTor Ã©s un servei que respon automÃ ticament als missatges amb enllaÃ§os a la Ãºltima versiÃ³ del Tor Browser, hostatjada en una gran varietat d'ubicacions que segurament no estiguin blocades, com ara Dropbox, Google Drive i Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "No puc connectar al Tor. EstÃ la meva xarxa blocada?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Tinc problemes per connectar amb el Tor i desconec el motiu.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "No puc connectar al Tor. EstÃ la meva xarxa blocada?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ceb.json b/ceb.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ceb.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/cs.json b/cs.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/cs.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/csb.json b/csb.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/csb.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/cv.json b/cv.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/cv.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/cy.json b/cy.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/cy.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/da.json b/da.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/da.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/de.json b/de.json new file mode 100644 index 000000000..a188d9d51 --- /dev/null +++ b/de.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Unsere Website wird blockiert. Kann Tor Browser den Benutzern helfen, die Website trotzdem zu erreichen?", + "description": "<p class=\"mb-3\">Tor Browser kann dabei helfen Menschen Zugang zu deiner Webseite an Orten zu verschaffen, wo diese blockiert wird. In den meisten FÃ€llen genÃŒgt es <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> herunterzuladen und mit ihm zur blockierten Seite zu navigieren um Zugang zu erhalten. FÃŒr Orte mit aufwÃ€ndigen ZensurmaÃnahmen verfÃŒgen wir ÃŒber einen Satz an Zensurumgehungsoptionen, einschlieÃlich <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">austauschbarer Ãbertragungsarten</a></mark>. FÃŒr weitere Informationen dazu Ã¶ffne die <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser-Benutzeranleitung</a></mark> im Abschnitt <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">Zensur</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Meine Lieblingswebsite blockiert die Verbindung ÃŒber Tor.", + "description": "<p class=\"mb-3\">Schade, dass Sie die gewÃŒnschte Internetseite nicht besuchen kÃ¶nnen! Manchmal blockieren Webseiten Tor-Nutzer weil sie den Unterschied zwischen regulÃ€ren Tor-Nutzern und automatisierten Besuchern nicht erkennen kÃ¶nnen. Den meisten Erfolg hatten wir indem wir die Webseitenbetreiber direkt kontaktieren um die Blockade aufzuheben. Manchmal hilft dies:<br />\"Hallo! Ich habe versucht Ihre Webseite xyz.com mit dem Tor Browser zu besuchen und habe festgestellt, dass Sie Tor-Nutzern nicht erlauben Ihre Webseite zu besuchen. I bitte Sie diese Entscheidung zu ÃŒberdenken; Tor wird von Menschen auf der ganzen Welt genutzt um deren PrivatsphÃ€re zu beschÃŒtzen und Zensur zu bekÃ€mpfen. Indem Sie Tor-Nutzer blockieren, blockieren Sie auch Nutzer in repressiven Staaten, die ein freies Internet nutzen wollen, Journalisten und Wissenschaftler die sich vor einer Erkennung schÃŒtzen wollen, Whistleblowers, Aktivisten, und gewÃ¶hnliche Menschen die invasives Tra cking durch Dritte nicht akzeptieren. Bitte beziehen Sie Stellung fÃŒr digitale BÃŒrgerrechte und Internetfreiheit, und erlauben Sie Tor-Nutzern den Zugriff auf xyz.com. Vielen Dank\"<br />Im Falle von Banken und anderen sensitiven Webseiten sind auch ortsbasierte Blockaden ÃŒblich (wenn eine Bank weiÃ, dass Sie ÃŒblicherweise von einem bestimmen Land aus zugreifen, und plÃ¶tzlich von einem Exit-Server auf der anderen Seite der Welt zugreifen, kÃ¶nnte Ihre Konto (zeitweilig) gesperrt werden). Wenn Sie einen Onion-Dienst nicht erreichen kÃ¶nnen, sehen Sie hier nach: <a href=\"http://127.0.0.1:5000/#onionservices-3\">Ich kann X.onion nicht erreichen!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Wie kann ich Tor herunterladen, wenn torproject.org blockiert ist?", + "description": "<p class=\"mb-3\">Wenn du Tor ÃŒber unsere <mark><a href=\"https://www.torproject.org\">Website</a></mark> nicht herunterladen kannst, ist es mÃ¶glich sich einen alternativen Download-Link von Tor ÃŒber GetTor zusenden zu lassen. GetTor ist ein Dienst der automatisch auf Nachrichten mit Links zur aktuellsten Version des Tor Browsers antwortet, die an verschiedenen Orten wie Dropbox, Google Drive und GitHub gehostet werden.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "Ich kann mich nicht mit Tor Browser verbinden, ist mein Netzwerk zensiert?", + "description": "<p class=\"mb-3\">Du befindest dich mÃ¶glicherweise in einem zensierten Netzwerk und solltes daher versuchen BrÃŒcken zu verwenden. Einige BrÃŒcken sind in Tor Browser eingebaut und du kannst sie im Tor Browser-Startfenster, das erscheint, wenn du Tor Browser das erste Mal startest, ÃŒber \"Konfigurieren\" (und die folgende Dialoge) auswÃ€hlen. Wenn du andere BrÃŒcken benÃ¶tigst, kannst du diese auf unserer <mark><a href=\"https://bridges.torproject.org/\">BrÃŒcken-Website</a></mark> erhalten. FÃŒr weitere Informationen ÃŒber BrÃŒcken, lies den Abschnitt in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser-Anleitung</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Ich habe Probleme mich mit Tor zu verbinden und kann die Ursache nicht finden.", + "description": "<p class=\"mb-3\">Wenn du Verbindungsprobleme hast, wÃ€hle bitte die Option \"Tor-Protokoll in die Zwischenablage kopieren\" aus. FÃŒge dann das Tor-Protokoll in eine Textdatei oder ein anderes Dokument ein. Du solltest nun einen der folgenden verbreiteten FehlereintrÃ€ge sehen (suche nach foldenden Zeilen in deinem Tor-Protokoll):</p><h5>Ãblicher Fehlereintrag #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "Ich kann mich nicht mit Tor Browser verbinden, ist mein Netzwerk zensiert?", + "description": "<p class=\"mb-3\">Du befindest dich mÃ¶glicherweise in einem zensierten Netzwerk und solltes daher versuchen BrÃŒcken zu verwenden. Einige BrÃŒcken sind in Tor Browser eingebaut und du kannst sie im Tor Browser-Startfenster, das erscheint, wenn du Tor Browser das erste Mal startest, ÃŒber \"Konfigurieren\" (und die folgende Dialoge) auswÃ€hlen. Wenn du andere BrÃŒcken benÃ¶tigst, kannst du diese auf unserer <mark><a href=\"https://bridges.torproject.org/\">BrÃŒcken-Website</a></mark> erhalten. FÃŒr weitere Informationen ÃŒber BrÃŒcken, lies den Abschnitt in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser-Anleitung</a></mark>.</p>" + } + + +} diff --git a/dz.json b/dz.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/dz.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/el.json b/el.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/el.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/en_GB.json b/en_GB.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/en_GB.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/eo.json b/eo.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/eo.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/es.json b/es.json new file mode 100644 index 000000000..dc9ef431e --- /dev/null +++ b/es.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Nuestro sitio web estÃ¡ bloqueado por un censor. Â¿El Navegador Tor puede ayudar a los usuarios a acceder a nuestro sitio web?", + "description": "<p class=\\\"mb-3\\\">El Navegador Tor ciertamente puede ayudar a que la gente acceda a tu sitio web desde lugares donde estÃ¡ bloqueado. La mayorÃa de las veces se lograrÃ¡ el acceso simplemente descargando el Navegador Tor y luego usÃ¡ndolo para navegar hacia el sitio bloqueado. En lugares donde hay una fuerte censura, tenemos distintas opciones de elusiÃ³n disponibles, incluyendo transportes intercambiables. Para mÃ¡s informaciÃ³n, por favor lee la secciÃ³n sobre elusiÃ³n de la censura del Manual de Usuario del Navegador Tor.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Mi sitio web favorito estÃ¡ bloqueando el acceso a travÃ©s de Tor.", + "description": "<p class=\"mb-3\">Â¡Sentimos oÃr que no puede visitar el sitio web que querÃa! A veces los sitios web bloquearÃ¡n a los usuarios de Tor porque no puede diferenciar entre el usuario corriente de Tor y el trÃ¡fico automatizado. El mayor Ã©xito que hemos tenido en lograr que los sitios desbloqueen a los usuarios de Tor es hacer que los usuarios contacten con los administradores del sitio directamente. Algo como esto podrÃa funcionar:<br />\"Â¡Hola! TratÃ© de acceder a su sitio xyz.com mientras usaba el Navegador Tor, y descubrÃ que no permite que los usarios de Tor accedan a su sitio. Le insto a reconsiderar esta decisiÃ³n; Tor es usado por personas por todo el mundo para proteger su privacidad y luchar contra la censura. Al bloquear a los usuarios de Tor, probablemente estÃ¡ bloqueando a personas en paÃses represivos que quieren usar una Internet libre, periodistas e investigadores que quieren protegerse a si mismos de ser identificados, informantes, activistas, y gente ordinaria que quiere optar por evitar el rastreo invasivo de terceros. Por favor, adopte una postura fuerte en favor de la privacidad digital y la libertad en Internet, y permita a los usuarios de Tor acceder a xyz.com. Gracias.\"<br />Probablemente pueda evitar barreras idiomÃ¡ticas si lo hace en inglÃ©s:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital privacy and internet freedom, and allow Tor users access to xyz.com. Thank you.\ "<br />En el caso de bancos, y otros sitios web sensibles, tambiÃ©n es comÃºn ver bloqueos en base a la ubicaciÃ³n geogrÃ¡fica (si un banco sabe que generalmente accede a sus servicios desde un paÃs, y de repente estÃ¡ conectando desde un repetidor de salida de Tor en la otra parte del mundo, su cuenta puede ser bloqueada o suspendida). Si no puede conectar a un servicio onion, por favor, vea <a href=\"http://127.0.0.1:5000/#onionservices-3\">Â¡No puedo alcanzar X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Â¿CÃ³mo descargo Tor si torproject.org estÃ¡ bloqueada?", + "description": "<p class=\"mb-3\">Si no puedes descargar Tor a travÃ©s de nuestro â<mark><a href=\"https://www.torproject.org\">sitio web</a></mark>, puedes obtener una copia de Tor que se te entregarÃ¡ vÃa GetTor. GetTor es un servicio que responde automÃ¡ticamente a los mensajes con enlaces a la versiÃ³n mÃ¡s reciente del Navegador Tor, alojada en distintas ubicaciones, que es menos probable que estÃ©n censuradas, como Dropbox, Google Drive, y GitHub.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "No puedo conectar al Navegador Tor, Â¿estÃ¡ censurada mi red?", + "description": "<p class=\"mb-3\">PodrÃas estar en una red censurada, asÃ que deberÃas intentar usar puentes. Algunos puentes van incorporados al Navegador Tor, y puedes usar esos puentes seleccionando \"configurar\" (y luego siguiendo las instrucciones) en la ventana del Arranque de Tor que aparece cuando abres el Navegador Tor por primera vez. Si necesitas otros puentes, puedes obtenerlos en nuestro â<mark><a href=\"https://bridges.torproject.org/\">sitio web de puentes</a></mark>. Para mÃ¡s informaciÃ³n acerca de los puentes, lee el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">âmanual del Navegador Tor</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Estoy teniendo problemas conectando a Tor, y no logro averiguar quÃ© es lo que estÃ¡ mal.", + "description": "<p class=\"mb-3\"><p class=\"mb-3\">Si estÃ¡ teniendo problemas para conectar, por favor seleccione la opciÃ³n para \âcopiar registro de Tor al portapapeles\â. Luego pegue el registro de Tor en un fichero de texto u otro documento. DeberÃa ver uno de estos errores comunes de registro (busque las siguientes lÃneas en su registro de Tor):</p><h5>Error comÃºn de registro nÂº 1: Fallo de conexiÃ³n proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WA RN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si ve lÃneas como estas en su registro de Tor, significa que no estÃ¡ pudiendo conectar a un proxy SOCKS. Si se requiere un proxy SOCKS para la configuraciÃ³n de su red, entonces, por favor, asegÃºrese de que ha introducido los detalles de su proxy correctamente. Si no se requiere un proxy SOCKS o no estÃ¡ seguro, por favor, trate de conectar a la red Tor sin un proxy SOCKS.<p><h5>Error comÃºn de registro nÂº 2: No se puede conectar a los repetidores guardiÃ¡n</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/20 17 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si ve lÃneas como estas en su registro de Tor, significa que su Tor no pudo conectar al primer nodo en el circuito Tor. Esto podrÃa significar que se encuentra en una red que estÃ¡ censurada. Por favor, trate de conectar con puentes, y eso deberÃa corregir el problema.</p><h5>Error comÃºn de registro nÂº 3: No se pudo completar la negociaciÃ³n TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 1 3-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Si vÃ© lÃneas como estas en su registro de Tor, significa que Tor no pudo completar una negociaciÃ³n TLS con las autoridades de directorio. Usar puentes probablemente corregirÃ¡ esto.</p><h5>Error comÃºn de registro nÂº 4: Desfase de reloj</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Si ve lÃneas com o esta en su registro de Tor, significa que su reloj de sistema no estÃ¡ ajustado correctamente. Por favor, asegÃºrese de que su reloj estÃ¡ ajustado de forma precisa, incluyendo la zona horaria correcta. Luego reinicie Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "No puedo conectar al Navegador Tor, Â¿estÃ¡ censurada mi red?", + "description": "<p class=\"mb-3\">PodrÃa estar en una red censurada, y por tanto deberÃa intentar usar puentes. Algunos puentes estÃ¡n integrados en el Navegador Tor, y puede usarlos seleccionando \"configurar"\ (y siguiendo las instrucciones) en la ventana del Arranque de Tor que aparece cuando abre el Navegador Tor por primera vez. Si necesita otros puentes, puede obtenerlos en nuestro â<mark><a href=\"https://bridges.torproject.org/\">sitio web de puentes</a></mark>. Para mÃ¡s informaciÃ³n sobre los puentes, vea el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">Manual del Navegador âTor</a></mark>.</p>" + } + + +} diff --git a/es_AR.json b/es_AR.json new file mode 100644 index 000000000..faf7fb06b --- /dev/null +++ b/es_AR.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censura-1", + "control": "censura-1", + "title": "Nuestro sitio web esta bloqueado por un censor. Â¿Puede Tor Browser ayudar a los usuarios a acceder a nuestra web?", + "description": "<p class=\"mb-3\">Tor Browser definitivamente puede ayudar a las personas a acceder a su sitio web en lugares donde estÃ© bloqueado. La mayor parte del tiempo, alcanza con descargar <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> y usarlo para navegar el sitio web bloqueado. En lugares donde la censura es mas fuerte contamos con varias opciones disponibles para evitarla. Incluyendo <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">Pluggable Transport</a></mark>. Para mas informaciÃ³n, acudÃ a la secciÃ³n sobre <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censura </a></mark> del<mark><a href=\"https://tb-manual.torproject.org/en-US/\">Manual de usuario de Tor Browser</a></mark>." + }, + "censorship-2": { + "id": "#censura-2", + "control": "censura-2", + "title": "Mi sitio web bloquea su acceso vÃa Tor.", + "description": "<p class=\"mb-3\">Lamentamos oÃr que no puedas visitar el sitio web que querÃ©s! Aveces algunos sitios web bloquean a los usuarios de Tor pero que no pueden diferenciarlos del trafico generado automÃ¡ticamente. Tuvimos Ã©xito mayormente pidiendo a los usuarios de Tor que contacten con el administrador del sitio y le pidan que les permita navegar. Un mensaje como este puede ayudar: <br />\"Â¡Hola!, tratÃ© de acceder al sitio xyz.com usando Tor Browser y me di cuenta que no se lo permiten a usuarios de Tor. Te pido que reconsideres esta decisiÃ³n; Tor es usado por personas de toda Internet para proteger su privacidad y luchar contra la censura. Bloqueandonos, estas impidiendo que personas en paÃses represivos que quieren usar libremente Internet, periodistas e investigadores que quieren protegerse de ser descubiertos, informantes, activistas y personas ordinarias quienes optan por evitar el rastreo intrusivo de servicios de terceros. Por favor tomÃ¡ una posiciÃ³n a favor de la privacidad digital y la libertad en Internet y permitÃ a los usuarios de Tor acceder a xyz.com, Muchas gracias.\"<br /> En el caso de bancos y otros sitios web sensibles, es comÃºn ver bloqueos basados en la ubicacion geogrÃ¡fica (si un banco sabe que generalmente accedes sus servicios desde un pais particular, y de repente te conectas desde un nodo de salida desde el otro lado del mundo, tu cuenta puede ser bloqueada o sospendida). Si no te es posible conectarte a un servicio onion, por favor lee <a href=\"http://127.0.0.1:5000/#onionservices-3\">no puedo conectarme a X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censura-3", + "control": "censura-3", + "title": "Â¿Como descargo Tor si torproject.org esta bloqueado?", + "description": "<p class=\"mb-3\">Si no podes descargar Tor mediante nuestro <mark><a href=\"https://www.torproject.org\">sitio web</a></mark>, te podemos enviar una copia mediante GetTor. GetTor es un servicio que automÃ¡ticamente responde mensajes con enlaces a la ultima versiÃ³n de Tor Browser, alojadas en varios lugares que generalmente no estÃ¡n bloqueados, como Dropbox, Google Drive y Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/es_CL.json b/es_CL.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/es_CL.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/es_CO.json b/es_CO.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/es_CO.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/es_MX.json b/es_MX.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/es_MX.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/et.json b/et.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/et.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/eu.json b/eu.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/eu.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/fa.json b/fa.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/fa.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/fi.json b/fi.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/fi.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/fil.json b/fil.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/fil.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/fo.json b/fo.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/fo.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/fr.json b/fr.json new file mode 100644 index 000000000..8114facd9 --- /dev/null +++ b/fr.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censure-1", + "control": "censure-1", + "title": "Notre site Web est bloquÃ© par un censeur. Le navigateur Tor peut-il aider les utilisateurs Ã accÃ©der Ã notre site Webâ?", + "description": "<p class=\"mb-3\">Le navigateur Tor peut certainement aider les utilisateurs Ã accÃ©der Ã votre site Web oÃ¹ il est bloquÃ©. La plupart du temps, il suffira de tÃ©lÃ©charger le <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">navigateur Tor</a></mark>et de lâutiliser pour naviguer vers le site bloquÃ© pour y accÃ©der. Pour les endroits soumis Ã une censure forte, de nombreuses options de contournement sont offertes, dont les â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">transports enfichables</a></mark>. Pour de plus amples renseignements, veuillez consulter la rubrique sur la <mark><a href=\"https://tb-manual.torproject.org/fr/circumvention.html\">censure</a></mark> du <mark><a href=\"https://tb-manual.torproject.org/fr/\">âguide dâutilisation du navigateur Tor</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censure-2", + "control": "censure-2", + "title": "Mon site Web prÃ©fÃ©rÃ© bloque lâaccÃšs Ã partir de Tor.", + "description": "<p class=\"mb-3\">Nous sommes dÃ©solÃ©s dâapprendre que vous ne pouvez pas visiter le site Web que vous souhaitezâ! Un site Web bloquera parfois les utilisateurs de Tor parce quâils ne peuvent pas faire la diffÃ©rence entre lâutilisateur de Tor moyen et le trafic automatisÃ©. Les meilleurs rÃ©sultats pour dÃ©bloquer lâaccÃšs des utilisateurs de Tor Ã un site donnÃ© ont Ã©tÃ© obtenus en demandant aux utilisateurs de contacter directement les administrateurs dudit site. Ce qui suit pourrait suffireÂ :<br />Â«Â Bonjourâ! Jâai essayÃ© dâaccÃ©der Ã votre site xyz.com tout en utilisant le navigateur Tor et jâai dÃ©couvert que vous ne permettez pas aux utilisateurs de Tor dây accÃ©der. Je vous demande instamment de reconsidÃ©rer votre dÃ©cisionâ; Tor est utilisÃ© partout dans le monde par des personnes souhaitant protÃ©ger leurs renseignements personnels tout en combattant la censure. En bloquant les utilisateurs de Tor, vous bloquez vraisemblableme nt des personnes se trouvant dans des pays oÃ¹ rÃšgne la rÃ©pression et qui souhaitent utiliser un Internet libre, des journalistes et des chercheurs qui ne veulent pas Ãªtre dÃ©couverts, des lanceurs dâalerte, des activistes et des personnes ordinaires qui ne veulent pas Ãªtre suivies Ã la trace par des tiers invasifs. Veuillez adopter une position ferme privilÃ©giant la confidentialitÃ© numÃ©rique et la libertÃ© sur Internet, et permettre aussi aux utilisateurs de Tor dâaccÃ©der Ã xyz.com. Merci.<br />Voici le mÃªme message en anglaisÂ : <br />âHi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from di scovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital privacy and internet freedom, and allow Tor users access to xyz.com. Thank you.â<br />Dans le cas de banques ou autres sites Web dÃ©licats, il est aussi habituel de constater un blocage dâaprÃšs la position gÃ©ographique (si une banque sait que vous accÃ©dez habituellement Ã ses services Ã partir dâun pays et que vous vous connectez soudainement Ã partir dâun relais de sortie situÃ© de lâautre cÃŽtÃ© de la planÃšte, votre compte pourrait Ãªtre verrouillÃ© ou suspendu). Si vous ne pouvez pas vous connecter Ã un service oignon, veuillez consulter <a href=âhttp://127.0.0.1:5000/#onionservices-3â>Je ne peux pas accÃ©der Ã X.onionâ!</a></p>" + }, + "censorship-3": { + "id": "#censure-3", + "control": "censure-3", + "title": "Comment puis-je tÃ©lÃ©charger Tor si torproject.org est bloquÃ©â?", + "description": "<p class=\"mb-3\">Si vous ne pouvez pas tÃ©lÃ©charger Tor Ã partir de notre <mark><a href=\"https://www.torproject.org\">site Web</a></mark>, une exemplaire de Tor peut vous Ãªtre livrÃ© par GetTor. GetTor est un service qui rÃ©pond automatiquement aux messages en incluant des liens vers la derniÃšre version du navigateur Tor, hÃ©bergÃ©e en divers endroits tels que Dropbox, Google Disque et GitHub.</p>" + }, + "censorship-4": { + "id": "#censure-4", + "control": "censure-4", + "title": "Je n'arrive pas Ã me connecter au navigateur Tor, mon rÃ©seau est-il censurÃ© ?", + "description": "<p class=\"mb-3\">Il se peut que vous soyez sur un rÃ©seau censurÃ© et que vous deviez tenter dâutiliser des ponts. Des ponts sont intÃ©grÃ©s au navigateur Tor et vous pouvez utiliser ces ponts en choisissant Â«Â ConfigurerÂ Â» (puis en suivant les indications) dans la fenÃªtre du lanceur Tor qui surgit quand vous ouvrez le navigateur Tor pour la premiÃšre fois. Sâil vous faut dâautres ponts, vous pouvez en obtenir sur notre â<mark><a href=\"https://bridges.torproject.org/\">site Web BridgeDB</a></mark>. Pour de plus amples renseignements concernant les ponts, consulter le <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">âguide dâutilisation du navigateur Tor</a></mark>.</p>\n" + }, + "censorship-5": { + "id": "#censure-5", + "control": "censure-5", + "title": "JâÃ©prouve des difficultÃ©s Ã me connecter Ã Tor et je nâarrive pas Ã comprendre ce qui ne va pas.", + "description": "<p class=\"mb-3\">Si vous Ã©prouvez des difficultÃ©s Ã vous connecter, veuillez sÃ©lectionner lâoption Â«Â Copier le journal de Tor dans le presse-papiersÂ Â». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver lâune de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor)Â : </p><h5>Erreur habituelle de journal noÂ 1 : Ã©chec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter Ã un mandataire SOCKS. Si un mandataire SOCKS est nÃ©cessaire Ã la configuration de rÃ©seau, veuillez alors vous assurer dâavoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS nâest pas nÃ©cessaire ou si vous ne savez pas, veuillez tenter de vous connecter au rÃ©seau Tor sans mandataire SOCKS.<p><h5>Erreur habituelle de journal noÂ 2 : impossible dâatteindre les relais gardes</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/ 2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâarrivez pas Ã vous connecter au premier nÅud du circuit Tor. Cela pourrait signifier que vous Ãªtes sur un rÃ©seau qui est censurÃ©. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5>Erreur habituelle de journal noÂ 3 : Ã©chec dâÃ©tablissement dâune liaison TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19 :53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas rÃ©ussi Ã Ã©tablir une liaison TLS avec les autoritÃ©s d'annuaire. Lâutilisation de ponts corrigera certainement cette situation.</p><h5>Erreur habituelle de journal noÂ 4 : dÃ©calage dâhorloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or t hat theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">\nSi vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge systÃšme nâest pas juste. Veuillez vous assurer que votre horloge est rÃ©glÃ©e avec prÃ©cision, fuseau horaire inclus, puis redÃ©marrez Tor. </p>" + }, + "censorship-6": { + "id": "#censure-6", + "control": "censure-6", + "title": "Je n'arrive pas Ã me connecter au navigateur Tor, mon rÃ©seau est-il censurÃ© ?", + "description": "<p class=\"mb-3\">Il se peut que vous soyez sur un rÃ©seau censurÃ© et que vous deviez tenter dâutiliser des ponts. Des ponts sont intÃ©grÃ©s au navigateur Tor et vous pouvez utiliser ces ponts en choisissant Â«Â ConfigurerÂ Â» (puis en suivant les indications) dans la fenÃªtre du lanceur Tor qui surgit quand vous ouvrez le navigateur Tor pour la premiÃšre fois. Sâil vous faut dâautres ponts, vous pouvez en obtenir sur notre â<mark><a href=\"https://bridges.torproject.org/\">site Web BridgeDB</a></mark>. Pour de plus amples renseignements concernant les ponts, consulter le <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">âguide dâutilisation du navigateur Tor</a></mark>.</p>" + } + + +} diff --git a/fr_CA.json b/fr_CA.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/fr_CA.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/fur.json b/fur.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/fur.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/fy.json b/fy.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/fy.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ga.json b/ga.json new file mode 100644 index 000000000..4d858b9e9 --- /dev/null +++ b/ga.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Rinneadh cinsireacht ar Ã¡r suÃomh GrÃ©asÃ¡in. An fÃ©idir le hÃºsÃ¡ideoirÃ BrabhsÃ¡laÃ Tor a ÃºsÃ¡id chun teacht air?", + "description": "<p class=\"mb-3\">Cinnte is fÃ©idir le daoine BrabhsÃ¡laÃ Tor a ÃºsÃ¡id chun teacht ar do shuÃmh Ã³ Ã¡iteanna ina bhfuil cosc air. Go hiondÃºil, is leor â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">BrabhsÃ¡laÃ Tor</a></mark> a ÃoslÃ³dÃ¡il agus a ÃºsÃ¡id agus beidh daoine in ann do shuÃomh a shroicheadh. Chomh maith leis sin, cuirimid uirlisÃ eile ar fÃ¡il a chabhraÃonn le daoine in Ã¡iteanna faoi chinsireacht throm an cÃ³ras cinsireachta a sheachaint, mar shampla â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">cÃ³rais iompair ionphlugÃ¡ilte</a></mark>. FÃ©ach ar <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âLÃ¡mhleabhar BhrabhsÃ¡laÃ Tor</a></mark>, go hÃ¡irithe an t-alt maidir <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">cinsireacht</a></mark> chun tuilleadh eolais a fhÃ¡il.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Cuireann an suÃomh is ansa liom cosc ar lÃonra Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Conas is fÃ©idir Tor a ÃoslÃ³dÃ¡il mÃ¡ tÃ¡ cosc ar torproject.org?", + "description": "<p class=\"mb-3\">Mura bhfuil tÃº in ann Tor a ÃoslÃ³dÃ¡il Ã³nÃ¡r â<mark><a href=\"https://www.torproject.org\">suÃomh GrÃ©asÃ¡in</a></mark>, is fÃ©idir leat Tor a fhÃ¡il trÃ sheirbhÃs GetTor. Is Ã©ard atÃ¡ ann nÃ¡ seirbhÃs a thugann freagra ar theachtaireachtaÃ le nascanna leis an leagan is dÃ©anaÃ de BhrabhsÃ¡laÃ Tor, Ã³stÃ¡ilte in Ã¡iteanna nach ndÃ©antar cinsireacht orthu rÃ³mhinic, mar shampla Dropbox, Google Drive, nÃ³ Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "NÃ fÃ©idir liom ceangal le BrabhsÃ¡laÃ Tor. An bhfuil mo lÃonra faoi chinsireacht?", + "description": "<p class=\"mb-3\">B'fhÃ©idir go bhfuil do lÃonra faoi chinsireacht. Mar sin, ba chÃ³ir duit triail a bhaint as droichead. TÃ¡ roinnt droichead ionsuite i mBrabhsÃ¡laÃ Tor, agus is fÃ©idir leat iad siÃºd a ÃºsÃ¡id trÃ \"Cumraigh\" a roghnÃº (agus na treoracha a leanÃºint) sa bhfuinneog Tor Launcher a osclaÃonn an chÃ©ad uair a ÃºsÃ¡ideann tÃº BrabhsÃ¡laÃ Tor. MÃ¡ theastaÃonn droichid eile uait, tÃ¡ siad ar fÃ¡il Ã³nÃ¡r suÃomh â<mark><a href=\"https://bridges.torproject.org/\">Droichid</a></mark>. FÃ©ach ar <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âlÃ¡mhleabhar BhrabhsÃ¡laÃ Tor</a></mark> le tuilleadh eolais a fhÃ¡il.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "NÃ fÃ©idir liom ceangal le lÃonra Tor, agus nÃ thuigim cad Ã© an fhadhb.", + "description": "<p class=\"mb-3\">MÃ¡ tÃ¡ fadhb agat ag ceangal le lÃonra Tor, ÃºsÃ¡id an rogha âcÃ³ipeÃ¡il logchomhad Tor go dtÃ an ghearrthaisce.â Ansin, greamaigh an logchomhad i dtÃ©acschomhad nÃ³ cÃ¡ipÃ©is eile. Is dÃ³cha go bhfeicfidh tÃº ceann de na hearrÃ¡idÃ coitianta seo (cuardaigh na lÃnte seo a leanas sa logchomhad):</p><h5>EarrÃ¡id choitianta #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to co nnect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn siad gur theip ort ceangal a bhunÃº le seachfhreastalaÃ SOCKS. MÃ¡ theastaÃonn seachfhreastalaÃ SOCKS uait ar do lÃonra, deimhnigh gur chuir tÃº mionsonraÃ an fhreastalaÃ isteach go ceart. Mura dteastaÃonn seachfhreastalaÃ SOCKS uair, nÃ³ mura bhfuil tÃº cinnte, dÃ©an iarracht ceangal a bhunÃº le lÃonra Tor gan seachfhreastalaÃ SOCKS.<p><h5>EarrÃ¡id choitianta #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] F ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ort ceangal a bhunÃº leis an chÃ©ad nÃ³d sa gciorcad Tor. Uaireanta, ciallaÃonn seo go bhfuil do lÃonra faoi chinsireacht. Bain triail as ceangal trÃ dhroichead; is dÃ³cha go rÃ©iteoidh sin an fhadhb.</p><h5>EarrÃ¡id choitianta #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 co nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ar Tor croitheadh lÃ¡imhe TLS leis na hÃºdarÃ¡is a chur i gcrÃch. Is dÃ³cha go rÃ©iteoidh droichead an fhadhb seo.</p><h5>EarrÃ¡id choitianta #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, c iallaÃonn sÃ© go bhfuil an clog i do rÃomhaire mÃcheart. Ba chÃ³ir duit socruithe an chloig a dheimhniÃº, an t-am, dÃ¡ta, agus crios ama san Ã¡ireamh. Ansin, atosaigh Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "NÃ fÃ©idir liom ceangal le BrabhsÃ¡laÃ Tor. An bhfuil mo lÃonra faoi chinsireacht?", + "description": "<p class=\"mb-3\">B'fhÃ©idir go bhfuil do lÃonra faoi chinsireacht. Mar sin, ba chÃ³ir duit triail a bhaint as droichead. TÃ¡ roinnt droichead ionsuite i mBrabhsÃ¡laÃ Tor, agus is fÃ©idir leat iad siÃºd a ÃºsÃ¡id trÃ \"Cumraigh\" a roghnÃº (agus na treoracha a leanÃºint) sa bhfuinneog Tor Launcher a osclaÃonn an chÃ©ad uair a ÃºsÃ¡ideann tÃº BrabhsÃ¡laÃ Tor. MÃ¡ theastaÃonn droichid eile uait, tÃ¡ siad ar fÃ¡il Ã³nÃ¡r suÃomh â<mark><a href=\"https://bridges.torproject.org/\">Droichid</a></mark>. FÃ©ach ar <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âlÃ¡mhleabhar BhrabhsÃ¡laÃ Tor</a></mark> le tuilleadh eolais a fhÃ¡il.</p>" + } + + +} diff --git a/gd.json b/gd.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/gd.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/gl.json b/gl.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/gl.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/gu.json b/gu.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/gu.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/gu_IN.json b/gu_IN.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/gu_IN.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/gun.json b/gun.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/gun.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ha.json b/ha.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ha.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/he.json b/he.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/he.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/hi.json b/hi.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/hi.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/hr.json b/hr.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/hr.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/hr_HR.json b/hr_HR.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/hr_HR.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ht.json b/ht.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ht.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/hu.json b/hu.json new file mode 100644 index 000000000..2baffb8b4 --- /dev/null +++ b/hu.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "A weboldalunkat blokkolta egy cenzor. Hogyan segÃti a Tor BÃ¶ngÃ©szÅ a felhasznÃ¡lÃ³kat az oldalunk elÃ©rÃ©sÃ©ben?", + "description": "<p class=\"mb-3\">A Tor BÃ¶ngÃ©szÅ segÃthet elÃ©rni weboldalÃ¡t, olyan helyekrÅl, ahol azok blokkoltak. A legtÃ¶bb esetben elÃ©g a â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor BÃ¶ngÃ©szÅ</a></mark> letÃ¶ltÃ©se Ã©s hasznÃ¡lata a blokkolt oldal megnyitÃ¡sÃ¡ra lehetÅvÃ© teszi a hozzÃ¡fÃ©rÃ©st. Olyan helyeken, ahol a cenzorÃ¡lÃ¡s erÅs, tÃ¶bb megkerÃŒlÅ opciÃ³ elÃ©rhetÅ, beleÃ©rtve a â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">csatolhatÃ³ Ã¡tviteleket</a></mark> is. TovÃ¡bbi informÃ¡ciÃ³kÃ©rt tekintese meg a <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor BÃ¶ngÃ©szÅ FelhasznÃ¡lÃ³i kÃ©zikÃ¶nyv</a></mark> <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">cenzorÃ¡lÃ¡srÃ³l</a></mark> szÃ³lÃ³ fejezetÃ©t.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "A kedvenc oldalam blokkolja a Tor-on keresztÃŒli hozzÃ¡fÃ©rÃ©st.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/hy.json b/hy.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/hy.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ia.json b/ia.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ia.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/id.json b/id.json new file mode 100644 index 000000000..55c318a59 --- /dev/null +++ b/id.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Situs kami diblokir sensor. Apakah Tor Browser dapat membantu pengguna kami dalam mengakses situs kami?", + "description": "<p class=\"mb-3\">Tor Browser dapat membantu dalam akses situs web Anda dari tempat yang terblokir. Umumnya hanya unduh <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser </a></mark>dan gunakannya untuk membuka akses situs yang terblokir. Di tempat-tempat yang mengalami sensor berat, tersedia beberapa pilihan yang mengatasinya, termasuk <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transport </a></mark>. Untuk info lebih lanjut, silakan baca bagian <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser Manual </a></mark>di bagian <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Situs web favorit saya memblokir akses melalui Tor.", + "description": "<p class=\"mb-3\">Kami turut prihatin atas Anda tidak dapat melakukan akses ke situs web yang Anda inginkan! Kadang beberapa situs web memblokir pengguna Tor karena tidak dapat membedakan pengguna Tor biasa dan lalu-lintas otomatos. Hal terbaik yang dapat dilakukan adalah pengguna menghubungi langsung admin situsnya. Ini mungkin dapat menjadi contoh: <br />\"Halo! Saya berusaha melakukan akses terhadap situs xyz.com Anda melalui Tor Browser dan ternyata Anda tidak mengizinkan pengguna Tor untuk melakukan akses terhadap situs Anda. Saya mohon dengan sangat untuk mempertimbangkan hal ini; Tor digunakan orang-orang di seluruh dunia untuk melindungi privasi mereka dan melawan sensor. Dengan memblokir pengguna Tor, Anda akan memblokir orang-orang di negara-negara represif yang ingin menggunakan Internet secara bebas, wartawan, dan peneliti yang ingin melindungi diri sendiri dari penemuan, termasuk whistleblower, aktivis, dan orang-orang biasa yang ingin terbebas dari pel acakan menyeluruh yang dilakukan pihak lain. Mohon dukungan penuh terhadap privasi digital dan kebebasan Internet, dan izinkan pengguna Tor untuk melakukan akses ke xyz.com. Terima kasih.\"<br />Untuk situs web perbankan dan situs web lain yang sensitif, umumnya ada pemblokiran berdasarkan wilayah geografis (jika bank Anda mengetahui Anda biasanya melakukan akses terhadap jasa mereka dari suatu negara dan jika tiba-tiba Anda membuka situs web mereka dari exit relay di negara lain, akun Anda mungkin akan dikunci atau dibekukan). Jika Anda tidak dapat terhubung ke sebuah onion service, silakan lihat <a href=\"http://127.0.0.1:5000/#onionservices-3\">Saya tidak dapat menghubungi X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Bagaimana cara mengunduh Tor jika torproject.org diblokir?", + "description": "<p class=\"mb-3\">Jika Anda tidak dapat mengunduh Tor dari <mark><a href=\"https://www.torproject.org\">situs kami</a></mark>, Tor dapat dikirim kepada Anda melalui GetTor. GetTor adalah service yang yang otomatis merespon pesan berisi tautan ke versi terakhir Tor Browser, yang dihosting di lokasi beragam sehingga kemungkinan kecil disensor, seperti Dropbox, Google Drive, dan Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "Saya tidak bisa terhubung ke Tor Browser, apakah jaringan saya terkena sensor?", + "description": "<p class=\"mb-3\">Anda mungkin berada di jaringan yang terdampak sensor, sehingga Anda seharusnya menggunakan bridge yang terintegrasi di Tor Browser. Anda dapat menggunakannya dengan memilih \"configure\" (lalu setelah beberapa pemberitahuan) di jendela launcher Tor yang muncul setelah Anda menjalankan Tor Browser. Jika Anda memerlukan bridge lain, Anda dapat memperolehnya di <mark><a href=\"https://bridges.torproject.org/\">situs web bridge kami </a></mark>. Untuk info lebih lanjut tentang bridge, silakan baca <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser </a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.", + "description": "<p class=\"mb-3\">Jika Anda mendapat masalah dalam terhubung ke Jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Jaringan Tor \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Tor gagal ter sambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.< /p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "Saya tidak bisa terhubung ke Tor Browser, apakah jaringan saya terkena sensor?", + "description": "<p class=\"mb-3\">Anda mungkin berada di jaringan yang terdampak sensor, sehingga Anda seharusnya menggunakan bridge yang terintegrasi di Tor Browser. Anda dapat menggunakannya dengan memilih \"configure\" (lalu setelah beberapa pemberitahuan) di jendela launcher Tor yang muncul setelah Anda buka Tor Browser. Jika Anda memerlukan bridge lain, Anda dapat memperolehnya di <mark><a href=\"https://bridges.torproject.org/\">situs web bridge kami </a></mark>. Untuk info lebih lanjut tentang bridge, silakan baca <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser </a></mark>.</p>" + } + + +} diff --git a/is.json b/is.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/is.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/it.json b/it.json new file mode 100644 index 000000000..4858178bd --- /dev/null +++ b/it.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censura-1", + "control": "censura-1", + "title": "Il nostro sito viene censurato da qualcuno. Tor Browser puÃ² aiutare gli utenti ad accedervi?", + "description": "<p class=\"mb-3\">Il Browser Tor puÃ² sicuramente aiutare le persone ad accedere al tuo sito web in luoghi dove Ãš bloccato. La maggior parte delle volte, scaricare semplicemente il <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Browser Tor </a></mark> e usarlo per navigare sul sito bloccato permetterÃ l'accesso. In luoghi dove Ãš presente un'alta forma di censura, abbiamo un numero di opzioni per aggirarla, includendo <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">una tecnologia per prevenire l'ispezione dei dati </a></mark>. Per ulteriori informazioni, per favore vedi il <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Manuale Utente del Browser Tor</a></mark>nella sezione<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censura</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censura-2", + "control": "censura-2", + "title": "Il mio sito preferito sta bloccando l'accesso da Tor.", + "description": "<p class=\"mb-3\">Scusa di sentirlo, non puoi visitare il sito di web che volutoti! Talvolta siti di web fermerÃ² utilizzatore di Tor perche non possono dire la differenza tra utilizzatore ordinario di Tor e traffico automatico. Il migliore successo noi abbiamo avuto nel prendendo siti a sbloccare utilizzatore di Tor che direttamente contattare amministratori al utilizzatori. Qualcosa come questo puÃ² abilitare di funzione<br />\"Ciao! Ho tirato ad accedere vostro sito xyz.com mentre usando Tor Browser e scoperto che tu non permettere utilizzatore di Tor ad accedere vostro sito. Io spingo te a riconsiderare questo decisione; Tor Ã© usando da uomini sul mondo per difendere loro intimita e censura di lotta. Con bloccare utilizzatore di Tor, sei come bloccando uomini nel paesi repressivi chi vogliono ad usare un rete libero, giornalisti e ricercatori chi vogliono a difendere loro stessi da scoperta, spione, attiviste e uomini ordinari chi vogliono decidere di non parte cipare di invasivo controllo terzo. Per piacere prende atteggiamento poderoso per favore di intimata digitale e libero di rete e permette utilizzatore di Tor ad accedere xyz.com. Grazie.\"<br />In caso di bance e altro siti sensitivi, Ã© anche comune a vedere bloccando tratto geografia (se un banca sa tu generalmente accedere loro servizio da una campagna e improvvisamente sei connettendo da un relÃšÂ uscita sulla altro lato di mondo, tuo conto puÃ² chiuso o pensile). Se sei incapace di connettere a servizio di cipolla, per piacere consulta<a href=\"http://127.0.0.1:5000/#onionservices-3\">Non posso accedere X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censura-3", + "control": "censura-3", + "title": "Come posso scaricare Tor se torproject.org viene bloccato?", + "description": "<p class=\"mb-3\">Se non puoi scaricare Tor dal nostro <mark><a href=\"https://www.torproject.org\">sito</a></mark>, puoi ottenerne una copia attraverso GetTor. GetTor Ãš un servizio che risponde automaticamente a messaggi con link all'ultima versione di Tor Browser, ospitata in vari luoghi che sono difficili da censurare, come Dropbox, Google Drive e GitHub.</p>" + }, + "censorship-4": { + "id": "#censura-4", + "control": "censura-4", + "title": "Non posso connettermi a Tor Browser, la mia rete Ãš censurata?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censura-5", + "control": "censura-5", + "title": "Sto avendo problemi nella connessione a Tor e non riesco a capire quale sia la causa.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censura-6", + "control": "censura-6", + "title": "Non posso connettermi a Tor Browser, la mia rete Ãš censurata?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ja.json b/ja.json new file mode 100644 index 000000000..a8465c9e6 --- /dev/null +++ b/ja.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#æ€é²-1", + "control": "æ€é²-1", + "title": "ç§ãã¡ã®WEBãµã€ãã¯æ€é²ã«ãããããã¯ãããŸãããTorãã©ãŠã¶ãŒã¯ãŠãŒã¶ãŒã®WEBãµã€ããžã®ã¢ã¯ã»ã¹ãå©ããŠãããŸããïŒ", + "description": "<p class=\"mb-3\">ããªãã®ãµã€ãããããã¯ãããå ŽåãTorãã©ãŠã¶ãŒãäººã¯ç¢ºå®ã«ã¢ã¯ã»ã¹ã§ããããå©ãããå€§æµã®å Žåã<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Torãã©ãŠã¶ãŒ</a></mark>ãå©çšããŠãµã€ãã®ã¢ãã¬ã¹ã«ã¢ã¯ã»ã¹ããã ãã§ååã§ããããå³ããæ€é²ãããå Žåã<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">Pluggable Transport</a></mark>ãªã©æ§ããªè¿åæ¹æ³ããããŸããè©³çŽ°ã«ã€ããŠã¯ã<mark><a href=\"https://tb-manual.torproject.org/en-US/\">Torãã©ãŠã¶ãŒã®ãŠãŒã¶ãŒããã¥ã¢ã«</a></mark>ã«<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">æ€é²</a></mark>ã«é¢ããç« ãèª¿ã¹ãŠäžããã</p>" + }, + "censorship-2": { + "id": "#æ€é²-2", + "control": "æ€é²-2", + "title": "ãæ°ã«å¥ãã®WEBãµã€ããžã®ã¢ã¯ã»ã¹ãTorã«ãããããã¯ãããŸããã", + "description": "<p class=\"mb-3\">ããªãã®æããµã€ãã«ã¢ã¯ã»ã¹ã§ããªãããšã¯ç³ãèš³ãããŸããïŒãµã€ãã¯ãã°ãã°TorãŠãŒã¶ãŒããããã¯ããŸããåœŒãã¯éåžžã®TorãŠãŒã¶ãŒãšèªåãã©ãã£ãã¯ã®éããèŠåããããšãã§ããªãããã§ãããããã¯ãè§£é€ããµã€ããååŸããã®ã«ãã£ãšãé©ããææ®µã¯ãTOAãŠãŒã¶ãŒããµã€ãç®¡çèã«å¯ŸããŠçŽæ¥çã«ã³ã³ã¿ã¯ããåãããšã§ãããã®ãããªããªãã¯ãäœ¿ãããããããŸãã:<br />âããïŒç§ã¯ããªãã®ãµã€ãxyz.comã«Torãã©ãŠã¶ãŒã§ã¢ã¯ã»ã¹ããããšããã®ã ããã©ãããªãã®ãµã€ãã¯TorãŠãŒã¶ãŒãžã®ã¢ã¯ã»ã¹ãèš±å¯ããŠããªãã¿ãããªãã ããã®æ±ºå®ã¯åæ€èšããããšããå§ãããããTorã¯ãã©ã€ãã·ãŒä¿è·ãšæ€é²ãžã®å¯Ÿæã®çºã«äžçäžã®äººãã«ãã£ãŠäœ¿ãããŠãããã ãTorãŠãŒã¶ãŒããããã¯ãã ããšã¯ãèªç±ãªã€ã³ã¿ãŒããããæãæå§çãªåœã®äººãããé²åºããå®ãããã¹ããžã£ãŒããªã¹ããèª¿æ»å¡ãåéšåçºèãæŽ»åå®¶ãåã³äŸµç¥çãªãµãŒãããŒãã£ã®ãã©ããã³ã°ããéãããæ®éã®äººããããããã¯ããŠããŸããã ãã©ãããããžã¿ã«ãã©ã€ãã·ãŒãšã€ã³ã¿ãŒãããã®èªç±ãå°éããŠãTorãŠãŒã¶ãŒãxyz.comã«ã¢ã¯ã»ã¹ã§ããããã«ããŠã»ãããããããšããâ<br />éè¡ããã®ä»ã®å³å¯ãªWEBãµã€ãã®å Žåããã®å°åã®å°ççãªé®ææå ±ãèŠãŸãããïŒéè¡ãããªããæ®æ®µããåœããã¢ã¯ã»ã¹ããŠããããšãç¥ã£ãŠããã°ãããªãã®ã¢ã«ãŠã³ãã¯çªç¶ããã¯ããããäžæãããå¯èœæ§ããããŸãïŒãããããªãããªããªã³ãµãŒãã¹ã«æ¥ç¶ã§ããªãå Žåã¯ã<a href=\"http://127.0.0.1:5000/#onionservices-3\">X.onionã«ã¢ã¯ã»ã¹ã§ããŸãã</a>ãåç§ã ãŠãã ããã</p>" + }, + "censorship-3": { + "id": "#æ€é²-3", + "control": "æ€é²-3", + "title": "torproject.orgããããã¯ãããŠããå Žåãã©ã®ããã«TorãããŠã³ããŒãã§ããŸããïŒ", + "description": "<p class=\"mb-3\">ç§ãã¡ã®<mark><a href=\"https://www.torproject.org\">WEBãµã€ã</a></a>ããTorãããŠã³ããŒãã§ããªãå ŽåãGetTorã«ãã£ãŠTorãããŠã³ããŒãã§ããŸããGetTor ã¯ææ°ããŒãžã§ã³ã® Torãã©ãŠã¶ãŒ ãžã®ãªã³ã¯ãã¡ãã»ãŒãžã§èªåçã«è¿ä¿¡ãããµãŒãã¹ã§ãããã¡ã€ã«ã¯ DropboxïŒGoogle Drive ããã³ GitHub ãšãã£ãããŸããŸãªæ€é²ãããå¯èœæ§ãäœãå Žæã§ãã¹ããããŠããŸãã </p>" + }, + "censorship-4": { + "id": "#æ€é²-4", + "control": "æ€é²-4", + "title": "Torãã©ãŠã¶ãŒã«æ¥ç¶ã§ããŸãããç§ã®ãããã¯ãŒã¯ã¯æ€é²ãããŠããŸããïŒ", + "description": "<p class=\"mb-3\">æ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ãããã®ã§ãããªããžãäœ¿ã£ãŠè©ŠããŠã¿ãŠäžãããããããªããžã¯Torãã©ãŠã¶ãŒã«çµã¿èŸŒãŸãããããåããŠTorãã©ãŠã¶ãŒãéãæã«è¡šç€ºãããTor LauncherãŠã£ã³ããŠã«ãããèšå®ããéžæããŠäžããïŒãããŠããã³ããã«åŸã£ãŠäžããïŒãä»ã®ããªããžãå¿èŠãªããç§ãã¡ã®<mark><a href=\"https://bridges.torproject.org/\">ããªããžWEBãµã€ã</a></mark>ããæã«å¥ããããšãã§ããŸããè©³çŽ°ã«ã€ããŠã¯ã<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Torãã©ãŠã¶ãŒã®ãŠãŒã¶ãŒããã¥ã¢ã«</a></mark>ã«ããªããžã«é¢ããç« ãèª¿ã¹ãŠäžããã</p>" + }, + "censorship-5": { + "id": "#æ€é²-5", + "control": "æ€é²-5", + "title": "Torã«ã¢ã¯ã»ã¹ã§ããªãããäœãåé¡ãªã®ãåãããŸããã", + "description": "<p class=\"mb-3\">Torã«ã¢ã¯ã»ã¹ã§ããªãå ŽåããTorãã°ãã¯ãªããããŒãã«ã³ããŒãããéžæè¢ãéžãã§ããã°ãã¡ã¢åž³ãããã¯ããã¥ã¡ã³ããã¡ã€ã«ã«è²Œãä»ããŠäžãããä»¥äžã®è¯ããããšã©ãŒã¡ãã»ãŒãžãèŠã€ããã¯ãã§ãïŒ</p><h5>ãããããã°ãšã©ãŒ#1: ãããã·æ¥ç¶å€±æ</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx.. xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãSOCKSãããã·ãšç¹ãããªããšããããšã§ãããããã¯ãŒã¯ã«ã¯SOCKSãããã·ãå¿èŠãªããèšå®ãç¢ºèªããŠäžãããSOCKSãããã·ãå¿èŠã§ã¯ãªãå Žåããããã¯ããåãããªãå ŽåãSOCKSãããã·ç¡ãã§Torã«ã¢ã¯ã»ã¹ããŠã¿ãŠäžããã<p><h5>ãããããã°ãšã©ãŒ#2: ã¬ãŒããªã¬ãŒãšæ¥ç¶ã§ããªã</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discardi ng this circuit.</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorã¯circuitã®æåã®ããŒããšæ¥ç¶ã§ããªãã£ããšããããšã§ããæ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ããããŸããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããã¯ãã§ãã</p><h5>ãããããã°ãšã©ãŒ#3: TLSãã³ãã·ã§ã€ã¯ã®å€±æ</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãTorããã£ã¬ã¯ããªãªãŒãœãªãã£ãšTLSãã³ãã·ã§ã€ã¯ãå®äºã§ããªãã£ããšããããšã§ããããªããžãäœ¿ã£ãŠTorã«ã¢ã¯ã»ã¹ãããåé¡ãè§£æ±ºã§ããå¯èœæ§ãããã</p><h5>ãããããã°ãšã©ãŒ#4: ã¯ããã¯ã¹ãã¥ãŒ</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p clas s=\"mb-3\">Torãã°ã«ãã®ãããªè¡ãããã°ãã·ã¹ãã ã»ã¯ããã¯ã«ã¯ééã£ãæå»ãèšå®ãããŸããã·ã¹ãã ã»ã¯ããã¯ãæ£ããæå»ãšã¿ã€ã ãŸãŒã³ã«åãããŠããTorãåèµ·åããŠäžããã </p>" + }, + "censorship-6": { + "id": "#æ€é²-6", + "control": "æ€é²-6", + "title": "Torãã©ãŠã¶ãŒã«æ¥ç¶ã§ããŸãããç§ã®ãããã¯ãŒã¯ã¯æ€é²ãããŠããŸããïŒ", + "description": "<p class=\"mb-3\">æ€é²ããããããã¯ãŒã¯ã«æ¥ç¶ããŠããå¯èœæ§ãããã®ã§ãããªããžãäœ¿ã£ãŠè©ŠããŠã¿ãŠäžãããããããªããžã¯Torãã©ãŠã¶ãŒã«çµã¿èŸŒãŸãããããåããŠTorãã©ãŠã¶ãŒãéãæã«è¡šç€ºãããTor LauncherãŠã£ã³ããŠã«ãããèšå®ããéžæããŠäžããïŒãããŠããã³ããã«åŸã£ãŠäžããïŒãä»ã®ããªããžãå¿èŠãªããç§ãã¡ã®<mark><a href=\"https://bridges.torproject.org/\">ããªããžWEBãµã€ã</a></mark>ããæã«å¥ããããšãã§ããŸããè©³çŽ°ã«ã€ããŠã¯ã<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Torãã©ãŠã¶ãŒã®ãŠãŒã¶ãŒããã¥ã¢ã«</a></mark>ã«ããªããžã«é¢ããç« ãèª¿ã¹ãŠäžããã</p>" + } + + +} diff --git a/jv.json b/jv.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/jv.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ka.json b/ka.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ka.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/kk.json b/kk.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/kk.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/km.json b/km.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/km.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/kn.json b/kn.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/kn.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ko.json b/ko.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ko.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ko_KR.json b/ko_KR.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ko_KR.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ku.json b/ku.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ku.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ku_IQ.json b/ku_IQ.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ku_IQ.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/kw.json b/kw.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/kw.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ky.json b/ky.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ky.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/la.json b/la.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/la.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/lb.json b/lb.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/lb.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/lg.json b/lg.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/lg.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ln.json b/ln.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ln.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/lo.json b/lo.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/lo.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/lt.json b/lt.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/lt.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/lv.json b/lv.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/lv.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/mg.json b/mg.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/mg.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/mi.json b/mi.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/mi.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/mk.json b/mk.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/mk.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ml.json b/ml.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ml.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/mn.json b/mn.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/mn.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/mr.json b/mr.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/mr.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ms_MY.json b/ms_MY.json new file mode 100644 index 000000000..1e214b28c --- /dev/null +++ b/ms_MY.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Laman sesawang kami telah ditapis. Bolehkan Pelayar Tor membantu pengguna capai laman sesawang kami?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Bagaimana saya boleh memuat turun Tor jika torproject.org telah disekat?", + "description": "<p class=\"mb-3\">Jika anda tidak boleh memuat turun Tor melalui â<mark><a href=\"https://www.torproject.org\">laman sesawang</a></mark> kami, anda boleh dapatkan satu salinan Tor yang dihantar terus menerusi GetTor. GetTor merupakan servis yang membalas secara automatik mesej dengan pautan ke versi terkini Pelayar Tor, telah dihos dengan pada pelbagai lokasi yang berkemungkinan tidak ditapis, seperti Dropbox, Google Drive, dan Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Saya menghadapi masalah ketika menyambung dengan Tor, dan saya tidak tahu apa masalah yang berlaku.", + "description": "<p class=\"mb-3\">Jika anda menghadapi masalah sambungan, pilih pilihan \"salin log Tor ke papan keratan.â Kemudian tampal log Tor ke dalam fail teks atau lain-lain fail dokumen. Anda akan dapati terdapat ralat log (lihat baris berikut di dalam log Tor anda):</p><h5>Ralat log umum #1: Kegagalan sambungan proksi</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\" )</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud anda gagal menyambung dengan proksi SOCKS. Jika proksi SOCKS diperlukan untuk persediaan rangkaian anda, maka sila pastikan anda telah memasukkan perincian proksi tersebut dengan betul. Jika proksi SOCKS tidak diperlukan, atau anda tidak pasti, cuba sambung ke rangkaian Tor tanpa proksi SOCKS.<p><h5>Ralat log umum #2: Tidak dapat capai geganti pengawal</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb- 3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud Tor anda gagal menyambung ke nod pertama dalam litar Tor. Ia bermaksud anda berada dalam rangkaian bertapis. Cuba menyambung dengan titi, dan sepatutnya ia masalah selesai.</p><h5>Ralat log umum #3: Gagal menyelesaikan jabat-tangan TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat ba ris seperti ini di dalam log Tor anda, ia bermaksud Tor gagal menyelesaikan jabat-tangan TLS dengan autoriti direktori. Penggunaan titi dapat menyelesaikan masalah ini.</p><h5>Ralat log umum #4: Pencong jam</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini dalam log Tor anda, ia bermaksud jam sistem anda salah. Sila pastikan jam anda telah ditetapkan dengan tepat, termasuklah zon waktu yang betul. Kemudian mulakan semula Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/mt.json b/mt.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/mt.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/my.json b/my.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/my.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/nah.json b/nah.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/nah.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/nap.json b/nap.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/nap.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/nb.json b/nb.json new file mode 100644 index 000000000..80a0c173c --- /dev/null +++ b/nb.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "VÃ¥r nettside er blokkert av en sensurinstans. Kan Tor-nettleseren hjelpe brukere Ã¥ nÃ¥ den?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Min favorittnettside blokkerer tilgang fra Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Hvordan kan jeg laste ned Tor hvis torproject.org er blokkert?", + "description": "<p class=\"mb-3\">Hvis du ikke kan laste ned Tor fra vÃ¥r â<mark><a href=\"https://www.torproject.org\">nettside</a></mark>, kan du fÃ¥ en kopi levert via GetTor, en tjeneste som automatisk svarer med lenker til seneste versjon av Tor-nettleseren, hvis vertskap er betjent av forskjellige steder det er mindre mulighet for at er sensurert, som Dropbox, Google Drive og GitHub.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/nds.json b/nds.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/nds.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ne.json b/ne.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ne.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/nl.json b/nl.json new file mode 100644 index 000000000..9f96969e7 --- /dev/null +++ b/nl.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censuur-1", + "control": "censuur-1", + "title": "Onze website wordt geblokkeerd door een censor. Kan Tor Browser gebruikers helpen toegang tot onze website te krijgen?", + "description": "<p class=\"mb-3\">Tor Browser kan mensen zeker helpen toegang te krijgen tot uw website op plaatsen waar deze is geblokkeerd. Meestal gewoon downloaden van de <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> en dan gebruik het om te navigeren naar de geblokkeerde site en zal toegang toestaan. Op plaatsen waar sprake is van zware censuur hebben we een aantal opties voor censuurontwijking beschikbaar, waaronder <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">inplugbare transports</a></mark>. Voor meer informatie, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/\"> Tor Browser Gebruiker Manual</a></mark> hoofdstuk over <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censuur-2", + "control": "censuur-2", + "title": "Mijn favoriete website blokkeert de toegang via Tor.", + "description": "<p class=\"mb-3\">Sorry om te horen dat je de website die je wilde niet kunt bezoeken! Soms blokkeren websites Tor-gebruikers omdat ze niet het verschil kunnen zien tussen de gemiddelde Tor-gebruiker en automatisch verkeer. Het beste succes dat we hebben gehad bij het ontgrendelen van Tor-gebruikers, is ervoor te zorgen dat gebruikers rechtstreeks contact opnemen met de sitebeheerders. Zoiets zou de slag kunnen slaan: <br /> \"Hallo! Ik probeerde toegang tot uw site xyz.com te krijgen tijdens het gebruik van Tor Browser en ontdekte dat u Tor gebruikers geen toegang tot uw site verleent. Ik dring er bij u op aan om deze beslissing opnieuw te overwegen; gebruikt door mensen over de hele wereld om hun privacy te beschermen en censuur te bestrijden. Door Tor-gebruikers te blokkeren, blokkeert u waarschijnlijk mensen in repressieve landen die een gratis internet willen gebruiken, journalisten en onderzoekers die zichzelf willen beschermen tegen ontdekking, klokkenluiders , activisten en gewone mensen die willen opteren voor invasieve tracking door derden. Stel u ten stelligste voor ten gunste van digitale privacy en internetvrijheid en geef Tor-gebruikers toegang tot xyz.com. Dank u. \"<br />In het geval van banken en andere gevoelige websites, is het ook gebruikelijk om op geografie gebaseerde blokkering te zien (als een bank weet dat u over het algemeen toegang hebt tot hun services vanuit het ene land en plotseling verbinding maakt via een uitgaande relais aan de andere kant van de wereld, is uw account mogelijk vergrendeld Of geschorst). Als u geen verbinding kunt maken met een onion service, raadpleegt u <a href=\"http://127.0.0.1:5000/#onionservices-3\">Ik kan X.onion niet bereiken! </a></p>" + }, + "censorship-3": { + "id": "#censuur-3", + "control": "censuur-3", + "title": "Hoe kan ik Tor downloaden als het torproject.org is geblokkeerd?", + "description": "<p class=\"mb-3\">Als u Tor niet via onze <mark><a href=\"https://www.torproject.org\">website</a></mark> kunt downloaden, kunt u via GetTor een exemplaar van Tor aan u laten bezorgen. GetTor is een service die automatisch reageert op berichten met links naar de nieuwste versie van Tor Browser, gehost op verschillende locaties die minder vaak worden gecensureerd, zoals Dropbox, Google Drive en Github.</p>" + }, + "censorship-4": { + "id": "#censuur-4", + "control": "censuur-4", + "title": "Ik kan geen verbinding maken met de Tor-browser, wordt mijn netwerk gecensureerd?", + "description": "<p class=\"mb-3\">Mogelijk bevindt u zich op een gecensureerd netwerk en moet u dus proberen bruggen te gebruiken. Sommige bruggen zijn ingebouwd in Tor Browser en u kunt die bruggen gebruiken door \"configure\" te kiezen (gevolgd door de aanwijzingen) in het Tor Launcher-venster dat verschijnt wanneer u Tor Browser voor de eerste keer opent. Als u andere bruggen nodig heeft, kunt u ze vinden op onze <mark><a href=\"https://bridges.torproject.org/\">Bridges-website</a></mark>.Voor meer informatie over bruggen, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser-handleiding</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censuur-5", + "control": "censuur-5", + "title": "Ik ondervind problemen bij het verbinding maken met Tor, en ik vind maar niet wat er fout gaat.", + "description": "<p class=\"mb-3\">Als u problemen ondervindt bij het verbinden, selecteert u de optie om \"Tor log naar klembord te kopiÃ«ren\". Plak vervolgens het Tor-log in een tekstbestand of een ander document. U zou een van deze Vaak voorkomend logfouten moeten zien (kijk naar de volgende regels in uw Tor-logboek): </p><h5>Vaak voorkomend logboekfout # 1: Proxy-verbindingsfout</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09: 23: 40.800 [LET OP] Opening Socks luisteraar op 127.0.0.1 : 9150 \n 2017-10-29 09: 23: 47.900 [LET OP] Bootstrapped 5%: verbinden met directoryserver \n 2017-10-29 09: 23: 47.900 [LETICE] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-clie nt: kan toxx..xxx..xxx.xx: xxxxx niet verbinden (\"algemene SOCKS-serverstoring\") </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, is dit betekent dat u geen verbinding kunt maken met een SOCKS-proxy. Als een SOCKS-proxy vereist is voor uw netwerkconfiguratie, moet u ervoor zorgen dat u uw proxy-gegevens correct hebt ingevoerd. Als een SOCKS-proxy niet vereist is, of als u het niet zeker weet, probeer dan verbinding te maken met het Tor-netwerk zonder een SOCKS-proxy.<p><h5>Gebruikslog fout # 2: Kan relais niet bereiken</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM .500 [LET OP] Luisteraar luisterpositie openen op 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [LET OP] Bootstrapped 80%: Verbinding maken met het Tor-netwerk \n 11/1/2017 21:11:44 PM.300 [WARN] Kan knooppunt voor hop 0 van ons pad niet vinden. Dit circuit weggooien. \n 11/1/2017 21:11:44 PM.500 [LET OP] Bootstrap 85%: Handshake beÃ«indigen met eerste hop \n 11/1/2017 21:11:45 P M.300 [WARN] Kan knooppunt niet vinden voor hop 0 van ons pad. Dit circuit verwijderen.</code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dit dat uw Tor geen verbinding kon maken met het eerste knooppunt in het Tor-circuit. Dit kan betekenen dat u zich op een netwerk bevindt dat gecensureerd is. Probeer te verbinden met bruggen, en dat zou het probleem moeten verhelpen.</p><h5> Algemene logfout # 3: Kan TLS-handshake niet voltooien</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 13-11-17 19: 53: 49.300 [WARN] Probleem met bootstrappen. Vastgelopen met 10%: handshake beÃ«indigen met directoryserver. (GEDAAN, GEDAAN, aantal 10; advieswaarschuwing; host [host] op xxx.xxx.xxx.xx: xxx) \n 13-11-17 19: 53: 49.300 [WARN] 10 verbindingen zijn mislukt: \n 13-11-17 19: 53: 49.300 [WARN] 9 verbindingen stierven in staatshandshaking (TLS) met SSL-status SSLv2 / v3 lezen server hallo A in HANDSHAKE \n 13-11-17 19: 53: 49.300 [WARN] 1 verbindingen zijn overleden in state connect () ing met SSL-staat (No SSL-object) </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dat Tor een TLS-handshake niet kon voltooien met de directory-autoriteiten. Het gebruik van bruggen lost dit waarschijnlijk op.</p><h5>Veel logboekfout # 4: Klok skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00: 04: 47.400 [LET OP] Opening Socks luisteraar op 127.0.0.1:9150 \n 19.11.2017 00: 04: 48.000 [LET OP] Bootstrap 5%: verbinding maken met directoryserver \n 19.11.2017 00: 04: 48.200 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 19.11.2017 00: 04: 48.800 [WARN] NETINFO-cel ontvangen met scheve tijd (OF: xxx.xx.x.xx: xxxx): het lijkt erop dat onze klok 1 dag, 0 uur, 1 minuut achterloopt, of die van hen liggen voor de deur. \n Tor vereist een nauwkeurige klok om te werken: controleer uw tijd-, tijdzone- en datuminstellin gen.</code></pre></p><p class=\"mb-3\">Als u lijnen zoals deze in uw Tor-logboek ziet, betekent dit dat uw systeemklok onjuist is. Zorg ervoor dat uw klok correct is ingesteld, inclusief de juiste tijdzone. Start dan Tor opnieuw. </p>" + }, + "censorship-6": { + "id": "#censuur-6", + "control": "censuur-6", + "title": "Ik kan geen verbinding maken met de Tor-browser, wordt mijn netwerk gecensureerd?", + "description": "<p class=\"mb-3\">Mogelijk bevindt u zich op een gecensureerd netwerk en moet u dus proberen bruggen te gebruiken. Sommige bruggen zijn ingebouwd in Tor Browser en u kunt die bruggen gebruiken door \"configure\" te kiezen (gevolgd door de aanwijzingen) in het Tor Launcher-venster dat verschijnt wanneer u Tor Browser voor de eerste keer opent. Als u andere bruggen nodig heeft, kunt u ze vinden op onze <mark><a href=\"https://bridges.torproject.org/\">Bridges-website</a></mark>.Voor meer informatie over bruggen, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser-handleiding</a></mark>.</p>" + } + + +} diff --git a/nl_BE.json b/nl_BE.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/nl_BE.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/nn.json b/nn.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/nn.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/nso.json b/nso.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/nso.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/oc.json b/oc.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/oc.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/om.json b/om.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/om.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/or.json b/or.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/or.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/pa.json b/pa.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/pa.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/pap.json b/pap.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/pap.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/pl.json b/pl.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/pl.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/pms.json b/pms.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/pms.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ps.json b/ps.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ps.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/pt.json b/pt.json new file mode 100644 index 000000000..d50c3aefb --- /dev/null +++ b/pt.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "O nosso site da Web estÃ¡ bloqueado por um censor. O Tor Browser pode ajudar os utilizadores a aceder ao nosso site da Web?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "O meu site da Web favorito estÃ¡ a bloquear o acesso ao Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Como Ã© que eu transfiro o Tor se o torproject.org estiver bloqueado?", + "description": "<p class=\"mb-3\">Se nÃ£o conseguir transferir o Tor atravÃ©s do nosso <mark><a href=\"https://www.torproject.org\">site da Web</a></mark>, pode obter uma cÃ³pia do Tor enviada para si atravÃ©s do GetTor. O GetTor Ã© um serviÃ§o que responde automaticamente Ã s mensagens com hiperligaÃ§Ãµes para a versÃ£o mais recente do Tor Browser, alojado em vÃ¡rios locais que sÃ£o menos propensos a serem censurados, tais como Dropbox, Google Drive e Github.1" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "Eu nÃ£o consigo ligar ao Tor Browser. A minha rede estÃ¡ censurada?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Eu estou a ter problemas para ligar ao Tor, e eu nÃ£o consigo descobrir o que estÃ¡ errado.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "Eu nÃ£o consigo ligar-me ao Tor Browser. A minha rede estÃ¡ censurada?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/pt_BR.json b/pt_BR.json new file mode 100644 index 000000000..75c340dd5 --- /dev/null +++ b/pt_BR.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censura-1", + "control": "censura-1", + "title": "Nosso site estÃ¡ bloqueado por um censor. O Navegador Tor pode ajudar aos usuÃ¡rios a acessar nosso site?", + "description": "<p class=\"mb-3\">O Navegador Tor pode certamente ajudar as pessoas a acessarem seu site em lugares onde ele Ã© bloqueado. Na maioria das vezes, basta baixar oâ<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Navegador Tor</a></mark> e usÃ¡-lo para navegar atÃ© o site bloqueado para permitir o acesso. Em locais onde hÃ¡ uma forte censura, temos vÃ¡rias opÃ§Ãµes de contornar a censura disponÃveis, incluindo â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">transportes plugÃ¡veis</a></mark>. Para mais informaÃ§Ãµes, consulte o<mark>Manual do UsuÃ¡rio do Navegador Tor</a>sobre censura</mark>.</p>" + }, + "censorship-2": { + "id": "#censura-2", + "control": "censura-2", + "title": "Meu website favorito estÃ¡ bloqueando o acesso via Tor.", + "description": "<p class=\"mb-3\"> Lamentamos saber que vocÃª nÃ£o pode visitar o website que quer! Ãs vezes, os websites bloqueam os usuÃ¡rios do Tor porque nÃ£o sabem a diferenÃ§a entre o usuÃ¡rio mÃ©dio e o trÃ¡fego automatizado. Uma estratÃ©gia na qual temos obtido sucesso para fazer os websites desbloquearem os usuÃ¡rios do Tor Ã© fazer com que os prÃ³prios usuÃ¡rios contatem os administradores do site diretamente. Algo assim deve funcionar: <br /> \"OlÃ¡! Eu tentei acessar seu website xyz.com enquanto utilizando o Tor Browser e descobri que nÃ£o hÃ¡ permissÃ£o de acesso para usuÃ¡rios do Tor. Eu peÃ§o que reconsiderem essa decisÃ£o; o Tor Ã© utilizado por pessoas de todo o mundo que querem proteger sua privacidade e lutar contra a censura. Ao bloquear os usuÃ¡rios do Tor, vocÃªs estÃ£o provavelmente bloqueando pessoas que querem usar uma internet livre em paÃses opressores, jornalistas e pesquisadores que querem se proteger, ativistas e pessoas comuns que querem se livrar d o rastreamento de terceiros invasivos. Por favor, tomem uma posiÃ§Ã£o forte em favor da privacidade digital e da liberdade na internet e permitam os usuÃ¡rios do Tor o acesso ao xyz.com. Obrigado.\" <br />No caso dos bancos, e outros sensitive websites, Ã© tambÃ©m comum que apareÃ§am bloqueios baseados na localizaÃ§Ã£o geogrÃ¡fica (se um banco sabe que vocÃª geralmente acessa seus serviÃ§os de um paÃs, e de repente vocÃª estÃ¡ conectando de uma exit relay no outro lado do mundo, sua conta pode ser trancada ou suspensa). Se vocÃª nÃ£o consegue se conectar a um onion service, por favor ver <a href=\"http://127.0.0.1:5000/#onionservices-3\">NÃ£o consigo acessar X.onion! </a> </p>" + }, + "censorship-3": { + "id": "#censura-3", + "control": "censura-3", + "title": "Como eu baixo Tor caso torproject.org esteja bloqueado?", + "description": "<p class=\"mb-3\">Se nÃ£o conseguir fazer o download usando o <mark><a href=\"https://www.torproject.org\"> website </a></mark>, vocÃª pode obter uma cÃ³pia do Tor via GetTor. GetTor Ã© um serviÃ§o que automaticamente responde Ã s mensagens com links para a Ãºltima versÃ£o do Navegador Tor, hospedado em uma variedade de locais menos propensos a serem censurados, como Dropbox, Google Drive e GitHub. </p>" + }, + "censorship-4": { + "id": "#censura-4", + "control": "censura-4", + "title": "Eu nÃ£o consigo conectar ao Tor Browser, a minha rede estÃ¡ censurada?", + "description": "<p class=\"mb-3\">VocÃª pode estar em uma rede censurada e, assim, vocÃª deveria tentar usar bridges. Algumas bridges sÃ£o construÃdas no Tor Browser e vocÃª pode usÃ¡-las escolhendo \"configure\" (e seguir as instruÃ§Ãµes) na janela Tor Launcher que aparece quando vocÃª abre o Tor Browser pela primeira vez. Se vocÃª precisar de outras bridges, vocÃª pode consegui-las em nosso <mark><a href=\"https://bridges.torproject.org/\">Bridges website </a></mark>. Para mais informaÃ§Ãµes sobre bridges, veja o <a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manual do Tor Browser </a><mark>.</mark>" + }, + "censorship-5": { + "id": "#censura-5", + "control": "censura-5", + "title": "Estou tendo problemas para conectar ao Tor e nÃ£o consigo descobrir o que estÃ¡ dando errado.", + "description": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opÃ§Ã£o para \"copiar o log de Tor para a Ã¡rea de transferÃªncias\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. VocÃª deverÃ¡ ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexÃ£o de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretÃ³rio\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretÃ³rio\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0 8.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se vocÃª encontrar linhas como estas em seu log do Tor, isto significa que falhou em conectar-se Ã um SOCKS proxy. Se um SOCKS proxy Ã© obrigatÃ³rio para a sua configuraÃ§Ã£o de rede, por favor certifique-se que vocÃª digitou seus detalhes de proxy corretamente. Se um SOCKS proxy nÃ£o Ã© obrigatÃ³rio, ou vocÃª nÃ£o estÃ¡ certo sobre isso, por favor tente conectar-se Ã rede Tor sem um SOCKS proxy. Erro de log comum #2: Canât reach guard relays 11/1/2017 21:11:43 PM.500 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [OBSERVE] Bootstrapped 80%: Conectando Ã rede Tor\n11/1/2017 21:11:44 PM.300 [AVISO] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [OBSERVE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [AVISO] 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\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hands hake 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\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor 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. " + }, + "censorship-6": { + "id": "#censura-6", + "control": "censura-6", + "title": "Eu nÃ£o consigo me conectar ao Navegador Tor, minha rede estÃ¡ censurada?", + "description": "<p class=\"mb-3\">VocÃª deve estar em uma internet censurada, e por isso vocÃª deve tentar usar pontes. Algumas pontes jÃ¡ sÃ£o feitas para o Navegador Tor, e vocÃª pode usar estas pontes selecionando \"configurar\" (e seguir os passos) na janela de inicializaÃ§Ã£o do Tor que aparece quando vocÃª abre o Navegador Tor pela primeira vez. Se vocÃª precisar de outras pontes, vocÃª pode consegui-las em nosso <mark><a href=\"https://bridges.torproject.org/\">website de Pontes</a></mark>. Para mais informaÃ§Ãµes sobre pontes, veja o <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manual do Navegador Tor</a></mark>.</p>" + } + + +} diff --git a/ro.json b/ro.json new file mode 100644 index 000000000..559d4978f --- /dev/null +++ b/ro.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Cum descarc Tor dacÄ torproject.org e blocat?", + "description": "<p class=\"mb-3\">DacÄ nu poÈi descÄrca Tor din â<mark><a href=\"https://www.torproject.org\">website</a></mark>, poÈi obÈine o o copie a Tor prin intermediul GetTor. GetTor e un serviciu care rÄspunde automat la mesaje cu legÄturi cÄtre ultima versiune de Tor Browser stocata Ã®ntr-o varietate de locuri mai puÈin probabil de a fi cenzurate, cum ar fi Dropbox, Google Drive sau Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Am dificultÄÈi Ã®n conectarea la Tor Èi nu Ã®nÈeleg ce e greÈit.", + "description": "<p class=\"mb-3\">DacÄ aveÈi probleme de conectare, selectaÈi opÈiunea \"copiazÄ log-ul Tor Ã®n clipboard\". Apoi lipiÈi log-ul astfel copiat Ã®ntr-un fiÈier text sau alt document. Ar trebui sÄ vedeÈi unul dintre aceste mesaje de eroare comune (cÄutaÈi astfel de linii Ã®n log-ul Tor):</p><h5>Eroare comunÄ #1: Eroare de conectare la proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxx xx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">DacÄ vedeÈi astfel de linii in log-ul Tor, Ã®nseamnÄ cÄ nu vÄ puteÈi conecta la un proxy SOCKS. DacÄ un proxy SOCKS este necesar pentru reÈeaua pe care o folosiÈi, atunci asiguraÈi-vÄ cÄ aÈi introdus setÄrile de proxy corecte. DacÄ un proxy SOCKS nu e necesar sau nu sunteÈi sigur, Ã®ncercaÈi sÄ vÄ conectaÈi la reÈeaua Tor fÄrÄ un proxy SOCKS.<p><h5>Eroare comunÄ #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></p re></p><p class=\"mb-3\">DacÄ vedeÈi astfel de linii in log-ul Tor Ã®nseamnÄ ca nu s-a reuÈit conectarea la primul nod din circuitul Tor. Aceasta ar putea Ã®nsemna cÄ vÄ aflaÈi Ã®ntr-o reÈea cenzuratÄ. ÃncercaÈi conectarea prin punÈi, care ar trebui sÄ rezolve problema.</p><h5>Eroare comunÄ #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Dac Ä vedeÈi astfel de linii in log-ul Tor Ã®nseamnÄ cÄ nu s-a realizat o conexiune completÄ TLS cu serverele de directoare. Folosirea punÈilor va rezolva probabil acest lucru. </p><h5>Eroare comunÄ #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">DacÄ vedeÈi astfel de linii in log-ul Tor Ã®nseamnÄ cÄ ceasul sistemului Dvs. e incorect. AsiguraÈi-vÄ cÄ ceasul sistemului este corect, inclusiv fusul orar, apoi reporn iÈi Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ru.json b/ru.json new file mode 100644 index 000000000..f937981d6 --- /dev/null +++ b/ru.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "ÐÐ°Ñ ÑÐ°Ð¹Ñ Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°Ðœ ÑÐµÐœÐ·ÑÑÐŸÐ¹. Ð¡ÐŒÐŸÐ³ÑÑ Ð»Ðž Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ðž Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÑÐ°Ð¹ÑÑ ÑÐµÑÐµÐ· Tor Browser?", + "description": "<p class=\"mb-3\">Tor Browser Ð±ÐµÐ·ÑÑÐ»ÐŸÐ²ÐœÐŸ ÐŒÐŸÐ¶ÐµÑ Ð¿ÐŸÐŒÐŸÑÑ Ð»ÑÐŽÑÐŒ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº Ð²Ð°ÑÐµÐŒÑ Ð²ÐµÐ±-ÑÐ°Ð¹ÑÑ Ð² ÐŒÐµÑÑÐ°Ñ, Ð³ÐŽÐµ ÐŸÐœ Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°Ðœ. ÐÐŸÐ»ÑÑÑÑ ÑÐ°ÑÑÑ Ð²ÑÐµÐŒÐµÐœÐž Ð¿ÑÐŸÑÑÐ°Ñ Ð·Ð°Ð³ÑÑÐ·ÐºÐ° <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> Ðž ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÐœÐžÐµ ÐµÐ³ÐŸ ÐŽÐ»Ñ Ð¿ÐµÑÐµÑÐŸÐŽÐ° ÐœÐ° Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°ÐœÐœÑÐ¹ ÑÐ°Ð¹Ñ Ð¿ÐŸÐ·Ð²ÐŸÐ»ÐžÑ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐŽÐŸÑÑÑÐ¿ Ðº ÐœÐµÐŒÑ. Ð ÐŒÐµÑÑÐ°Ñ, Ð³ÐŽÐµ ÑÑÑÐµÑÑÐ²ÑÐµÑ ÑÑÐžÐ»ÐµÐœÐœÐ°Ñ ÑÐµÐœÐ·ÑÑÐ°, Ñ ÐœÐ°Ñ ÐµÑÑÑ ÑÑÐŽ ÐŽÐŸÑÑÑÐ¿ÐœÑÑ ÐžÐœÑÑÑÑÐŒÐµÐœÑÐŸÐ² ÐŸÐ±ÑÐŸÐŽÐ° ÑÐµÐœÐ·ÑÑÑ, Ð²ÐºÐ»ÑÑÐ°Ñ <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. ÐÐ° ÐŽÐŸÐ¿ÐŸÐ»ÐœÐžÑÐµÐ»ÑÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐµÐ¹, Ð¿ÐŸÐ¶Ð°Ð»ÑÐ¹ÑÑÐ°, ÐŸÐ±ÑÐ°ÑÐžÑÐµÑÑ Ðº ÑÐ°Ð·ÐŽÐµÐ»Ñ <mark><a hre f=\"https://tb-manual.torproject.org/en-US/circumvention.html\">ÐŸ ÑÐµÐœÐ·ÑÑÐµ</a></mark> Ð² <mark><a href=\"https://tb-manual.torproject.org/en-US/\">ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²Ðµ Ð¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÐµÐ»Ñ Tor Browser</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "ÐÐŸÐ¹ Ð»ÑÐ±ÐžÐŒÑÐ¹ ÑÐ°Ð¹Ñ Ð±Ð»ÐŸÐºÐžÑÑÐµÑ ÐŽÐŸÑÑÑÐ¿ ÑÐµÑÐµÐ· Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "ÐÐ°Ðº Ð·Ð°Ð³ÑÑÐ·ÐžÑÑ Tor, ÐµÑÐ»Ðž torproject.org Ð·Ð°Ð±Ð»ÐŸÐºÐžÑÐŸÐ²Ð°Ðœ?", + "description": "<p class=\"mb-3\">ÐÑÐ»Ðž ÐÑ ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ ÑÐºÐ°ÑÐ°ÑÑ Tor ÑÐµÑÐµÐ· ÐœÐ°Ñ <mark><a href=\"https://www.torproject.org\">ÑÐ°Ð¹Ñ</a></mark>, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐºÐŸÐ¿ÐžÑ Tor ÑÐµÑÐµÐ· GetTor. GetTor - ÑÑÐŸ ÑÑÐ»ÑÐ³Ð°, ÐºÐŸÑÐŸÑÐ°Ñ Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐµÑÐºÐž ÐŸÑÐ²ÐµÑÐ°ÐµÑ ÐœÐ° ÑÐŸÐŸÐ±ÑÐµÐœÐžÑ ÑÑÑÐ»ÐºÐ°ÐŒÐž ÐœÐ° Ð¿ÐŸÑÐ»ÐµÐŽÐœÑÑ Ð²ÐµÑÑÐžÑ Tor Browser, ÑÐ°Ð·ÐŒÐµÑÐµÐœÐœÑÐµ Ð² ÑÐ°Ð·Ð»ÐžÑÐœÑÑ ÐŒÐµÑÑÐ°Ñ, ÐºÐŸÑÐŸÑÑÐµ ÐŒÐµÐœÐµÐµ Ð²ÐµÑÐŸÑÑÐœÐŸ Ð¿ÐŸÐŽÐ²ÐµÑÐ³Ð°ÑÑÑÑ ÑÐµÐœÐ·ÑÑÐµ, ÑÐ°ÐºÐžÐµ ÐºÐ°Ðº Dropbox, Google ÐÐžÑÐº Ðž Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "Ð¯ ÐœÐµ ÐŒÐŸÐ³Ñ Ð¿ÐŸÐŽÐºÐ»ÑÑÐžÑÑÑÑ Ðº Tor Browser, ÐŒÐŸÑ ÑÐµÑÑ ÑÐµÐœÐ·ÑÑÐžÑÑÐµÑÑÑ?", + "description": "<p class=\"mb-3\">ÐÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ, Ð²Ñ ÐœÐ°ÑÐŸÐŽÐžÑÐµÑÑ Ð² Ð¿ÐŸÐŽÐ²ÐµÑÐ³Ð°ÐµÐŒÐŸÐ¹ ÑÐµÐœÐ·ÑÑÐµ ÑÐµÑÐž, Ð¿ÐŸÑÑÐŸÐŒÑ Ð²Ð°ÐŒ ÑÐ»ÐµÐŽÑÐµÑ Ð¿ÐŸÐ¿ÑÐŸÐ±ÐŸÐ²Ð°ÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŒÐŸÑÑÑ. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÑÑÑ Ð²ÑÑÑÐŸÐµÐœÑ Ð² Tor Browser, Ðž Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÐž ÐŒÐŸÑÑÑ, Ð²ÑÐ±ÑÐ°Ð² Â«ÐÐ°ÑÑÑÐŸÐžÑÑÂ» (ÐŽÐ°Ð»ÐµÐµ ÑÐ»ÐµÐŽÑÑ Ð¿ÐŸÐŽÑÐºÐ°Ð·ÐºÐ°ÐŒ) Ð² ÐŸÐºÐœÐµ Ð·Ð°Ð¿ÑÑÐºÐ° Tor, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÑÐ¿Ð»ÑÐ²Ð°ÐµÑ Ð¿ÑÐž Ð¿ÐµÑÐ²ÐŸÐŒ ÐŸÑÐºÑÑÑÐžÐž Tor Browser. ÐÑÐ»Ðž Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÑ ÐŽÑÑÐ³ÐžÐµ ÐŒÐŸÑÑÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐžÑ ÐœÐ° ÐœÐ°ÑÐµÐŒ <mark><a href=\"https://bridges.torproject.org/\">Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐµ, Ð¿ÐŸÑÐ²ÑÑÐµÐœÐœÐŸÐŒ ÐŒÐŸÑÑÐ°ÐŒ</a></mark>. ÐÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸ ÐŒÐŸÑÑÐ°Ñ, ÑÐŒ. <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Tor Browser</a></mark>. </p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "Ð¯ ÐœÐµ ÐŒÐŸÐ³Ñ Ð¿ÐŸÐŽÐºÐ»ÑÑÐžÑÑÑÑ Ðº Tor Browser, ÐŒÐŸÑ ÑÐµÑÑ ÑÐµÐœÐ·ÑÑÐžÑÑÐµÑÑÑ?", + "description": "<p class=\"mb-3\">ÐÐŸÐ·ÐŒÐŸÐ¶ÐœÐŸ, Ð²Ñ ÐœÐ°ÑÐŸÐŽÐžÑÐµÑÑ Ð² Ð¿ÐŸÐŽÐ²ÐµÑÐ³Ð°ÐµÐŒÐŸÐ¹ ÑÐµÐœÐ·ÑÑÐµ ÑÐµÑÐž, Ð¿ÐŸÑÑÐŸÐŒÑ Ð²Ð°ÐŒ ÑÐ»ÐµÐŽÑÐµÑ Ð¿ÐŸÐ¿ÑÐŸÐ±ÐŸÐ²Ð°ÑÑ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÐŒÐŸÑÑÑ. ÐÐµÐºÐŸÑÐŸÑÑÐµ ÐŒÐŸÑÑÑ Ð²ÑÑÑÐŸÐµÐœÑ Ð² Tor Browser, Ðž Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ ÐžÑÐ¿ÐŸÐ»ÑÐ·ÐŸÐ²Ð°ÑÑ ÑÑÐž ÐŒÐŸÑÑÑ, Ð²ÑÐ±ÑÐ°Ð² Â«ÐÐ°ÑÑÑÐŸÐžÑÑÂ» (ÐŽÐ°Ð»ÐµÐµ ÑÐ»ÐµÐŽÑÑ Ð¿ÐŸÐŽÑÐºÐ°Ð·ÐºÐ°ÐŒ) Ð² ÐŸÐºÐœÐµ Ð·Ð°Ð¿ÑÑÐºÐ° Tor, ÐºÐŸÑÐŸÑÑÐ¹ Ð²ÑÐ¿Ð»ÑÐ²Ð°ÐµÑ Ð¿ÑÐž Ð¿ÐµÑÐ²ÐŸÐŒ ÐŸÑÐºÑÑÑÐžÐž Tor Browser. ÐÑÐ»Ðž Ð²Ð°ÐŒ ÐœÑÐ¶ÐœÑ ÐŽÑÑÐ³ÐžÐµ ÐŒÐŸÑÑÑ, Ð²Ñ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÐŸÐ»ÑÑÐžÑÑ ÐžÑ ÐœÐ° ÐœÐ°ÑÐµÐŒ <mark><a href=\"https://bridges.torproject.org/\">Ð²ÐµÐ±-ÑÐ°Ð¹ÑÐµ, Ð¿ÐŸÑÐ²ÑÑÐµÐœÐœÐŸÐŒ ÐŒÐŸÑÑÐ°ÐŒ</a></mark>. ÐÐ»Ñ Ð¿ÐŸÐ»ÑÑÐµÐœÐžÑ Ð±ÐŸÐ»ÐµÐµ Ð¿ÐŸÐŽÑÐŸÐ±ÐœÐŸÐ¹ ÐžÐœÑÐŸÑÐŒÐ°ÑÐžÐž ÐŸ ÐŒÐŸÑÑÐ°Ñ, ÑÐŒ. <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">ÑÑÐºÐŸÐ²ÐŸÐŽÑÑÐ²ÐŸ Tor Browser</a></mark>. </p>" + } + + +} diff --git a/ru(a)petr1708.json b/ru(a)petr1708.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ru(a)petr1708.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/scn.json b/scn.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/scn.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sco.json b/sco.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sco.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/si_LK.json b/si_LK.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/si_LK.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sk.json b/sk.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sk.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sk_SK.json b/sk_SK.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sk_SK.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sl.json b/sl.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sl.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sl_SI.json b/sl_SI.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sl_SI.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sn.json b/sn.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sn.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/so.json b/so.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/so.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/son.json b/son.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/son.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sq.json b/sq.json new file mode 100644 index 000000000..b4e0cb967 --- /dev/null +++ b/sq.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Siti ynÃ« Ã«shtÃ« i bllokuar nga njÃ« censurÃ«. Mundet Tor tÃ« ndihmoje pÃ«rdoruesit tÃ« aksesojn sitin tonÃ«?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sr.json b/sr.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sr.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sr(a)latin.json b/sr(a)latin.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sr(a)latin.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/st.json b/st.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/st.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/su.json b/su.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/su.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/support-censorship.json b/support-censorship.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/support-censorship.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sv.json b/sv.json new file mode 100644 index 000000000..f7115ef62 --- /dev/null +++ b/sv.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "VÃ¥r webbplats Ã€r blockerad av en censor. Kan Tor Browser hjÃ€lpa anvÃ€ndare att komma Ã¥t vÃ¥r webbplats?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "Min favoritwebbplats blockerar Ã¥tkomst Ã¶ver Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "Hur laddar jag ner Tor om torproject.org Ã€r blockerad?", + "description": "Om du inte kan ladda ner Tor pÃ¥ vÃ¥r â<mark><a href=\"https://www.torproject.org\">webbsajt</a></mark>, sÃ¥ kan du fÃ¥ Tor levererat till dig via GetTor. GetTor Ã€r en tjÃ€nst som automatiskt svarar pÃ¥ meddelanden med lÃ€nkar till den senaste versionen av Tor Browser, som finns pÃ¥ flera olika platser som sannolikt inte Ã€r censurerade, till exempel Dropbox, Google Drive och Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "Jag kan inte ansluta till Tor Browser, Ã€r mitt nÃ€tverk censurerat?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Jag har problem med att ansluta till Tor, och jag kan inte ta reda pÃ¥ vad som Ã€r fel.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "Jag kan inte ansluta till Tor Browser, Ã€r mitt nÃ€tverk censurerat?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/sw.json b/sw.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sw.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/szl.json b/szl.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/szl.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ta.json b/ta.json new file mode 100644 index 000000000..2b46484de --- /dev/null +++ b/ta.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#à®€à®£à®¿à®à¯à®à¯-1", + "control": "à®€à®£à®¿à®à¯à®à¯-1", + "title": "à®à®à¯à®à®³à¯ à®µà®²à¯à®€à¯à®€à®³à®®à¯ à®€à®£à®¿à®à¯à®à¯à®¯à®Ÿà®²à¯ à®€à®à¯à®à¯à®à®ªà¯à®ªà®à¯à®à¯à®³à¯à®³à®€à¯. à®à®Ÿà®°à¯ à®à®²à®Ÿà®µà®¿ à®à®à¯à®à®³à¯ à®µà®²à¯à®€à¯à®€à®³à®€à¯à®€à¯ à®à®£à¯à® à®ªà®¯à®©à®°à¯à®à®³à¯à®à¯à®à¯ à®à®€à®µ à®®à¯à®à®¿à®¯à¯à®®à®Ÿ?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/te.json b/te.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/te.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/te_IN.json b/te_IN.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/te_IN.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/tg.json b/tg.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/tg.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/th.json b/th.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/th.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ti.json b/ti.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ti.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/tk.json b/tk.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/tk.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/tr.json b/tr.json new file mode 100644 index 000000000..a546fcdf0 --- /dev/null +++ b/tr.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Sitemiz bir denetÃ§i tarafÄ±ndan engellenmiÅtir. Tor Browser sitemize eriÅebilmeleri iÃ§in kullanÄ±cÄ±lara yardÄ±m etsin mi?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "En sevdiÄim website'm Tor'a eriÅimimi engelliyor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "torproject.org' a eriÅilemiyorsa Tor 'u nasÄ±l indirebilirim?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "Tor taryÄ±cÄ±sÄ±na baÄlanamÄ±yorum. BaÄlantÄ±m sÄ±kÄ±ntÄ±lÄ± mÄ±?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "Tor 'a baÄlanmakta sÄ±kÄ±ntÄ± Ã§ekiyorum ve ne de problem olduÄunu bulamÄ±yorum.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "Tor Browser' a baÄlanamÄ±yorum. BaÄlantÄ±m sÄ±kÄ±ntÄ±lÄ± mÄ±?\n", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/tzm.json b/tzm.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/tzm.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ug(a)Arab.json b/ug(a)Arab.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ug(a)Arab.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/uk.json b/uk.json new file mode 100644 index 000000000..07e25c48c --- /dev/null +++ b/uk.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#ÑÐµÐœÐ·ÑÑÐ°-1", + "control": "ÑÐµÐœÐ·ÑÑÐ°-1", + "title": "ÐÐ°Ñ Ð²ÐµÐ±-ÑÐ°Ð¹Ñ Ð·Ð°Ð±Ð»ÐŸÐºÐŸÐ²Ð°ÐœÐžÐ¹ ÑÐµÐœÐ·ÐŸÑÐŸÐŒ. Ð§Ðž ÐŒÐŸÐ¶Ðµ Ð±ÑÐ°ÑÐ·ÐµÑ Tor ÐŽÐŸÐ¿ÐŸÐŒÐŸÐ³ÑÐž ÐºÐŸÑÐžÑÑÑÐ²Ð°ÑÐ°ÐŒ ÐŸÑÑÐžÐŒÐ°ÑÐž ÐŽÐŸÑÑÑÐ¿ ÐŽÐŸ ÐœÐ°ÑÐŸÐ³ÐŸ Ð²ÐµÐ±-ÑÐ°Ð¹ÑÑ?", + "description": "1" + }, + "censorship-2": { + "id": "#ÑÐµÐœÐ·ÑÑÐ°-2", + "control": "ÑÐµÐœÐ·ÑÑÐ°-2", + "title": "ÐÑÐ¹ ÑÐ»ÑÐ±Ð»ÐµÐœÐžÐ¹ Ð²ÐµÐ±-ÑÐ°Ð¹Ñ Ð±Ð»ÐŸÐºÑÑ ÐŽÐŸÑÑÑÐ¿ ÑÐµÑÐµÐ· Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#ÑÐµÐœÐ·ÑÑÐ°-3", + "control": "ÑÐµÐœÐ·ÑÑÐ°-3", + "title": "Ð¯Ðº Ð·Ð°Ð²Ð°ÐœÑÐ°Ð¶ÐžÑÐž Tor, ÑÐºÑÐŸ torproject.org Ð·Ð°Ð±Ð»ÐŸÐºÐŸÐ²Ð°ÐœÐžÐ¹?", + "description": "Ð¯ÐºÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð·Ð°Ð²Ð°ÐœÑÐ°Ð¶ÐžÑÐž Tor ÑÐµÑÐµÐ· ÐœÐ°ÑÐžÐ¹ Ð²ÐµÐ±-ÑÐ°Ð¹Ñ, Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐžÐŒÐ°ÑÐž ÐºÐŸÐ¿ÑÑ Tor, ÐŽÐŸÑÑÐ°Ð²Ð»ÐµÐœÑ Ð²Ð°ÐŒ ÑÐµÑÐµÐ· GetTor. GetTor â ÑÐµ ÑÐ»ÑÐ¶Ð±Ð°, ÑÐºÐ° Ð°Ð²ÑÐŸÐŒÐ°ÑÐžÑÐœÐŸ Ð²ÑÐŽÐ¿ÐŸÐ²ÑÐŽÐ°Ñ ÐœÐ° Ð¿ÐŸÐ²ÑÐŽÐŸÐŒÐ»ÐµÐœÐœÑ Ð· Ð¿ÐŸÑÐžÐ»Ð°ÐœÐœÑÐŒÐž ÐœÐ° ÐŸÑÑÐ°ÐœÐœÑ Ð²ÐµÑÑÑÑ Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor, ÑÐŸ ÑÐŸÐ·ÐŒÑÑÑÑÑÑÑÑ Ð² ÑÑÐ·ÐœÐžÑ ÐŒÑÑÑÑÑ, ÑÐºÑ, ÑÐº Ð¿ÑÐ°Ð²ÐžÐ»ÐŸ, ÐœÐµ Ð¿ÑÐŽÐ»ÑÐ³Ð°ÑÑÑ ÑÐµÐœÐ·ÑÑÑ, ÑÐ°ÐºÐžÑ ÑÐº Dropbox, Google ÐÐžÑÐº Ñ Github." + }, + "censorship-4": { + "id": "#ÑÐµÐœÐ·ÑÑÐ°-4", + "control": "ÑÐµÐœÐ·ÑÑÐ°-4", + "title": "Ð¯ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð¿ÑÐŽÐºÐ»ÑÑÐžÑÐžÑÑ ÐŽÐŸ Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor, ÑÐž ÐŒÐŸÑ ÐŒÐµÑÐµÐ¶Ð° Ð¿ÑÐŽÐŽÐ°ÑÑÑÑÑ ÑÐµÐœÐ·ÑÑÑ?", + "description": "<p class=\"mb-3\">ÐÐž ÐŒÐŸÐ¶ÐµÑÐµ Ð±ÑÑÐž Ñ ÐŒÐµÑÐµÐ¶Ñ, ÑÐŸ ÑÐµÐœÐ·ÑÑÑÑÑÑ, Ñ ÑÐŸÐŒÑ Ð²Ðž Ð¿ÐŸÐ²ÐžÐœÐœÑ ÑÐ¿ÑÐŸÐ±ÑÐ²Ð°ÑÐž Ð²ÐžÐºÐŸÑÐžÑÑÐŸÐ²ÑÐ²Ð°ÑÐž ÐŒÐŸÑÑÐž. ÐÐµÑÐºÑ ÐŒÐŸÑÑÐž Ð²Ð±ÑÐŽÐŸÐ²Ð°ÐœÑ Ñ Ð±ÑÐ°ÑÐ·ÐµÑ Tor, Ñ Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐºÐŸÑÐžÑÑÐŸÐ²ÑÐ²Ð°ÑÐž ÑÑ ÐŒÐŸÑÑÐž, Ð²ÐžÐ±ÑÐ°Ð²ÑÐž \"ÐœÐ°Ð»Ð°ÑÑÑÐ²Ð°ÑÐž\" (Ð° Ð¿ÐŸÑÑÐŒ ÑÐ»ÑÐŽÑÐ²Ð°ÑÐž Ð¿ÑÐŽÐºÐ°Ð·ÐºÐ°ÐŒ) Ñ Ð²ÑÐºÐœÑ Ð·Ð°Ð¿ÑÑÐºÑ Tor, ÑÐŸ Ð·'ÑÐ²ÐžÑÑÑÑ Ð¿ÑÐŽ ÑÐ°Ñ Ð²ÑÐŽÐºÑÐžÑÑÑ Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor Ð²Ð¿ÐµÑÑÐµ. Ð¯ÐºÑÐŸ Ð²Ð°ÐŒ Ð¿ÐŸÑÑÑÐ±ÐœÑ ÑÐœÑÑ ÐŒÐŸÑÑÐž, Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐžÐŒÐ°ÑÐž ÑÑ ÐœÐ° ÐœÐ°ÑÐŸÐŒÑ <mark><a href=\"https://bridges.torproject.org/\">Ð¡Ð°Ð¹ÑÑ ÐŒÐŸÑÑÑÐ²</a></mark>. Ð©ÐŸÐ± ÐŸÑÑÐžÐŒÐ°ÑÐž ÐŽÐŸÐŽÐ°ÑÐºÐŸÐ²Ñ Ð²ÑÐŽÐŸÐŒÐŸÑÑÑ Ð¿ÑÐŸ ÐŒÐŸÑÑÐž, Ð¿ÐµÑÐµÐ³Ð»ÑÐœÑÑÐµ <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Ð¿ÐŸÑÑÐ±ÐœÐžÐº ÐºÐŸÑÐžÑÑÑÐ²Ð°ÑÐ° Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor</a></m ark>.</p>" + }, + "censorship-5": { + "id": "#ÑÐµÐœÐ·ÑÑÐ°-5", + "control": "ÑÐµÐœÐ·ÑÑÐ°-5", + "title": "Ð£ ÐŒÐµÐœÐµ Ð²ÐžÐœÐžÐºÐ»Ð° Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐ° Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ ÐŽÐŸ Tor, Ñ Ñ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð·ÑÐŸÐ·ÑÐŒÑÑÐž, ÑÐŸ ÐœÐµ ÑÐ°Ðº.", + "description": "<p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð²Ð°Ñ Ð²ÐžÐœÐžÐºÐ»Ðž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÐž Ð· Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÐœÐœÑÐŒ, Ð²ÐžÐ±ÐµÑÑÑÑ ÐŸÐ¿ÑÑÑ Â«ÐºÐŸÐ¿ÑÑÐ²Ð°ÑÐž Ð¶ÑÑÐœÐ°Ð» Tor Ñ Ð±ÑÑÐµÑ ÐŸÐ±ÐŒÑÐœÑÂ». ÐÐŸÑÑÐŒ Ð²ÑÑÐ°Ð²ÑÐµ Ð¶ÑÑÐœÐ°Ð» Tor Ñ ÑÐµÐºÑÑÐŸÐ²ÐžÐ¹ ÑÐ°Ð¹Ð» Ð°Ð±ÐŸ ÑÐœÑÐžÐ¹ ÐŽÐŸÐºÑÐŒÐµÐœÑ. ÐÐž ÐŒÐ°ÑÑÐµ Ð¿ÐŸÐ±Ð°ÑÐžÑÐž ÐŸÐŽÐœÑ Ð· ÑÐžÑ Ð¿ÐŸÐŒÐžÐ»ÐŸÐº Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ (ÑÑÐºÐ°Ð¹ÑÐµ ÐœÐ°ÑÑÑÐ¿ÐœÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor):</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â1: ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·'ÑÐŽÐœÐ°ÐœÐœÑ Ð· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐŸÐŒ</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"g eneral SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p> <p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ðž ÐœÐµ ÐŒÐŸÐ¶ÐµÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS. Ð¯ÐºÑÐŸ ÐŽÐ»Ñ ÐœÐ°Ð»Ð°ÑÑÑÐ²Ð°ÐœÐœÑ ÐŒÐµÑÐµÐ¶Ñ Ð¿ÐŸÑÑÑÐ±ÐµÐœ Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑ SOCKS, Ð±ÑÐŽÑ Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ðž Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐŸ Ð²Ð²ÐµÐ»Ðž ÑÐœÑÐŸÑÐŒÐ°ÑÑÑ Ð¿ÑÐŸ Ð¿ÑÐŸÐºÑÑ. Ð¯ÐºÑÐŸ Ð¿ÑÐŸÐºÑÑ SOCKS ÐœÐµ Ð¿ÐŸÑÑÑÐ±ÐœÐžÐ¹, Ð°Ð±ÐŸ Ð²Ðž ÐœÐµ Ð²Ð¿ÐµÐ²ÐœÐµÐœÑ, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ ÐŒÐµÑÐµÐ¶Ñ Tor Ð±ÐµÐ· Ð¿ÑÐŸÐºÑÑ-ÑÐµÑÐ²ÐµÑÐ° SOCKS.<p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â2: ÐÐµ Ð²ÐŽÐ°ÑÑÑÑÑ Ð ŽÑÑÑÐ°ÑÐžÑÑ Ð±ÐµÐ·Ð¿ÐµÑÐœÐžÑ Ð¿ÐµÑÐµÐŽÐ°Ð²Ð°ÑÑÐ²</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ñ Ð¶ÑÑÐœÐ°Ð»Ñ Tor Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž, ÑÐŸ ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°ÑÐŸÐŒÑ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð¿ÑÐŽ'ÑÐŽÐœÐ°ÑÐžÑÑ ÐŽÐŸ Ð¿ÐµÑÑÐŸÐ³ÐŸ Ð²ÑÐ·Ð»Ð° Ð² Ð»Ð°ÐœÑÑÐ·Ñ Tor. ÐŠÐµ ÐŒÐŸÐ¶Ðµ ÐŸÐ·ÐœÐ°ÑÐ°ÑÐž, ÑÐŸ Ð²Ðž Ð¿ÐµÑÐµÐ±ÑÐ²Ð°ÑÑÐµ Ñ ÐŒÐµÑÐµÐ¶Ñ, ÑÐºÐ° Ð¿ÑÐŽÐŽÐ°ÑÑÑÑÑ ÑÐµÐœÐ·ÑÑÑ. ÐÑÐŽÑ Ð»Ð°ÑÐºÐ°, ÑÐ¿ÑÐŸÐ±ÑÐ¹ÑÐµ Ð¿ÑÐŽÐºÐ»ÑÑÐžÑÐžÑÑ ÐŽÐŸ ÐŒÐŸÑ ÑÑÐ², Ñ ÑÐµ ÐŒÐ°Ñ Ð²ÐžÑÑÑÐžÑÐž Ð¿ÑÐŸÐ±Ð»ÐµÐŒÑ.</p><h5>ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â3: ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð·Ð°Ð²ÐµÑÑÐžÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Tor ÐœÐµ Ð²ÐŽÐ°Ð»ÐŸÑÑ Ð²ÐžÐºÐŸÐœÐ°ÑÐž ÑÑÐºÐŸÑÑÐžÑÐºÐ°ÐœÐœÑ TLS Ð·Ð° ÐŽÐŸÐ¿ÐŸÐŒÐŸÐ³ÐŸÑ ÑÐ»ÑÐ¶Ð± ÐºÐ°ÑÐ°Ð»ÐŸÐ³Ñ. ÐÐžÐºÐŸÑÐžÑÑÐ°ÐœÐœÑ ÐŒÐŸÑÑÑÐ², ÑÐ²ÐžÐŽÑÐµ Ð·Ð° Ð²ÑÐµ, Ð±ÑÐŽÐµ Ð²ÐžÐ¿ÑÐ°Ð²Ð»ÑÑÐž ÑÐµ.</p><h5> ÐÐŸÐŒÐžÐ»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑÐœÐŸÐ³ÐŸ Ð¶ÑÑÐœÐ°Ð»Ñ â4: Ð·Ð±ÐžÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑÐŸ Ð²Ðž Ð±Ð°ÑÐžÑÐµ ÑÐ°ÐºÑ ÑÑÐŽÐºÐž Ð² Ð¶ÑÑÐœÐ°Ð»Ñ Tor, ÑÐµ ÐŸÐ·ÐœÐ°ÑÐ°Ñ, ÑÐŸ Ð²Ð°Ñ ÑÐžÑÑÐµÐŒÐœÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº ÐœÐµÐ¿Ñ Ð°Ð²ÐžÐ»ÑÐœÐžÐ¹. ÐÑÐŽÑ-Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑÐµÐºÐŸÐœÐ°Ð¹ÑÐµÑÑ, ÑÐŸ Ð²Ð°ÑÐžÐ¹ Ð³ÐŸÐŽÐžÐœÐœÐžÐº Ð²ÑÑÐ°ÐœÐŸÐ²Ð»ÐµÐœÐžÐ¹ ÑÐŸÑÐœÐŸ, Ð²ÐºÐ»ÑÑÐœÐŸ Ð· Ð¿ÑÐ°Ð²ÐžÐ»ÑÐœÐžÐŒ ÑÐ°ÑÐŸÐ²ÐžÐŒ Ð¿ÐŸÑÑÐŸÐŒ. ÐÐŸÑÑÐŒ Ð¿ÐµÑÐµÐ·Ð°Ð¿ÑÑÑÑÑÑ Tor.</p>" + }, + "censorship-6": { + "id": "#ÑÐµÐœÐ·ÑÑÐ°-6", + "control": "ÑÐµÐœÐ·ÑÑÐ°-6", + "title": "Ð¯ ÐœÐµ ÐŒÐŸÐ¶Ñ Ð¿ÑÐŽÐºÐ»ÑÑÐžÑÐžÑÑ ÐŽÐŸ Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor, ÑÐž ÐŒÐŸÑ ÐŒÐµÑÐµÐ¶Ð° Ð¿ÑÐŽÐŽÐ°ÑÑÑÑÑ ÑÐµÐœÐ·ÑÑÑ?", + "description": "<p class=\"mb-3\">ÐÐž ÐŒÐŸÐ¶ÐµÑÐµ Ð±ÑÑÐž Ñ ÐŒÐµÑÐµÐ¶Ñ, ÑÐŸ ÑÐµÐœÐ·ÑÑÑÑÑÑ, Ñ ÑÐŸÐŒÑ Ð²Ðž Ð¿ÐŸÐ²ÐžÐœÐœÑ ÑÐ¿ÑÐŸÐ±ÑÐ²Ð°ÑÐž Ð²ÐžÐºÐŸÑÐžÑÑÐŸÐ²ÑÐ²Ð°ÑÐž ÐŒÐŸÑÑÐž. ÐÐµÑÐºÑ ÐŒÐŸÑÑÐž Ð²Ð±ÑÐŽÐŸÐ²Ð°ÐœÑ Ñ Ð±ÑÐ°ÑÐ·ÐµÑ Tor, Ñ Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ Ð²ÐžÐºÐŸÑÐžÑÑÐŸÐ²ÑÐ²Ð°ÑÐž ÑÑ ÐŒÐŸÑÑÐž, Ð²ÐžÐ±ÑÐ°Ð²ÑÐž \"ÐœÐ°Ð»Ð°ÑÑÑÐ²Ð°ÑÐž\" (Ð° Ð¿ÐŸÑÑÐŒ ÑÐ»ÑÐŽÑÐ²Ð°ÑÐž Ð¿ÑÐŽÐºÐ°Ð·ÐºÐ°ÐŒ) Ñ Ð²ÑÐºÐœÑ Ð·Ð°Ð¿ÑÑÐºÑ Tor, ÑÐŸ Ð·'ÑÐ²ÐžÑÑÑÑ Ð¿ÑÐŽ ÑÐ°Ñ Ð²ÑÐŽÐºÑÐžÑÑÑ Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor Ð²Ð¿ÐµÑÑÐµ. Ð¯ÐºÑÐŸ Ð²Ð°ÐŒ Ð¿ÐŸÑÑÑÐ±ÐœÑ ÑÐœÑÑ ÐŒÐŸÑÑÐž, Ð²Ðž ÐŒÐŸÐ¶ÐµÑÐµ ÐŸÑÑÐžÐŒÐ°ÑÐž ÑÑ ÐœÐ° ÐœÐ°ÑÐŸÐŒÑ <mark><a href=\"https://bridges.torproject.org/\">Ð¡Ð°Ð¹ÑÑ ÐŒÐŸÑÑÑÐ²</a></mark>. Ð©ÐŸÐ± ÐŸÑÑÐžÐŒÐ°ÑÐž ÐŽÐŸÐŽÐ°ÑÐºÐŸÐ²Ñ Ð²ÑÐŽÐŸÐŒÐŸÑÑÑ Ð¿ÑÐŸ ÐŒÐŸÑÑÐž, Ð¿ÐµÑÐµÐ³Ð»ÑÐœÑÑÐµ <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Ð¿ÐŸÑÑÐ±ÐœÐžÐº ÐºÐŸÑÐžÑÑÑÐ²Ð°ÑÐ° Ð±ÑÐ°ÑÐ·ÐµÑÐ° Tor</a></m ark>.</p>" + } + + +} diff --git a/ur.json b/ur.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ur.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ur_PK.json b/ur_PK.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ur_PK.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/uz.json b/uz.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/uz.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/ve.json b/ve.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ve.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/vi.json b/vi.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/vi.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/wa.json b/wa.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/wa.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/wo.json b/wo.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/wo.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/zh_CN.json b/zh_CN.json new file mode 100644 index 000000000..69f34533c --- /dev/null +++ b/zh_CN.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#å®¡æ¥-1", + "control": "å®¡æ¥-1", + "title": "æççœç«è¢«å®¡æ¥æºæå±èœäºïŒTor Browser èœåž®å©çšæ·è®¿é®æççœç«åïŒ", + "description": "<p class=\"mb-3\">Tor Browser åœç¶å¯ä»¥åž®å©äººä»¬åšçœç»åå®¡æ¥çå°åºè®¿é®è¢«å±èœççœç«ãå€§å€æ°æ¶ååªéèŠäžèœœ<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser </a></mark>å¹¶äœ¿çšå®è¿è¡æµè§å³å¯ãåšçœç»å®¡æ¥ååäž¥æ Œçå°åºïŒæä»¬è¿æäŸäºè®žå€è§é¿æªæœïŒäŸåŠ<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>ãè¯·åé<mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser çšæ·æå</a></mark>ç<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">å®¡æ¥</a></mark>ç« èä»¥è·åŸæŽå€ä¿¡æ¯ã</p>" + }, + "censorship-2": { + "id": "#å®¡æ¥-2", + "control": "å®¡æ¥-2", + "title": "ææç±ççœç«å±èœæ¥èª Tor çè®¿é®ã", + "description": "<p class=\"mb-3\">äžèœè®¿é®äœ æ³èŠççœç«çæ¯éæŸå¢ïŒæäºçœç«å±èœäº Tor å äžºä»ä»¬æ æ³åèŸšåºæ®é Tor çšæ·åæºåšäººçåºå«ãæ ¹æ®è¿å»çç»éªïŒæ³èŠè®©çœç«è§£å°æ¥èª Tor çè®¿é®æææçæ¹æ³æ¯ç±çšæ·çŽæ¥èç³»çœç«ç®¡çåãä¹è®žè¿æ ·çæ¶æ¯å°±å¯ä»¥æåïŒ<br />âåšïŒåšçš Tor Browser çæ¶ååç°äœ ççœç« xyz.com äžåè®žæ¥èª Tor çè®¿é®ïŒåžæäœ å¯ä»¥éæ°èèè¿äžªå³å®ãåšçåå°åŸå€äººéœåšäœ¿çš Tor æ¥ä¿æ€éç§åå¯¹æå®¡æ¥ïŒå±èœ Tor çåæ¶äœ ä¹å±èœäºåŒºæåœå®¶äžæ³èªç±è®¿é®äºèçœççšæ·ãéèŠéèèªå·±çè®°èåæ£äžŸèãæ³èº²é¿çœç»è·èžªçç ç©¶èåæ®éçšæ·ãè¯·ç«åšæ¯æåšçº¿éç§åçœç»èªç±çç«åºäžïŒåè®ž Tor çšæ·è®¿é® xyz.comïŒè°¢è°¢ïŒâ<br />åŠå€ïŒé¶è¡è¿ç±»æ¯èŸææççœç«ç»åžžè¿è¡å°åºèåŽçå±èœãåŠæäœ å¹³æ¶åªåšæäžªç¹å®çåœå®¶äœ¿çšä»ä»¬çæå¡ïŒä»äœäº å¶ä»åœå®¶çåºå£èç¹è¿è¡è®¿é®æ¶äœ çèŽŠå·å¯èœå°±äŒè¢«å»ç»ãåŠæ æ³è¿æ¥ onion æå¡ïŒè¯·åé <a href=\"http://127.0.0.1:5000/#onionservices-3\">æ æ³è¿æ¥ x.onionïŒ</a></p>" + }, + "censorship-3": { + "id": "#å®¡æ¥-3", + "control": "å®¡æ¥-3", + "title": "torproject.org è¢«å±èœäºïŒæä¹äžèœœ TorïŒ", + "description": "<p class=\"mb-3\">åŠææ æ³éè¿æä»¬ç<mark><a href=\"https://www.torproject.org\">çœç«</a></mark>äžèœœ TorïŒäœ å¯ä»¥éè¿ GetTor è·å TorãGetTor äŒèªåšåéäžèœœ Tor Browser ææ°çæ¬çéŸæ¥ïŒç± DropboxãGoogle DriveãGitHub çæŽéŸåå°å®¡æ¥ççœç«è¿è¡ååã</p>" + }, + "censorship-4": { + "id": "#å®¡æ¥-4", + "control": "å®¡æ¥-4", + "title": "æ æ³è¿æ¥ TorïŒæççœç»è¢«å®¡æ¥äºåïŒ", + "description": "<p class=\"mb-3\">äœ å¯èœåšäœ¿çšåå®¡æ¥ççœç»ïŒè¯·å°è¯çœæ¡¥æ¥è¿è¡åºå¯¹ãTor Browser äžåçœ®äºäžäºçœæ¡¥ïŒäœ å¯ä»¥åš Tor Browser éŠæ¬¡å¯åšæ¶åŒ¹åºç Tor Launcher çªå£äžéæ©âè®Ÿçœ®âïŒç¶åè·éæç€ºïŒæ¥å¯çšãåŠæéèŠå¶ä»çœæ¡¥ïŒæä»¬ç<mark><a href=\"https://bridges.torproject.org/\">çœæ¡¥ç«ç¹</a></mark>å¯ä»¥æäŸå®ä»¬ãå³äºçœæ¡¥çæŽå€ä¿¡æ¯è¯·åé<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser çšæ·æå</a></mark>ã</p>" + }, + "censorship-5": { + "id": "#å®¡æ¥-5", + "control": "å®¡æ¥-5", + "title": "æ æ³è¿æ¥å° TorïŒäœæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", + "description": "<p class=\"mb-3\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæ šçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§æ¥å¿éè¯¯#3: TLSæ¡æå€±èŽ¥</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor äžäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5> åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \nToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœãè¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ã</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" + }, + "censorship-6": { + "id": "#å®¡æ¥-6", + "control": "å®¡æ¥-6", + "title": "æ æ³è¿æ¥ TorïŒæççœç»è¢«å®¡æ¥äºåïŒ", + "description": "<p class=\"mb-3\">äœ å¯èœåšäœ¿çšåå®¡æ¥ççœç»ïŒè¯·å°è¯çœæ¡¥æ¥è¿è¡åºå¯¹ãTor Browser äžåçœ®äºäžäºçœæ¡¥ïŒäœ å¯ä»¥åš Tor Browser éŠæ¬¡å¯åšæ¶åŒ¹åºç Tor Launcher çªå£äžéæ©âè®Ÿçœ®âïŒç¶åè·éæç€ºïŒæ¥å¯çšãåŠæéèŠå¶ä»çœæ¡¥ïŒæä»¬ç<mark><a href=\"https://bridges.torproject.org/\">çœæ¡¥ç«ç¹</a></mark>å¯ä»¥æäŸå®ä»¬ãå³äºçœæ¡¥çæŽå€ä¿¡æ¯è¯·åé<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser çšæ·æå</a></mark>ã</p>" + } + + +} diff --git a/zh_HK.json b/zh_HK.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/zh_HK.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/zh_TW.json b/zh_TW.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/zh_TW.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +} diff --git a/zu.json b/zu.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/zu.json @@ -0,0 +1,40 @@ +{ + "censorship-1": { + "id": "#censorship-1", + "control": "censorship-1", + "title": "Our website is blocked by a censor. Can Tor Browser help users access our website?", + "description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the â<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including â<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">âTor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>" + }, + "censorship-2": { + "id": "#censorship-2", + "control": "censorship-2", + "title": "My favorite website is blocking access over Tor.", + "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>" + }, + "censorship-3": { + "id": "#censorship-3", + "control": "censorship-3", + "title": "How do I download Tor if the torproject.org is blocked?", + "description": "<p class=\"mb-3\">If you can't download Tor through our â<mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>" + }, + "censorship-4": { + "id": "#censorship-4", + "control": "censorship-4", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + }, + "censorship-5": { + "id": "#censorship-5", + "control": "censorship-5", + "title": "I am having trouble connecting to Tor, and I canât figure out whatâs wrong.", + "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to âcopy Tor log to clipboard.â Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + }, + "censorship-6": { + "id": "#censorship-6", + "control": "censorship-6", + "title": "I canât connect to Tor Browser, is my network censored?", + "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our â<mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">âTor Browser manual</a></mark>.</p>" + } + + +}

1 0

[tor/maint-0.3.3] Ship all files needed to build Tor with rust
by nickm＠torproject.org 06 Apr '18

06 Apr '18

commit 306563ac68250872791350bda1ba7a7acff5eb63 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Apr 6 16:18:11 2018 -0400 Ship all files needed to build Tor with rust Fixes bug 25732; bugfix on 0.3.3.2-alpha when strings.rs was introduced. --- changes/bug25732 | 4 ++++ src/rust/include.am | 5 ++++- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/changes/bug25732 b/changes/bug25732 new file mode 100644 index 000000000..49ffae29e --- /dev/null +++ b/changes/bug25732 @@ -0,0 +1,4 @@ + o Minor bugfixes (distribution, compilation): + - Actually include all of our Rust source in our source + distributions. (Previously, a few of the files were accidentally + omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha. diff --git a/src/rust/include.am b/src/rust/include.am index 9c4337484..7a0181e37 100644 --- a/src/rust/include.am +++ b/src/rust/include.am @@ -8,6 +8,8 @@ EXTRA_DIST +=\ src/rust/external/external.rs \ src/rust/external/lib.rs \ src/rust/protover/Cargo.toml \ + src/rust/protover/errors.rs \ + src/rust/protover/protoset.rs \ src/rust/protover/ffi.rs \ src/rust/protover/lib.rs \ src/rust/protover/protover.rs \ @@ -23,4 +25,5 @@ EXTRA_DIST +=\ src/rust/tor_rust/lib.rs \ src/rust/tor_util/Cargo.toml \ src/rust/tor_util/ffi.rs \ - src/rust/tor_util/lib.rs + src/rust/tor_util/lib.rs \ + src/rust/tor_util/strings.rs

1 0

Jump to page: