Opened 9 months ago

Closed 9 months ago

#29154 closed defect (not a bug)

My tor does not work anymore!

Reported by: killerbee Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi everyone,
yesterday I noticed that my tor differently from the past does not seem to work anymore. Tor says it's connected correctly, but my IP address continues to be the same before the connection to the circuit.

I link the screenshots below, and my torrc file configuration with the hope that you can help me.

Tor issue: https://ibb.co/k1prs2J

Packages version: https://ibb.co/PF37Ps1

Tor folder: https://ibb.co/nfxkZ3n

My torrc file: https://textuploader.com/1avt1

Thanks in advance!
Mike

Child Tickets

Change History (12)

comment:1 Changed 9 months ago by killerbee

I was forgetting: I use Ubuntu 16.04.5 LTS

Mike

comment:2 Changed 9 months ago by teor

Component: - Select a componentCore Tor/Tor
Milestone: Tor: unspecified

Hi, thabks for this bug report.

It looks like tor might already be running.

I can't read the images you sent very well. Can you copy and paste the texf of the tor log?
Can you tell us how you're using Tor, and how you know your IP address hasn't changed?

comment:3 Changed 9 months ago by killerbee

Hi, I use tor in shell mode.
I use this site: check.torproject.org or curl ifconfig.me host to check my IP Address.

I paste below the content of the screenshot (I don't know if exists a tor log and where find it):

-- TOR ISSUE --

mike@dev:~$ curl ifconfig.me

xx.104.95.86mike@dev:~$ tor &

[1] 20007

mike@dev:~$ Jan 24 09:45:46.031 [notice] Tor 0.2.9.14 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g and Zlib 1.2.8.

Jan 24 09:45:46.031 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning

Jan 24 09:45:46.031 [notice] Read configuration file "/etc/tor/torrc".

Jan 24 09:45:46.035 [notice] Opening Socks listener on 127.0.0.1:9050

Jan 24 09:45:46.035 [warn] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?

Jan 24 09:45:46.035 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.

Jan 24 09:45:46.035 [err] Reading config failed--see warnings above.

^C

[1]+ Uscita 1 tor

mike@dev:~$ curl ifconfig.me

xx.104.95.86mike@dev:~$ ports | grep 'tor'

[sudo] password di mike:

LISTEN 0 128 127.0.0.1:9050 *:* users:(("tor",pid=19947,fd=6))

mike@dev:~$ sudo killall tor

mike@dev:~$ ports | grep 'tor'

mike@dev:~$

mike@dev:~$ tor &

[1] 20026

mike@dev:~$ Jan 24 09:46:32.018 [notice] Tor 0.2.9.14 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g and Zlib 1.2.8.

Jan 24 09:46:32.018 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning

Jan 24 09:46:32.018 [notice] Read configuration file "/etc/tor/torrc".

Jan 24 09:46:32.022 [notice] Opening Socks listener on 127.0.0.1:9050

Jan 24 09:46:32.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.

Jan 24 09:46:32.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.

Jan 24 09:46:32.000 [notice] Bootstrapped 0%: Starting

Jan 24 09:46:32.000 [notice] Bootstrapped 80%: Connecting to the Tor network

Jan 24 09:46:33.000 [notice] Bootstrapped 85%: Finishing handshake with first hop

Jan 24 09:46:33.000 [notice] Bootstrapped 90%: Establishing a Tor circuit

Jan 24 09:46:33.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.

Jan 24 09:46:33.000 [notice] Bootstrapped 100%: Done

mike@dev:~$ curl ifconfig.me

xx.104.95.86mike@dev:~$

mike@dev:~$ tor

Jan 24 09:47:16.812 [notice] Tor 0.2.9.14 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g and Zlib 1.2.8.

Jan 24 09:47:16.812 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning

Jan 24 09:47:16.812 [notice] Read configuration file "/etc/tor/torrc".

Jan 24 09:47:16.816 [notice] Opening Socks listener on 127.0.0.1:9050

Jan 24 09:47:16.816 [warn] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?

Jan 24 09:47:16.816 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.

Jan 24 09:47:16.816 [err] Reading config failed--see warnings above.

mike@dev:~$ ports | grep 'tor'

LISTEN 0 128 127.0.0.1:9050 *:* users:(("tor",pid=20026,fd=6))

mike@dev:~$ sudo killall tor

Jan 24 09:47:41.000 [notice] Catching signal TERM, exiting cleanly.

mike@dev:~$ tor

Jan 24 09:47:46.316 [notice] Tor 0.2.9.14 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g and Zlib 1.2.8.

Jan 24 09:47:46.316 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning

Jan 24 09:47:46.316 [notice] Read configuration file "/etc/tor/torrc".

Jan 24 09:47:46.319 [notice] Opening Socks listener on 127.0.0.1:9050

Jan 24 09:47:46.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.

Jan 24 09:47:46.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.

Jan 24 09:47:46.000 [notice] Bootstrapped 0%: Starting

Jan 24 09:47:46.000 [notice] Bootstrapped 80%: Connecting to the Tor network

Jan 24 09:47:47.000 [notice] Bootstrapped 85%: Finishing handshake with first hop

Jan 24 09:47:47.000 [notice] Bootstrapped 90%: Establishing a Tor circuit

Jan 24 09:47:48.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.

Jan 24 09:47:48.000 [notice] Bootstrapped 100%: Done

[IN ANOTHER TERMINAL:]

mike@dev:~$ curl ifconfig.me

xx.104.95.86

comment:4 Changed 9 months ago by killerbee

-- PACKAGES VERSION --

mike@dev:~$ openssl version -v

OpenSSL 1.0.2g 1 Mar 2016

mike@dev:~$ ldconfig -p | grep event

libtevent.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libtevent.so.0

libtevent-util.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libtevent-util.so.0

libevent-2.0.so.5 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5

mike@dev:~$ sudo apt show zlib1g

[sudo] password di mike:

Package: zlib1g

Version: 1:1.2.8.dfsg-2ubuntu4.1

Priority: required

Section: libs

Source: zlib

Origin: Ubuntu

Maintainer: Ubuntu Developers <ubuntu-devel-discuss@…>

Original-Maintainer: Mark Brown <broonie@…>

Bugs: https://bugs.launchpad.net/ubuntu/+filebug

Installed-Size: 160 kB

Provides: libz1

Depends: libc6 (>= 2.14)

Conflicts: zlib1 (<= 1:1.0.4-7)

Breaks: libxml2 (<< 2.7.6.dfsg-2), texlive-binaries (<< 2009-12)

Homepage: http://zlib.net/

Task: minimal

Supported: 5y

Download-Size: 51,2 kB

APT-Manual-Installed: yes

APT-Sources: http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages

Description: compression library - runtime

zlib is a library implementing the deflate compression method found

in gzip and PKZIP. This package includes the shared library.

N: C'è 1 record aggiuntivo: usare "-a" per visualizzarlo

-- WHAT I SEE IN TOR FOLDER --

mike@dev:~$ cd /etc/tor; ll

totale 28

drwxr-xr-x 2 root root 4096 gen 23 01:02 ./

drwxr-xr-x 150 root root 12288 gen 24 09:22 ../

-rw-r--r-- 1 root root 11176 gen 23 00:33 torrc

comment:5 Changed 9 months ago by killerbee

-- MY TORRC FILE --

## Configuration file for a typical Tor user

## Last updated 22 December 2017 for Tor 0.3.2.8-rc.

## (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 accept6 FC00::/7

#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 @LOCALSTATEDIR@/log/tor/notices.log

#Log notice file @LOCALSTATEDIR@/log/tor/notices.log

## Send every possible message to @LOCALSTATEDIR@/log/tor/debug.log

#Log debug file @LOCALSTATEDIR@/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 @LOCALSTATEDIR@/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 @LOCALSTATEDIR@/lib/tor/hidden_service/

#HiddenServicePort 80 127.0.0.1:80

#HiddenServiceDir @LOCALSTATEDIR@/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.

## OutboundBindAddressExit will be used for all exit traffic, while

## OutboundBindAddressOR will be used for all OR and Dir connections

## (DNS connections ignore OutboundBindAddress).

## If you do not wish to differentiate, use OutboundBindAddress to

## specify the same address for both in a single line.

#OutboundBindAddressExit 10.0.0.4

#OutboundBindAddressOR 10.0.0.5

## A handle for your relay, so people don't have to refer to it by key.

## Nicknames must be between 1 and 19 characters inclusive, and must

## contain only the characters [a-zA-Z0-9].

## If not set, "Unnamed" will be used.

#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 75 kilobytes per second.

## 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 KBytes # Throttle traffic to 100KB/s (800Kbps)

#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)

## 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 "40 GB" may allow up to 80 GB total before

## hibernating.

##

## Set a maximum of 40 gigabytes each way per period.

#AccountingMax 40 GBytes

## 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.

##

## If you are running multiple relays, you MUST set this option.

##

#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 @CONFDIR@/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 potentially reveal its IP/TCP address.

##

## If you are running multiple relays, you MUST set this option.

##

## Note: do not use MyFamily on bridge relays.

#MyFamily $keyid,$keyid,...

## Uncomment this if you do *not* want your relay to allow any exit traffic.

## (Relays allow exit traffic by default.)

#ExitRelay 0

## Uncomment this if you want your relay to allow IPv6 exit traffic.

## (Relays only allow IPv4 exit traffic by default.)

#IPv6Exit 1

## A comma-separated list of exit policies. They're considered first

## to last, and the first match wins.

##

## If you want to allow the same ports on IPv4 and IPv6, write your rules

## using accept/reject *. If you want to allow different ports on IPv4 and

## IPv6, write your IPv6 rules using accept6/reject6 *6, and your IPv4 rules

## using accept/reject *4.

##

## 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 the configured primary public IPv4 and IPv6 addresses,

## and any public IPv4 and IPv6 addresses on any interface on the relay.

## See the man page entry for ExitPolicyRejectPrivate if you want to allow

## "exit enclaving".

##

#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4 and IPv6 but no more

#ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well as default exit policy

#ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as default exit policy

#ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only 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!

##

## Warning: when running your Tor as a bridge, make sure than MyFamily is

## NOT configured.

#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

## Configuration options can be imported from files or folders using the %include

## option with the value being a path. If the path is a file, the options from the

## file will be parsed as if they were written where the %include option is. If

## the path is a folder, all files on that folder will be parsed following lexical

## order. Files starting with a dot are ignored. Files on subfolders are ignored.

## The %include option can be used recursively.

#%include /etc/torrc.d/

#%include /etc/torrc.custom

Thank you teor!
Mike

comment:6 Changed 9 months ago by nickm

This is the error message:

 Jan 24 09:45:46.035 [warn] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?

Something else is using port 9050 on your computer. It might be another copy of Tor? You can use the netstat to find out what is listening on what port. "netstat -tlp" will tell you the PID that is using ever current TCP listener. You might need to run it as root.

comment:7 Changed 9 months ago by killerbee

Hi nickm,

the first time I thought the same thing, it was the same tor that wal already running when I finish its command execution with ctrl + c.

If you notice, in fact, I launch a subsequent sudo killall tor, which goes to free up port 9050 again.

Later, however, when I reconnect, and tells me that everything is OK, the IP does not change.

mike@dev:~$ curl ifconfig.me

xx.104.95.86mike@dev:~$ 

mike@dev:~$ tor

Jan 24 14:59:23.965 [notice] Tor 0.2.9.14 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g and Zlib 1.2.8.

Jan 24 14:59:23.965 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning

Jan 24 14:59:23.965 [notice] Read configuration file "/etc/tor/torrc".

Jan 24 14:59:23.967 [notice] Opening Socks listener on 127.0.0.1:9050

Jan 24 14:59:23.967 [warn] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?

Jan 24 14:59:23.967 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.

Jan 24 14:59:23.967 [err] Reading config failed--see warnings above.

mike@dev:~$ sudo killall tor

Jan 24 14:59:27.000 [notice] Catching signal TERM, exiting cleanly.

mike@dev:~$ tor &

[2] 32737

[1]   Completato              tor

mike@dev:~$ Jan 24 14:59:39.015 [notice] Tor 0.2.9.14 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g and Zlib 1.2.8.

Jan 24 14:59:39.015 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning

Jan 24 14:59:39.015 [notice] Read configuration file "/etc/tor/torrc".

Jan 24 14:59:39.018 [notice] Opening Socks listener on 127.0.0.1:9050

Jan 24 14:59:39.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.

Jan 24 14:59:39.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.

Jan 24 14:59:39.000 [notice] Bootstrapped 0%: Starting

Jan 24 14:59:39.000 [notice] Bootstrapped 80%: Connecting to the Tor network

Jan 24 14:59:40.000 [notice] Bootstrapped 85%: Finishing handshake with first hop

Jan 24 14:59:40.000 [notice] Bootstrapped 90%: Establishing a Tor circuit

Jan 24 14:59:40.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.

Jan 24 14:59:40.000 [notice] Bootstrapped 100%: Done

mike@dev:~$ curl ifconfig.me

xx.104.95.86mike@dev:~$ 

comment:8 Changed 9 months ago by arma

Is your 'curl' configured to send its traffic into tor? tor doesn't magically intercept all outgoing connections.

More generally, you're definitely using Tor in a nonstandard way. Most people should just use Tor Browser, and those that use it in expert mode on Debian / Ubuntu should be using the Tor deb. (If you are using the Tor deb, you are definitely invoking it wrong -- it should be through 'service tor start' and the like.)

comment:9 Changed 9 months ago by killerbee

I don't know, I have installed tor via 'sudo apt install tor', but this method (tor &; curl ifconfig.me) was working for me few month ago. I don't know what is changed. My OS is Ubuntu 16.04.5 LTS.

I use tor to launch python scripts in anonymous mode, so tor browser is not what i need.

I have tryed to use the service command, but the result is the same. The IP doesn't change.

How can I configure the curl or make sure it is configured correctly? Once time it was working...

Thanks in advance.
Mike

comment:10 Changed 9 months ago by killerbee

P.S: If i use Tor Browser or Tor Chrome extension with Chromium, it works fine.

comment:11 Changed 9 months ago by killerbee

Ok, you can close the ticket. I'm a n00b lol!

I have to launch curl --socks5-hostname 127.0.0.1:9050 ifconfig.me

Tor has always worked.

Thanks at all.

Mike

comment:12 Changed 9 months ago by nickm

Resolution: not a bug
Status: newclosed
Note: See TracTickets for help on using tickets.