[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-talk] I can't connect to tor or vidalia, but I could yesterday

To: "tor-talk@xxxxxxxxxxxxxxxxxxxx" <tor-talk@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [tor-talk] I can't connect to tor or vidalia, but I could yesterday
From: John DeLuca <johnnyde94@xxxxxxxxx>
Date: Fri, 15 Nov 2013 09:44:11 -0500
Delivered-to: archiver@xxxxxxxx
Delivery-date: Fri, 15 Nov 2013 09:56:12 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:content-type:in-reply-to:message-id:date:to :content-transfer-encoding:mime-version; bh=IA3KSr8JfDnlNEdhsUfTFDjXnMI0HRclsoGelKmZ8nw=; b=0CaVHjsujjZ16SLfUriivTWdym3tBFLQHSX4xLTrNUZA2Zdujs/XXFqmxZg1Uic80V hjkeEzBbQBxoje9qznJeFPKDV8eVUkPRv211ks+mWMe9uesZHieiC1rw9RA5OqhEDIvM EjbzskccJ8WL9yfQlZBTeyJ8/RKcLaOgeglTKof97DqOjf6JpwARoGr6tf2THBZx2zum iNo3i/m6T9D2IqgWApGxgimSOpbLVpp9V/yv6VCNKJWySVky8Yf9Li82JaN6bUMnVU7q ASkjpCiOYeYbMmc4EtSeG6yu624AIT6VWoKlxrat79ZCWcK1OTJ05HlMa333ECSO8rII L35A==
In-reply-to: <E7CB688D-AA4D-495C-B9EB-76D79C6EA402@xxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-id: "all discussion about theory, design, and development of Onion Routing" <tor-talk.lists.torproject.org>
List-post: <mailto:tor-talk@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
References: <mailman.2855.1384443766.2610.tor-talk@xxxxxxxxxxxxxxxxxxxx> <E7CB688D-AA4D-495C-B9EB-76D79C6EA402@xxxxxxxxx>
Reply-to: tor-talk@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-talk" <tor-talk-bounces@xxxxxxxxxxxxxxxxxxxx>


Sent from my iPhone

> On Nov 14, 2013, at 11:13 AM, John DeLuca <johnnyde94@xxxxxxxxx> wrote:
> 
>> 
>> From: John DeLuca <johnnyde94@xxxxxxxxx>
>> Subject: I can't connect to tor or vidalia, but I could yesterday
>> Date: November 14, 2013 at 10:42:40 AM EST
>> To: tor-talk@xxxxxxxxxxxxxxxxxxxx
>> 
>> 
>> Nov 14 10:36:07.580 [Warning] We were supposed to connect to bridge '87.237.118.139:444' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.580 [Warning] We were supposed to connect to bridge '194.38.106.35:80' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.581 [Warning] We were supposed to connect to bridge '212.184.134.17:29001' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.581 [Warning] We were supposed to connect to bridge '77.79.11.204:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.582 [Warning] We were supposed to connect to bridge '81.91.1.81:403' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.582 [Warning] We were supposed to connect to bridge '60.16.182.53:9001' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.582 [Warning] We were supposed to connect to bridge '54.221.44.79:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.583 [Warning] We were supposed to connect to bridge '54.213.22.46:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.583 [Warning] We were supposed to connect to bridge '60.63.97.221:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:07.584 [Warning] We were supposed to connect to bridge '83.212.111.114:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:20.901 [Notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on Darwin.
>> Nov 14 10:36:20.902 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
>> Nov 14 10:36:20.902 [Notice] Read configuration file "/Users/johndeluca/Downloads/TorBrowser_en-US.app/Contents/MacOS/Vidalia.app/Contents/MacOS/../../../../../Library/Vidalia/torrc".
>> Nov 14 10:36:20.902 [Notice] Initialized libevent version 2.0.21-stable using method kqueue. Good.
>> Nov 14 10:36:20.903 [Notice] Opening Socks listener on 127.0.0.1:9150
>> Nov 14 10:36:20.903 [Notice] Opening Control listener on 127.0.0.1:9151
>> Nov 14 10:36:20.903 [Notice] No AES engine found; using AES_* functions.
>> Nov 14 10:36:20.904 [Notice] This OpenSSL has a good implementation of counter mode; using it.
>> Nov 14 10:36:21.044 [Notice] OpenSSL OpenSSL 1.0.0k 5 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
>> Nov 14 10:36:21.044 [Notice] Reloaded microdescriptor cache.  Found 0 descriptors.
>> Nov 14 10:36:21.045 [Notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
>> Nov 14 10:36:21.045 [Notice] New control connection opened.
>> Nov 14 10:36:21.045 [Warning] Error parsing Bridge address 'relays'
>> Nov 14 10:36:21.045 [Warning] Controller gave us config lines that didn't validate: Bridge line did not parse. See logs for details.
>> Nov 14 10:36:21.997 [Notice] Bootstrapped 5%: Connecting to directory server.
>> Nov 14 10:36:21.998 [Warning] We were supposed to connect to bridge '83.212.111.114:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:21.998 [Warning] We were supposed to connect to bridge '60.63.97.221:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:21.999 [Warning] We were supposed to connect to bridge '54.213.22.46:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:21.999 [Warning] We were supposed to connect to bridge '54.221.44.79:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:22.000 [Warning] We were supposed to connect to bridge '60.16.182.53:9001' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:22.000 [Warning] We were supposed to connect to bridge '81.91.1.81:403' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:22.001 [Warning] We were supposed to connect to bridge '77.79.11.204:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:22.001 [Warning] We were supposed to connect to bridge '212.184.134.17:29001' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:22.001 [Warning] We were supposed to connect to bridge '194.38.106.35:80' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:22.002 [Warning] We were supposed to connect to bridge '87.237.118.139:444' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:22.002 [Warning] We were supposed to connect to bridge '141.201.27.48:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:36:22.003 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
>> Nov 14 10:37:36.257 [Warning] We were supposed to connect to bridge '141.201.27.48:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.258 [Warning] We were supposed to connect to bridge '87.237.118.139:444' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.259 [Warning] We were supposed to connect to bridge '194.38.106.35:80' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.259 [Warning] We were supposed to connect to bridge '212.184.134.17:29001' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.260 [Warning] We were supposed to connect to bridge '77.79.11.204:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.260 [Warning] We were supposed to connect to bridge '81.91.1.81:403' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.261 [Warning] We were supposed to connect to bridge '60.16.182.53:9001' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.261 [Warning] We were supposed to connect to bridge '54.221.44.79:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.262 [Warning] We were supposed to connect to bridge '54.213.22.46:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.262 [Warning] We were supposed to connect to bridge '60.63.97.221:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.263 [Warning] We were supposed to connect to bridge '83.212.111.114:443' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
>> Nov 14 10:37:36.264 [Warning] Error parsing Bridge address 'relays'
>> Nov 14 10:37:36.265 [Warning] Controller gave us config lines that didn't validate: Bridge line did not parse. See logs for details.
> 
-- 
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Prev by Author: Re: [tor-talk] tor mention in newle released snowden documents
Next by Author: Re: [tor-talk] Is it possible to access healthcare.gov through Tor?
Previous by thread: [tor-talk] Torchan and other onion sites
Next by thread: [tor-talk] Current ipkg version for NAS
Index(es):
- Author
- Thread