انجمن‌های فارسی اوبونتو
کمک و پشتیبانی => سایر توزیع‌های گنو/لینوکس => دبیان => نویسنده: khalilshahr در 09 فروردین 1402، 08:29 ب‌ظ
-
سلام به همه
ببخشید من دیروز تور نصب کردم الان میخوام لاگین بگیرم ولی یچ جوابی نگرفتم اینم پیغام خطایی ک میده ...
vic@Home:~$ journalctl -exfu Tor
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
-- Journal begins at Tue 2023-03-28 01:04:56 +0330. --
-
دستور journalctl رو با sudo اجراش کن.
-
بی جوابه برادر
-
سلام
اقا من این دستور رو میزنم چیزی نشون نمیده .../
vic@Home:~$ sudo tail -f /var/log/tor/log
tail: cannot open '/var/log/tor/log' for reading: No such file or directory
tail: no files remaining
-
سلام
اقا من این دستور رو میزنم چیزی نشون نمیده .../
vic@Home:~$ sudo tail -f /var/log/tor/log
tail: cannot open '/var/log/tor/log' for reading: No such file or directory
tail: no files remaining
یه جا نوشته بود تور بخاطر امنیت و ... دیگه لاگ‌هاش رو اینجا نمی‌نویسه.
این رو امتحان کن:
sudo journalctl -exft Tor
-
سلام
اقا من این دستور رو میزنم چیزی نشون نمیده .../
vic@Home:~$ sudo tail -f /var/log/tor/log
tail: cannot open '/var/log/tor/log' for reading: No such file or directory
tail: no files remaining
یه جا نوشته بود تور بخاطر امنیت و ... دیگه لاگ‌هاش رو اینجا نمی‌نویسه.
این رو امتحان کن:
sudo journalctl -exft Tor
اینو ببنید ولی من هنوز نمیتونم یوتیوب رو باز کنم
vic@Home:~$ sudo journalctl -exft Tor
-- Journal begins at Sun 2022-08-07 17:55:10 +0430. --
Mar 28 12:03:27 Home Tor[2678]: We compiled with OpenSSL 101010ef: OpenSSL 1.1.1n 15 Mar 2022 and we are running with OpenSSL 101010ef: 1.1.1n. These two versions should be binary compatible.
Mar 28 12:03:27 Home Tor[2678]: Tor 0.4.5.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc.
Mar 28 12:03:27 Home Tor[2678]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Mar 28 12:03:27 Home Tor[2678]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Mar 28 12:03:27 Home Tor[2678]: Read configuration file "/etc/tor/torrc".
Mar 28 12:03:27 Home Tor[2678]: Opening Socks listener on 127.0.0.1:9050
Mar 28 12:03:27 Home Tor[2678]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Mar 28 12:03:27 Home Tor[2678]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Mar 28 12:03:27 Home Tor[2678]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Mar 28 12:03:27 Home Tor[2678]: Bootstrapped 0% (starting): Starting
Mar 28 12:03:27 Home Tor[2678]: Starting with guard context "default"
Mar 28 12:03:27 Home Tor[2678]: Signaled readiness to systemd
Mar 28 12:03:28 Home Tor[2678]: Opening Socks listener on /run/tor/socks
Mar 28 12:03:28 Home Tor[2678]: Opened Socks listener connection (ready) on /run/tor/socks
Mar 28 12:03:28 Home Tor[2678]: Opening Control listener on /run/tor/control
Mar 28 12:03:28 Home Tor[2678]: Opened Control listener connection (ready) on /run/tor/control
Mar 28 12:03:28 Home Tor[2678]: Bootstrapped 5% (conn): Connecting to a relay
Mar 28 12:03:29 Home Tor[2678]: Bootstrapped 10% (conn_done): Connected to a relay
Mar 28 12:03:29 Home Tor[2678]: Bootstrapped 14% (handshake): Handshaking with a relay
Mar 28 12:03:30 Home Tor[2678]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Mar 28 12:03:30 Home Tor[2678]: Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Mar 28 12:03:30 Home Tor[2678]: Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Mar 28 12:03:30 Home Tor[2678]: Bootstrapped 30% (loading_status): Loading networkstatus consensus
Mar 28 12:03:31 Home Tor[2678]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Mar 28 12:03:31 Home Tor[2678]: Bootstrapped 40% (loading_keys): Loading authority key certs
Mar 28 12:03:32 Home Tor[2678]: The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Mar 28 12:03:32 Home Tor[2678]: Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Mar 28 12:03:32 Home Tor[2678]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6781, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Mar 28 12:03:33 Home Tor[2678]: Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Mar 28 12:03:38 Home Tor[2678]: The current consensus contains exit nodes. Tor can build exit and internal paths.
Mar 28 12:03:41 Home Tor[2678]: Bootstrapped 57% (loading_descriptors): Loading relay descriptors
Mar 28 12:03:41 Home Tor[2678]: Bootstrapped 64% (loading_descriptors): Loading relay descriptors
Mar 28 12:03:41 Home Tor[2678]: Bootstrapped 69% (loading_descriptors): Loading relay descriptors
Mar 28 12:05:41 Home Tor[2678]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Mar 28 12:05:41 Home Tor[2678]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Mar 28 12:05:41 Home Tor[2678]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Mar 28 12:05:42 Home Tor[2678]: Bootstrapped 100% (done): Done
Mar 28 12:31:20 Home Tor[2678]: Interrupt: exiting cleanly.
-
پروکسی رو روی مرورگر درست تنظیم کردی؟ 127.0.0.1:9050 از نوع socks5
-
نه از کجا ؟
-
نه از کجا ؟
افزونه FoxyProxy رو نصب کن روی فایرفاکس یا SwitchyOmega اگه کرومیوم داری. اونجا یه proxy از نوع socks5 با آی‌پی 127.0.0.1 و پورت 9050 تنظیم کن. بعد هر وقت خواستی، کافیه روی افزونه بزنی روشنش کنی.
-
زدم ولی بازم جوابی نداد foxy proxy روشن هستش ولی جوابی نمیده ...
صبر کن اسکرین شات میگرم میفرستم
-
اینم تنظیمات فاکسی پراکسی اسکرین شات گرفتم ایرادی داره ممنون میشم
(https://s2.uupload.ir/files/tor_5i9n.png)
-
درسته. حالا قبل از رفتن به یوتیوب، روی افزونه بزن و tor رو انتخاب کن که فعال بشه. همچنان کار نمیکنه؟
-
نه اینو میگه ...
The proxy server is refusing connections
اونجا یوزر پسس میخواد نباید چیزی بزنم
-
نه اینو میگه ...
The proxy server is refusing connections
اونجا یوزر پسس میخواد نباید چیزی بزنم
به نظر torت متوقف شده (طبق خط آخر لاگ که بالاتر فرستادی می‌گم).
بزن
sudo systemctl restart tor.serviceو دوباره صبر کن تا ۱۰۰ بره. بعد ببین باز میکنه؟
-
دوست عزیز اینو زدم چند دقیقه هم صبر کردم ولی سریع میره روی ۱۰۰٪ به نظرت تور مشکلی داره در ضمن ن سرویس proxy chain هم فعال کردم ایا این مختل میکنه
خروجی ها رو خودت ببین ...
-
دوست عزیز اینو زدم چند دقیقه هم صبر کردم ولی سریع میره روی ۱۰۰٪ به نظرت تور مشکلی داره در ضمن ن سرویس proxy chain هم فعال کردم ایا این مختل میکنه
خروجی ها رو خودت ببین ...
vic@Home:~$ sudo systemctl restart tor.service
vic@Home:~$ sudo journalctl -exft Tor
-- Journal begins at Sun 2022-08-07 17:55:10 +0430. --
Mar 28 12:03:27 Home Tor[2678]: We compiled with OpenSSL 101010ef: OpenSSL 1.1.1n 15 Mar 2022 and we are running with OpenSSL 101010ef: 1.1.1n. These two versions should be binary compatible.
Mar 28 12:03:27 Home Tor[2678]: Tor 0.4.5.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc.
Mar 28 12:03:27 Home Tor[2678]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Mar 28 12:03:27 Home Tor[2678]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Mar 28 12:03:27 Home Tor[2678]: Read configuration file "/etc/tor/torrc".
Mar 28 12:03:27 Home Tor[2678]: Opening Socks listener on 127.0.0.1:9050
Mar 28 12:03:27 Home Tor[2678]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Mar 28 12:03:27 Home Tor[2678]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Mar 28 12:03:27 Home Tor[2678]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Mar 28 12:03:27 Home Tor[2678]: Bootstrapped 0% (starting): Starting
Mar 28 12:03:27 Home Tor[2678]: Starting with guard context "default"
Mar 28 12:03:27 Home Tor[2678]: Signaled readiness to systemd
Mar 28 12:03:28 Home Tor[2678]: Opening Socks listener on /run/tor/socks
Mar 28 12:03:28 Home Tor[2678]: Opened Socks listener connection (ready) on /run/tor/socks
Mar 28 12:03:28 Home Tor[2678]: Opening Control listener on /run/tor/control
Mar 28 12:03:28 Home Tor[2678]: Opened Control listener connection (ready) on /run/tor/control
Mar 28 12:03:28 Home Tor[2678]: Bootstrapped 5% (conn): Connecting to a relay
Mar 28 12:03:29 Home Tor[2678]: Bootstrapped 10% (conn_done): Connected to a relay
Mar 28 12:03:29 Home Tor[2678]: Bootstrapped 14% (handshake): Handshaking with a relay
Mar 28 12:03:30 Home Tor[2678]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Mar 28 12:03:30 Home Tor[2678]: Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Mar 28 12:03:30 Home Tor[2678]: Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Mar 28 12:03:30 Home Tor[2678]: Bootstrapped 30% (loading_status): Loading networkstatus consensus
Mar 28 12:03:31 Home Tor[2678]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Mar 28 12:03:31 Home Tor[2678]: Bootstrapped 40% (loading_keys): Loading authority key certs
Mar 28 12:03:32 Home Tor[2678]: The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Mar 28 12:03:32 Home Tor[2678]: Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Mar 28 12:03:32 Home Tor[2678]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6781, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Mar 28 12:03:33 Home Tor[2678]: Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Mar 28 12:03:38 Home Tor[2678]: The current consensus contains exit nodes. Tor can build exit and internal paths.
Mar 28 12:03:41 Home Tor[2678]: Bootstrapped 57% (loading_descriptors): Loading relay descriptors
Mar 28 12:03:41 Home Tor[2678]: Bootstrapped 64% (loading_descriptors): Loading relay descriptors
Mar 28 12:03:41 Home Tor[2678]: Bootstrapped 69% (loading_descriptors): Loading relay descriptors
Mar 28 12:05:41 Home Tor[2678]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Mar 28 12:05:41 Home Tor[2678]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Mar 28 12:05:41 Home Tor[2678]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Mar 28 12:05:42 Home Tor[2678]: Bootstrapped 100% (done): Done
Mar 28 12:31:20 Home Tor[2678]: Interrupt: exiting cleanly.
-
راستش اون proxy chains که گفتی رو نمی‌دونم چیه تا حالا باهاش کار نکردم.
ولی یه چیزی که متوجه شدم اینه که این لاگ‌های الان نیست 🤔 چون امروز ۱ آپریله.
خروجی این رو بذار:
sudo systemctl status tor.service
-
شما درست گفتین خیلی چیزها درست کار نمیکنه
vic@Home:~$ sudo systemctl status tor.service
● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: e>
Active: failed (Result: exit-code) since Sat 2023-04-01 00:37:49 +0330; 5m>
Process: 7641 ExecStart=/usr/bin/tor -f /etc/tor/torrc (code=exited, status>
Main PID: 7641 (code=exited, status=1/FAILURE)
CPU: 15ms
Apr 01 00:37:49 Home systemd[1]: Started Anonymizing overlay network for TCP (m>
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.093 [notice] Tor 0.4.5.16 runni>
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.093 [notice] Tor can't help you>
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.094 [notice] Read configuration>
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.096 [warn] '"CERT"' is not a k=>
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.096 [warn] 'CERT' is not a k=v >
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.096 [warn] Failed to parse/vali>
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.096 [err] Reading config failed>
Apr 01 00:37:49 Home systemd[1]: tor.service: Main process exited, code=exited,>
Apr 01 00:37:49 Home systemd[1]: tor.service: Failed with result 'exit-code'.
lines 1-17/17 (END)...skipping...
● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2023-04-01 00:37:49 +0330; 5min ago
Process: 7641 ExecStart=/usr/bin/tor -f /etc/tor/torrc (code=exited, status=1/FAILURE)
Main PID: 7641 (code=exited, status=1/FAILURE)
CPU: 15ms
Apr 01 00:37:49 Home systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.093 [notice] Tor 0.4.5.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc>
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.093 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.094 [notice] Read configuration file "/etc/tor/torrc".
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.096 [warn] '"CERT"' is not a k=v value.
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.096 [warn] 'CERT' is not a k=v item.
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.096 [warn] Failed to parse/validate config: Bridge line did not parse. See logs for details.
Apr 01 00:37:49 Home tor[7641]: Apr 01 00:37:49.096 [err] Reading config failed--see warnings above.
Apr 01 00:37:49 Home systemd[1]: tor.service: Main process exited, code=exited, status=1/FAILURE
Apr 01 00:37:49 Home systemd[1]: tor.service: Failed with result 'exit-code'.
-
به نظر محتویات torrc مشکل داره. اینجا می‌ذاریش؟
-
کد دستوریش رو لطف میکنی بگی ببخشید
-
کد دستوریش رو لطف میکنی بگی ببخشید
cat /etc/tor/torrc
-
اینم خروجی
vic@Home:~$ cat /etc/tor/torrc
## Configuration file for a typical Tor user
## Last updated 9 October 2013 for Tor 0.2.5.2-alpha.
## (may or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
## https://www.torproject.org/docs/faq#torrc
## Tor opens a socks proxy on port 9050 by default -- even if you don't
## configure one below. Set "SocksPort 0" if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
#SocksPort 9050 # Default: Bind to localhost:9050 for local connections.
#SocksPort 192.168.0.1:9100 # Bind to this address:port too.
## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests that reach a SocksPort. Untrusted users who
## can access your SocksPort may be able to learn about the connections
## you make.
#SocksPolicy accept 192.168.0.0/16
#SocksPolicy reject *
## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr
## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1
## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory /var/lib/tor
## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
#CookieAuthentication 1
############### This section is just for location-hidden services ###
## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.
#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22
################ This section is just for relays #####################
#
## See https://www.torproject.org/docs/tor-doc-relay for details.
## Required: what port to advertise for incoming Tor connections.
#ORPort 9001
## If you want to listen on a port other than the one advertised in
## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## follows. You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORPort 443 NoListen
#ORPort 127.0.0.1:9090 NoAdvertise
## The IP address or full DNS name for incoming connections to your
## relay. Leave commented out and Tor will guess.
#Address noname.example.com
## If you have multiple network interfaces, you can specify one for
## outgoing traffic to use.
# OutboundBindAddress 10.0.0.5
## A handle for your relay, so people don't have to refer to it by key.
#Nickname ididnteditheconfig
## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 KB.
## Note that units for these config options are bytes per second, not bits
## per second, and that prefixes are binary prefixes, i.e. 2^10, 2^20, etc.
#RelayBandwidthRate 100 KB # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)
## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies separately to sent and received bytes,
## not to their sum: setting "4 GB" may allow up to 8 GB total before
## hibernating.
##
## Set a maximum of 4 gigabytes each way per period.
#AccountingMax 4 GB
## Each period starts daily at midnight (AccountingMax is per day)
#AccountingStart day 00:00
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
## is per month)
#AccountingStart month 3 15:00
## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it's an email address and/or generate a new address for this purpose.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>
## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth.
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised in
## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
## follows. below too. You'll need to do ipchains or other port
## forwarding yourself to make this work.
#DirPort 80 NoListen
#DirPort 127.0.0.1:9091 NoAdvertise
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
## can explain what Tor is if anybody wonders why your IP address is
## contacting them. See contrib/tor-exit-notice.html in Tor's source
## distribution for a sample.
#DirPortFrontPage /etc/tor/tor-exit-notice.html
## Uncomment this if you run more than one Tor relay, and add the identity
## key fingerprint of each Tor relay you control, even if they're on
## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See
## https://www.torproject.org/docs/faq#MultipleRelays
## However, you should never include a bridge's fingerprint here, as it would
## break its concealability and potentionally reveal its IP/TCP address.
#MyFamily $keyid,$keyid,...
## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to _replace_
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you're _augmenting_ (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## described in the man page or at
## https://www.torproject.org/documentation.html
##
## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
## For security, by default Tor rejects connections to private (local)
## networks, including to your public IP address. See the man page entry
## for ExitPolicyRejectPrivate if you want to allow "exit enclaving".
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
#ExitPolicy reject *:* # no exits allowed
## Bridge relays (or "bridges") are Tor relays that aren't listed in the
## main directory. Since there is no complete public list of them, even an
## ISP that filters connections to all the known Tor relays probably
## won't be able to block all the bridges. Also, websites won't treat you
## differently because they won't know you're running Tor. If you can
## be a real relay, please do; but if not, be a bridge!
#BridgeRelay 1
## By default, Tor will advertise your bridge to users through various
## mechanisms like https://bridges.torproject.org/. If you want to run
## a private bridge, for example because you'll give out your bridge
## address manually to your friends, uncomment this line:
#PublishServerDescriptor 0
UseBridges 1
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy
Bridge obfs4 51.83.226.5:17695 D176FAD5D0BF2D8925D124CDE9724786578DC7Bf=eI2LmCk34doTw28vDamKzCGhCDQb5wiJJVHPzLbExVDNWCVLBFN=JWHPzLbHb5WiJWHLbHb5WiJWHLbHbHb5WHPWHlbHb5WiJVCVCVDC
bridge OBFS4 213.29.63.159:65534 92DABE8C0A6D898F2A47EA9DD788BFB70A1632F6 CERT = AKU6ZUSUYVEINZY0F2K2U5ZN7C1TRKDSZZVHMR44IRLS9X8RFKIRFKIRFKIRFKIRFKIRFKIRFKIRFKIRFICKY29
Bridge obfs4 155.4.51.253:3785 9E81FCC60A80EEE86BB0A9104E625A3AE21B70Fa=qjlBttxgA12J0zFMHMpToUpkLyrIcaxilNkzPyH00+iCaxilNkjPw4+icaxilNkjPyAn
-
اینم خروجی
vic@Home:~$ cat /etc/tor/torrc
## Configuration file for a typical Tor user
## Last updated 9 October 2013 for Tor 0.2.5.2-alpha.
## (may or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
## https://www.torproject.org/docs/faq#torrc
## Tor opens a socks proxy on port 9050 by default -- even if you don't
## configure one below. Set "SocksPort 0" if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
#SocksPort 9050 # Default: Bind to localhost:9050 for local connections.
#SocksPort 192.168.0.1:9100 # Bind to this address:port too.
## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests that reach a SocksPort. Untrusted users who
## can access your SocksPort may be able to learn about the connections
## you make.
#SocksPolicy accept 192.168.0.0/16
#SocksPolicy reject *
## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr
## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1
## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory /var/lib/tor
## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
#CookieAuthentication 1
############### This section is just for location-hidden services ###
## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.
#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22
################ This section is just for relays #####################
#
## See https://www.torproject.org/docs/tor-doc-relay for details.
## Required: what port to advertise for incoming Tor connections.
#ORPort 9001
## If you want to listen on a port other than the one advertised in
## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## follows. You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORPort 443 NoListen
#ORPort 127.0.0.1:9090 NoAdvertise
## The IP address or full DNS name for incoming connections to your
## relay. Leave commented out and Tor will guess.
#Address noname.example.com
## If you have multiple network interfaces, you can specify one for
## outgoing traffic to use.
# OutboundBindAddress 10.0.0.5
## A handle for your relay, so people don't have to refer to it by key.
#Nickname ididnteditheconfig
## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 KB.
## Note that units for these config options are bytes per second, not bits
## per second, and that prefixes are binary prefixes, i.e. 2^10, 2^20, etc.
#RelayBandwidthRate 100 KB # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)
## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies separately to sent and received bytes,
## not to their sum: setting "4 GB" may allow up to 8 GB total before
## hibernating.
##
## Set a maximum of 4 gigabytes each way per period.
#AccountingMax 4 GB
## Each period starts daily at midnight (AccountingMax is per day)
#AccountingStart day 00:00
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
## is per month)
#AccountingStart month 3 15:00
## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it's an email address and/or generate a new address for this purpose.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>
## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth.
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised in
## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
## follows. below too. You'll need to do ipchains or other port
## forwarding yourself to make this work.
#DirPort 80 NoListen
#DirPort 127.0.0.1:9091 NoAdvertise
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
## can explain what Tor is if anybody wonders why your IP address is
## contacting them. See contrib/tor-exit-notice.html in Tor's source
## distribution for a sample.
#DirPortFrontPage /etc/tor/tor-exit-notice.html
## Uncomment this if you run more than one Tor relay, and add the identity
## key fingerprint of each Tor relay you control, even if they're on
## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See
## https://www.torproject.org/docs/faq#MultipleRelays
## However, you should never include a bridge's fingerprint here, as it would
## break its concealability and potentionally reveal its IP/TCP address.
#MyFamily $keyid,$keyid,...
## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to _replace_
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you're _augmenting_ (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## described in the man page or at
## https://www.torproject.org/documentation.html
##
## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
## For security, by default Tor rejects connections to private (local)
## networks, including to your public IP address. See the man page entry
## for ExitPolicyRejectPrivate if you want to allow "exit enclaving".
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
#ExitPolicy reject *:* # no exits allowed
## Bridge relays (or "bridges") are Tor relays that aren't listed in the
## main directory. Since there is no complete public list of them, even an
## ISP that filters connections to all the known Tor relays probably
## won't be able to block all the bridges. Also, websites won't treat you
## differently because they won't know you're running Tor. If you can
## be a real relay, please do; but if not, be a bridge!
#BridgeRelay 1
## By default, Tor will advertise your bridge to users through various
## mechanisms like https://bridges.torproject.org/. If you want to run
## a private bridge, for example because you'll give out your bridge
## address manually to your friends, uncomment this line:
#PublishServerDescriptor 0
UseBridges 1
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy
Bridge obfs4 51.83.226.5:17695 D176FAD5D0BF2D8925D124CDE9724786578DC7Bf=eI2LmCk34doTw28vDamKzCGhCDQb5wiJJVHPzLbExVDNWCVLBFN=JWHPzLbHb5WiJWHLbHb5WiJWHLbHbHb5WHPWHlbHb5WiJVCVCVDC
bridge OBFS4 213.29.63.159:65534 92DABE8C0A6D898F2A47EA9DD788BFB70A1632F6 CERT = AKU6ZUSUYVEINZY0F2K2U5ZN7C1TRKDSZZVHMR44IRLS9X8RFKIRFKIRFKIRFKIRFKIRFKIRFKIRFKIRFICKY29
Bridge obfs4 155.4.51.253:3785 9E81FCC60A80EEE86BB0A9104E625A3AE21B70Fa=qjlBttxgA12J0zFMHMpToUpkLyrIcaxilNkzPyH00+iCaxilNkjPw4+icaxilNkjPyAn
اون سه‌تا پل که اضافه کردی، دومیش ایراد داره. وسطش کلمه CERT و بعدش هم فاصله داره که نباید باشه. حروف OBFS هم بزرگ نوشته شده. به نظرم اول اون خط یه # بذار یا کلا پل رو پاک کن. راستی بعد از هر کلمه Bridge هم یه فاصله اضافه خورده. نمی‌دونم به این حساسه یا نه ولی اینم درستش کنی بهتره.
-
اقا درستش کردم ولی بازم نشد ...
کلا برداشتم ولی بازم نشد بعدش کلا پل ها رو هم برداشتم ولی بازم همون خطا رو میداد...
یه سوال کلا تور رو حذف کنم ...
چیزی هستش که جایگزین کنم
-
اقا درستش کردم ولی بازم نشد ...
کلا برداشتم ولی بازم نشد بعدش کلا پل ها رو هم برداشتم ولی بازم همون خطا رو میداد...
یه سوال کلا تور رو حذف کنم ...
چیزی هستش که جایگزین کنم
بعد که حذف کردی، دوباره سرویس رو restart کردی؟
-
اره کردم ...
ولی من یه اشتباهی رو تو وارد کردن پل ها انجام دادم این حرف CERT بودش وقتی تو جیمیل روی ترجمه میزنه این کلمه رو گواهی ترجمه میکنه و من این رو حذف کرده بودم و اینکه بعد ازbridge نباید فاصله مینداختم بعد وارد کردن پل ها خودش فاصله اعمال میکرد.
الان که گزارش گرفتم خوبه الان براتون خروجی میفرستم ببینید ...
-
اینم خروجی ولی الان بازم نمیتونم وصل بشم به یوتیوب
vic@Home:~$ sudo systemctl status tor.service
● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: ena>
Active: active (running) since Sat 2023-04-01 02:05:00 +0330; 1min 16s ago
Main PID: 10412 (tor)
Tasks: 10 (limit: 4658)
Memory: 78.1M
CPU: 1.743s
CGroup: /system.slice/tor.service
├─10412 /usr/bin/tor -f /etc/tor/torrc
└─10417 /usr/bin/obfs4proxy
Apr 01 02:05:03 Home tor[10412]: Apr 01 02:05:03.000 [notice] Bootstrapped 20% (o>
Apr 01 02:05:04 Home tor[10412]: Apr 01 02:05:04.000 [notice] Bootstrapped 25% (r>
Apr 01 02:05:04 Home tor[10412]: Apr 01 02:05:04.000 [notice] new bridge descript>
Apr 01 02:05:04 Home tor[10412]: Apr 01 02:05:04.000 [notice] new bridge descript>
Apr 01 02:05:05 Home tor[10412]: Apr 01 02:05:05.000 [notice] new bridge descript>
Apr 01 02:05:05 Home tor[10412]: Apr 01 02:05:05.000 [notice] Bootstrapped 30% (l>
Apr 01 02:05:06 Home tor[10412]: Apr 01 02:05:06.000 [notice] Bootstrapped 75% (e>
Apr 01 02:05:07 Home tor[10412]: Apr 01 02:05:07.000 [notice] Bootstrapped 90% (a>
Apr 01 02:05:07 Home tor[10412]: Apr 01 02:05:07.000 [notice] Bootstrapped 95% (c>
Apr 01 02:05:08 Home tor[10412]: Apr 01 02:05:08.000 [notice] Bootstrapped 100% (>
lines 1-21/21 (END)...skipping...
● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2023-04-01 02:05:00 +0330; 1min 16s ago
Main PID: 10412 (tor)
Tasks: 10 (limit: 4658)
Memory: 78.1M
CPU: 1.743s
CGroup: /system.slice/tor.service
├─10412 /usr/bin/tor -f /etc/tor/torrc
└─10417 /usr/bin/obfs4proxy
Apr 01 02:05:03 Home tor[10412]: Apr 01 02:05:03.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Apr 01 02:05:04 Home tor[10412]: Apr 01 02:05:04.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Apr 01 02:05:04 Home tor[10412]: Apr 01 02:05:04.000 [notice] new bridge descriptor 'ToRussiaWithTruth' (fresh): $9E81FCC60A80EEE86BB0A9104E625A3AE21B70FA~ToRussiaWithTruth [flSXqftw9DMFh>
Apr 01 02:05:04 Home tor[10412]: Apr 01 02:05:04.000 [notice] new bridge descriptor 'roberto' (fresh): $D176FAD5D0BF2D8925D124CDE9724786578DC7BF~roberto [VoxCVKcLeKyGpl3gKV+eAijOq8Dvac+DH>
Apr 01 02:05:05 Home tor[10412]: Apr 01 02:05:05.000 [notice] new bridge descriptor 'DockerObfs4Bridge' (fresh): $92DABE8C0A6D898F2A47EA9DD788BFB70A1632F6~DockerObfs4Bridge [sRHN1rY9aveXH>
Apr 01 02:05:05 Home tor[10412]: Apr 01 02:05:05.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Apr 01 02:05:06 Home tor[10412]: Apr 01 02:05:06.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Apr 01 02:05:07 Home tor[10412]: Apr 01 02:05:07.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Apr 01 02:05:07 Home tor[10412]: Apr 01 02:05:07.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Apr 01 02:05:08 Home tor[10412]: Apr 01 02:05:08.000 [notice] Bootstrapped 100% (done): Done
-
سلام مجدد اقا این پیغام رو موقعی که سیستم روشن میشد میداد الان امدم چک کردم این پیغام خطا بودش دوستان کجا رو باید درست کنم ...
اون بالایی درسته ها با همون دستور ولی این دستور رو یه دیفالت اضافه کردم نتیجه اینی هست که میبینید
● tor@default.service - Anonymizing overlay network for TCP
Loaded: loaded (/lib/systemd/system/tor@default.service; enabled-runtime; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2023-04-01 11:56:30 +0330; 13min ago
Process: 496 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d /run/tor (code=exi>
Process: 497 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /et>
Process: 499 ExecStart=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/t>
Main PID: 499 (code=exited, status=1/FAILURE)
CPU: 44ms
Apr 01 11:56:30 Home systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 5.
Apr 01 11:56:30 Home systemd[1]: Stopped Anonymizing overlay network for TCP.
Apr 01 11:56:30 Home systemd[1]: tor@default.service: Start request repeated too quickly.
Apr 01 11:56:30 Home systemd[1]: tor@default.service: Failed with result 'exit-code'.
Apr 01 11:56:30 Home systemd[1]: Failed to start Anonymizing overlay network for TCP.
-
سعی کنید سرویس tor رو راه‌اندازی مجدد کنید و ببینید چی میشه
sudo systemctl restart tor
-
سلام
جناب درستش کردم البته تور رو نصب کردم بعدش فاکسی پراکسی رو هم نصب کردم بعدش مرورگر تور رو دان کردم و بعد تو پوشه مرورگر یه فایل بود به نام فایرفاکس اونو با ترمینال اجرا کردم و بعدش فاکسی پراکسی رو که ساخته بودم فعال کردم الان مشکلی ندارم حتی یوتیوب و سایت های دیگه هم باز میشه تک تک دارک وب هم باز میکنه ...