commit 4cc817bdbf99af3749a59fa5bf897e006aef6b8f
Author: Translation commit bot <[email protected]>
Date: Thu Apr 12 19:37:45 2018 +0000
Update translations for support-connecting
---
es.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/es.json b/es.json
index 33397ea76..13c454253 100644
--- a/es.json
+++ b/es.json
@@ -9,7 +9,7 @@
"id": "#connecting-2",
"control": "connecting-2",
"title": "Estoy teniendo problemas conectando a Tor, y no logro
averiguar qué es lo que está mal.",
- "description": "<p class=\"mb-3\">If youâre having trouble
connecting, please select the option to \"copy Tor log to clipboard.\" Then
paste the Tor log into a text file or other document. You should see one of
these common log errors (look for the following lines in your Tor
log):</p><h5>Common log error #1: Proxy connection failure</h5><p
class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks
listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%:
Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped
10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900
[WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general
SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable
to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n
2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect
toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server fa
ilure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in
your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS
proxy is required for your network setup, then please make sure youâve
entered your proxy details correctly. If a SOCKS proxy is not required, or
youâre not sure, please try connecting to the Tor network without a SOCKS
proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p
class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks
listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped
80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed
to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017
21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop
\n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path.
Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines
like these
in your Tor log, it means your Tor failed to connect to the first node in the
Tor circuit. This could mean that youâre on a network thatâs censored.
Please try connecting with bridges, and that should fix the
problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p
class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%:
Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN]
Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server.
(DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)
\n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17
19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL
state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]
1 connections died in state connect()ing with SSL state (No SSL
object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your
Tor log, it means that Tor
failed to complete a TLS handshake with the directory authorities. Using
bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p
class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks
listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%:
Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped
10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800
[WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems
that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is
ahead. \n Tor requires an accurate clock to work: please check your time,
timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines
like this in your Tor log, it means your system clock is incorrect. Please make
sure your clock is set accurately, including the correct timezone. Then restart
Tor. </p>"
+ "description": "Si tienes problemas para conectarte, por favor
selecciona la opción \"copiar el registro Tor al portapapeles\". Luego pega el
registro de Tor en un archivo de texto u otro documento. DeberÃas ver uno de
estos errores de registro comunes (busca las siguientes lÃneas en tu registro
Tor): Error de registro común #1: Fallo de conexión del proxy 2017-10-29
09:23:40.800[AVISO] Abriendo el localizador de Socks en 127.0.0.1:9150
2017-10-29 09:23:47.900[NOTICE] Bootstrapped 5%: Conexión al servidor de
directorio 2017-10-29 09:23:47.900[NOTICE] Bootstrapped 10%: Finalizar el
handshake con el servidor de directorio 2017-10-29 09:24:08.900[WARN] Cliente
proxy: no se puede conectar a xx..xxx..xxx..xxx.xx:xxxxx (\"fallo general del
servidor SOCKS\") 2017-10-29 09:24:08.900[WARN] Cliente proxy: no se puede
conectar a xx..xxx..xxx..xxx.xx:xxxxx (\"fallo general del servidor SOCKS\")
2017-10-29 09:24:08.900[WARN] Proxy Client: incapaz de conectar
toxx..xxx..xxx..xxx.xx:xxxxx (
\"general SOCKS server failure\") Si ves lÃneas como estas en tu registro
Tor, significa que no se está conectando a un proxy SOCKS. Si se requiere un
proxy SOCKS para la configuración de la red, asegúrate de que has introducido
los datos del proxy correctamente. Si no se requiere un proxy SOCKS, o no
estás seguro, por favor intenta conectarte a la red Tor sin un proxy SOCKS.
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] Abrir Socks oyente en 127.0.0.1:9150 11/1/2017
21:11:44 PM.300[AVISO] Bootstrapped 80%: Conexión a la red Tor 11/1/2017
21:11:44 PM.300[ADVERTENCIA] No se pudo encontrar el nodo de salto 0 de nuestro
camino. Descartar este circuito. 11/1/2017 21:11:44 PM.500[AVISO] Bootstrapped
85%: Finalizando el handshake con el primer salto 11/1/2017 21:11:45
PM.300[ADVERTENCIA] No se pudo encontrar el nodo para el salto 0 de nuestro
camino. Si ves lÃneas como estas en tu registro Tor, significa que Tor falló
al c
onectarse al primer nodo en el circuito Tor. Esto podrÃa significar que
estás en una red que está censurada. Common log error #3: Failed to complete
TLS handshake 13-11-17 19:52:24.300[NOTICE] Bootstrapped 10%: Finishing
handshake with directory server 13-11-17 19:53:49.300[WARN] Problem
bootstrapping. Atascado al 10%: Finalizando el handshake con el servidor de
directorios. (HECHO; REALIZADO; contar 10; advertencia de recomendación;
host[host] en xxx.xxx.xxx.xxx.xx:xxx) 13-11-17 19:53:49.300[ADVERTENCIA] 10 Las
conexiones han fallado: 13-11-17 19:53:49.300[WARN] 9 conexiones murieron en el
handshaking de estado (TLS) con el servidor de lectura SSLv2/v3 de estado SSL
hola A en el HANDSHAKE 13-11-17 19:53:49.300[WARN] 1 connections died in state
connect()ing with SSL state (No SSL object)Si ves lÃneas como esta en tu
registro de Tor, significa que Tor falló al completar un handshake TLS con el
servidor del directorio. El uso de puentes probablemente solucionará este
error de r
egistro común #4: Reloj sesgado 19.11.2017 00:04:47.400[NOTIFICACIÃN] Socks
de apertura oyente en 127.0.0.1:9150 19.11.2017 00:04:48.000[NOTIFICACIÃN]
Bootstrapped 5%: Conexión al servidor de directorio 19.11.2017
00:04:48.200[AVISO] Bootstrapped 10%: Finalizando el handshake con el servidor
de directorio 19.11.2017 00:04:48.800[ADVERTENCIA] Recibió una celda NETINFO
con tiempo sesgado (OR:xxx.xx.xx.xx:xxxx): Parece que nuestro reloj está
atrasado por 1 dÃa, 0 horas, 1 minuto, o que el tuyo está adelantado. Tor
necesita un reloj preciso para funcionar: por favor, comprueba sus 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. Por favor, asegúrate de
que tu reloj está ajustado con precisión, incluyendo la zona horaria
correcta. Luego reinicia Tor. \n"
},
"connecting-3": {
"id": "#connecting-3",
_______________________________________________
tor-commits mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
