[tor-commits] [translation/support-censorship] pulling translations from transifex

commit f0b627c73ebe13e1d5b9ce9f0e0d3af38bc505c8 Author: Translation commit bot translation@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@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@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@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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3E àŠŸàŠ° àŠ¬à§àŠ°àŠŸàŠ‰àŠœàŠŸàŠ° àŠ¡àŠŸàŠ‰àŠšàŠ²à§‹àŠ¡ àŠ•àŠ°àŠŸ </a></mark>àŠàŠ¬àŠ‚ àŠ€àŠŸàŠ°àŠªàŠ° àŠàŠŸàŠ¿ àŠ¬à§àŠ²àŠ• àŠ•àŠ°àŠŸ àŠžàŠŸàŠ‡àŠŸà§‡ àŠšà§‡àŠ­àŠ¿àŠ—à§‡àŠŸ àŠ•àŠ°àŠŸàŠ° àŠœàŠšà§àŠ¯ àŠ…à§àŠ¯àŠŸàŠ•à§àŠžà§‡àŠžà§‡àŠ° àŠ…àŠšà§àŠ®àŠ€àŠ¿ àŠŠà§‡àŠ¬à§‡à¥€ àŠ¯à§‡ àŠœàŠŸàŠ¯àŠŒàŠ—àŠŸàŠ¯àŠŒ àŠªà§àŠ°àŠšà§àŠ° àŠžà§‡àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª àŠ°àŠ¯àŠŒà§‡àŠ›à§‡, àŠ€àŠŸ àŠ…à§àŠ¯àŠŸàŠ•à§àŠžà§‡àŠžà§‡àŠ° àŠœàŠšà§àŠ¯ àŠ†àŠ®àŠŸàŠŠà§‡àŠ° àŠ•àŠŸàŠ›à§‡ àŠªà§àŠ°àŠšà§àŠ° àŠªàŠ°àŠ¿àŠ®àŠŸàŠ£à§‡ àŠžà§‡àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠª àŠªà§àŠ°àŠ€àŠŸàŠ°àŠ£àŠŸ àŠ¬àŠ¿àŠ•àŠ²à§à Šª àŠ†àŠ›à§‡, <mark><a href="https://www.torproject.org/docs/pluggable-transports.html.en%5C%22%3E%C3%A0%... àŠŸà§àŠ°àŠŸàŠšà§àŠžàŠªà§‹àŠ°à§àŠŸàŠ—à§àŠ²àŠ¿ àŠžàŠ¹ àŠàŠ®àŠš</a></mark>à¥€àŠ†àŠ°à§‹ àŠ€àŠ¥à§àŠ¯à§‡àŠ° àŠœàŠšà§àŠ¯, àŠŠà§‡àŠ–à§àŠš àŠŸàŠ° àŠ¬à§àŠ°àŠŸàŠ‰àŠœàŠŸàŠ° àŠ‡àŠ‰àŠœàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ²<a href="https://tb-manual.torproject.org/en-US/%5C%22%3E<mark> àŠ¬àŠ¿àŠ­àŠŸàŠ—<mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3E àŠžà§‡àŠšà§àŠžàŠ°àŠ¶àŠ¿àŠªà§‡àŠ° àŠ‰àŠªàŠ°</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%5C%22%3E àŠ“àŠ¯àŠŒà§‡àŠ¬àŠžàŠŸàŠ‡àŠŸà§‡àŠ° àŠ®àŠŸàŠ§à§àŠ¯àŠ®à§‡</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%5C%22%3E%C3%A0%C5%A0%C2%... àŠ¬à§àŠ°àŠŸàŠ‰àŠœàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ² àŠŠà§‡àŠ–à§àŠš</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%5C%22%3E%C3%A0%C5%A0%C2%... àŠ¬à§àŠ°àŠŸàŠ‰àŠœàŠŸàŠ° àŠ®à§àŠ¯àŠŸàŠšà§àŠ¯àŠŒàŠŸàŠ² àŠŠà§‡àŠ–à§àŠš</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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Elloc 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Eaustaus... Übertragungsarten</a></mark>. FÃŒr weitere Informationen dazu öffne die <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3ETor Browser-Benutzeranleitung</a></mark> im Abschnitt <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3EZensur</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%5C%22%3EIch 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%5C%22%3EWebsite</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/%5C%22%3EBr%C3%83%C5%92cken-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%5C%22%3ETor 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/%5C%22%3EBr%C3%83%C5%92cken-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%5C%22%3ETor 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3E%C3%82%C2%A1No 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%5C%22%3Esitio 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/%5C%22%3Esitio 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%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3Esitio 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%5C%22%3EManual 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%5C%22%3ETor 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%5C%22%3EPluggab... 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%5C%22%3Ecensura </a></mark> del<mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3EManual 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%5C%22%3Eno 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%5C%22%3Esitio 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3Enavigateur 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%5C%22%3Etranspo... 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%5C%22%3Ecensure</a></mark> du <mark><a href="https://tb-manual.torproject.org/fr/%5C%22%3E%C3%A2%C2%80%C2%8Bguide 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%5C%22%3Esite 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/%5C%22%3Esite 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%5C%22%3E%C3%A2%C2%80%C2%8Bg... 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/%5C%22%3Esite 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%5C%22%3E%C3%A2%C2%80%C2%8Bg... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3EBrabhs%C3%... 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%5C%22%3Ec%C3%83... iompair ionphlugáilte</a></mark>. Féach ar <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BL%C3%83%C2... Bhrabhsálaí Tor</a></mark>, go háirithe an t-alt maidir <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecinsireach...</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%5C%22%3EI 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%5C%22%3Esu%C3%83%C2%ADomh 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/%5C%22%3EDroichid</a></mark>. Féach ar <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EDroichid</a></mark>. Féach ar <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Ecsatolh... átviteleket</a></mark> is. További információkért tekintese meg a <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Böngésző Felhasználói kézikönyv</a></mark> <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecenzor%C3%...</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transport </a></mark>. Untuk info lebih lanjut, silakan baca bagian <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3ETor Browser Manual </a></mark>di bagian <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3ESaya 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%5C%22%3Esitus 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/%5C%22%3Esitus 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%5C%22%3Epetunjuk 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/%5C%22%3Esitus 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%5C%22%3Epetunjuk 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3EBrowser 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%5C%22%3Euna 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/%5C%22%3EManuale Utente del Browser Tor</a></mark>nella sezione<mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensura</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%5C%22%3ENon 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%5C%22%3Esito</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor%C3%A3%...</a></mark>を利甚しおサむトのアドレスにアクセスするだけで十分です。より厳しい怜閲がある堎合、<mark><a href="https://www.torproject.org/docs/pluggable-transports.html.en%5C%22%3EPluggab... Transport</a></mark>など様々な迂回方法がありたす。詳现に぀いおは、<mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3ETor%C3%A3%C2%83%C2%96%C3%A3%...</a></mark>に<mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3E%C3%A6%E2%...</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%5C%22%3EX.onion%C3%A3%C2%81%C2%AB%C3%...</a>を参照㠁—おください。</p>" + }, + "censorship-3": { + "id": "#怜閲-3", + "control": "怜閲-3", + "title": "torproject.orgがブロックされおいる堎合、どのようにTorをダりンロヌドできたすか", + "description": "<p class="mb-3">私たちの<mark><a href="https://www.torproject.org%5C%22%3EWEB%C3%A3%C2%82%C2%B5%C3%A3%C2%82%E2%82%A...</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/%5C%22%3E%C3%A3%C2%83%C2%96%C3%A3%C2%83%C2%AA...</a></mark>から手に入れるこずができたす。詳现に぀いおは、<mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3ETor%C3%A3%C2%83%...</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/%5C%22%3E%C3%A3%C2%83%C2%96%C3%A3%C2%83%C2%AA...</a></mark>から手に入れるこずができたす。詳现に぀いおは、<mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3ETor%C3%A3%C2%83%...</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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Elaman 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Enettside</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Einplugb... transports</a></mark>. Voor meer informatie, zie de <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E Tor Browser Gebruiker Manual</a></mark> hoofdstuk over <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EIk 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%5C%22%3Ewebsite</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/%5C%22%3EBridges-website</a></mark>.Voor meer informatie over bruggen, zie de <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E 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/%5C%22%3EBridges-website</a></mark>.Voor meer informatie over bruggen, zie de <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Esite 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ENavegador 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%5C%22%3Etranspo... 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%5C%22%3EN%C3%83%C2%A3o 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%5C%22%3E 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/%5C%22%3EBridges website </a></mark>. Para mais informações sobre bridges, veja o <a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3Emanual 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/%5C%22%3Ewebsite de Pontes</a></mark>. Para mais informações sobre pontes, veja o <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3Emanual 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor Browser</a></mark> О ОспПльзПваМОе егП Ўля перехПЎа Ма заблПкОрПваММый сайт пПзвПлОт пПлучОть ЎПступ к МеЌу. В Ќестах, гЎе существует усОлеММая цеМзура, у Мас есть ряЎ ЎПступМых ОМструЌеМтПв ПбхПЎа цеМзуры, включая <mark><a href="https://www.torproject.org/docs/pluggable-transports.html.en%5C%22%3Epluggab... transports</a></mark>. За ЎПпПлМОтельМПй ОМфПрЌацОей, пПжалуйста, ПбратОтесь к разЎелу <mark><a hre f="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3E%C3%90%C5%... цеМзуре</a></mark> в <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%91%C2%80%C3%91%C2%83%C3%... пПльзПвателя 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%5C%22%3EI 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%5C%22%3E%C3%91%C2%81%C3%90%C2%B0%C3%90%C2%B9%C3%9...</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/%5C%22%3E%C3%90%C2%B2%C3%90%C2%B5%C3%90%C2%B1..., пПсвящеММПЌ ЌПстаЌ</a></mark>. Для пПлучеМОя бПлее пПЎрПбМПй ОМфПрЌацОО П ЌПстах, сЌ. <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%91%C2%80%C3%... 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/%5C%22%3E%C3%90%C2%B2%C3%90%C2%B5%C3%90%C2%B1..., пПсвящеММПЌ ЌПстаЌ</a></mark>. Для пПлучеМОя бПлее пПЎрПбМПй ОМфПрЌацОО П ЌПстах, сЌ. <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%91%C2%80%C3%... Tor Browser</a></mark>. </p>" + } + + +} diff --git a/ru@petr1708.json b/ru@petr1708.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ru@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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... Browser manual</a></mark>.</p>" + } + + +} diff --git a/sr@latin.json b/sr@latin.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/sr@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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebbsajt</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... Browser manual</a></mark>.</p>" + } + + +} diff --git a/ug@Arab.json b/ug@Arab.json new file mode 100644 index 000000000..33c6fc15d --- /dev/null +++ b/ug@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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3EI 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/%5C%22%3E%C3%90%C2%A1%C3%90%C2%B0%C3%90%C2%B9... ЌПстів</a></mark>. ЩПб ПтрОЌатО ЎПЎаткПві віЎПЌПсті прП ЌПстО, перегляМьте <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%90%C2%BF%C3%... кПрОстувача браузера 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/%5C%22%3E%C3%90%C2%A1%C3%90%C2%B0%C3%90%C2%B9... ЌПстів</a></mark>. ЩПб ПтрОЌатО ЎПЎаткПві віЎПЌПсті прП ЌПстО, перегляМьте <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%90%C2%BF%C3%... кПрОстувача браузера 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor Browser </a></mark>并䜿甚它进行浏览即可。圚眑络审查十分䞥栌的地区我们还提䟛了讞倚规避措斜䟋劂<mark><a href="https://www.torproject.org/docs/pluggable-transports.html.en%5C%22%3Epluggab... transports</a></mark>。请参阅<mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3ETor Browser 甚户手册</a></mark>的<mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3E%C3%A5%C2%...</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%5C%22%3E%C3%A6%C2%97%C2%A0%C3%A6%C2%B... 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%5C%22%3E%C3%A7%C5%93%C2%91%C3%A7%C2%AB%C2%99</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/%5C%22%3E%C3%A7%C5%93%C2%91%C3%A6%C2%A1%C2%A5...</a></mark>可以提䟛它们。关于眑桥的曎倚信息请参阅<mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3ETor 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/%5C%22%3E%C3%A7%C5%93%C2%91%C3%A6%C2%A1%C2%A5...</a></mark>可以提䟛它们。关于眑桥的曎倚信息请参阅<mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3ETor 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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%5C%22%3ETor 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%5C%22%3Epluggab... transports</a></mark>. For more information, please see the <mark><a href="https://tb-manual.torproject.org/en-US/%5C%22%3E%C3%A2%C2%80%C2%8BTor Browser User Manual</a></mark> section on <mark><a href="https://tb-manual.torproject.org/en-US/circumvention.html%5C%22%3Ecensorship</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%5C%22%3EI 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%5C%22%3Ewebsite</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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... 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/%5C%22%3EBridges website</a></mark>. For more information about bridges, see the <mark><a href="https://tb-manual.torproject.org/en-US/bridges.html%5C%22%3E%C3%A2%C2%80%C2%... Browser manual</a></mark>.</p>" + } + + +}