[tor-commits] [translation/support-connecting] Update translations for support-connecting
translation at torproject.org
translation at torproject.org
Wed Apr 18 07:49:56 UTC 2018
commit 002874af664d6593928044adef709ee7401d784c
Author: Translation commit bot <translation at torproject.org>
Date: Wed Apr 18 07:49:54 2018 +0000
Update translations for support-connecting
---
ja.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ja.json b/ja.json
index 4a2169eb3..e1eece31b 100644
--- a/ja.json
+++ b/ja.json
@@ -9,7 +9,7 @@
"id": "#接続-2",
"control": "接続-2",
"title": "Torにアクセスできないが、何が問題なのか分かりません。",
- "description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to \"copy Tor log to clipboard.\" Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS 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": "<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: una
ble 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. Discarding 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 yo
ur time, timezone, and date settings.</code></pre></p><p class=\\\"mb-3\\\">Torログにこのような行があれば、システム・クロックには間違った時刻が設定されます。システム・クロックを正しい時刻とタイムゾーンに合わせてからTorを再起動して下さい。 </p>"
},
"connecting-3": {
"id": "#接続-3",
More information about the tor-commits
mailing list