[tor-relays] Failing: 4063 Connection error

Where can I set the connection limit higher or is this a result of max bandwidth allowed? This relay was up for over a year with no issues, however since updating the Tor version it's been problematic at best. Thanks. Linux version 2.6.32-042stab125.5 (r...@kbuild-rh6-x64.eng.sw.ru) (gcc version 4.

[tor-relays] No Gaurd

https://atlas.torproject.org/#details/E65D300F11E1DB12C534B0146BDAB6972F1A8A48 Relay looks pretty stable to me, I'm re-visiting the lack of guard status... ideas? signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-rel

[tor-relays] Horizons Relay Figerprint

E65D300F11E1DB12C534B0146BDAB6972F1A8A48 signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] A Common Thread: Guard Status

Just curious and I know it's probably been answered 100x times... I recently updated Tor to an, 'approved version', after 340+ days of up time. Upon restarting the relay, 25 days ago, Ive not been given the 'guard flag' again. Why? Thanks signature.asc Description: OpenPGP digital signature ___

[tor-relays] Tor Install Error

While using apt-get to update my tor relay to a 'recommended' version I keep encountering this error: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.torproject.org trusty InRelease: The followin

Re: [tor-relays] New Tor relay

On 2/21/2017 6:00 AM, Luca Tortiglione wrote: > Hi all! > I'm paying a VPS to run a tor relay. > I hope it will go well. > > Glad to belong to the family by helping the community. > > Of course, I'm runnin Tor 0.2.9.9 on Debian. > > Thank you. > Welcome and thanks for running a relay! :-) si

Re: [tor-relays] Raspberry Pi + Raspbian GNU/Linux 8.0 (jessie) + bind errors

On 1/5/2017 6:50 PM, Roger Dingledine wrote: > On Thu, Jan 05, 2017 at 06:38:23PM -0800, Kurt Besig wrote: >> I just installed tor on a Raspberry Pi 3 Model B and can't get a relay >> to start unless I sudo. When I attempt to start tor as a non-privileged >> user I get a

[tor-relays] Raspberry Pi + Raspbian GNU/Linux 8.0 (jessie) + bind errors

I just installed tor on a Raspberry Pi 3 Model B and can't get a relay to start unless I sudo. When I attempt to start tor as a non-privileged user I get a permissions error: Opening Jan 05 18:33:35.929 [notice] Opening OR listener on 0.0.0.0:443 Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0

[tor-relays] Raspberry Pi + Raspbian GNU/Linux 8.0 (jessie) + bind errors

I just installed tor on a Raspberry Pi 3 Model B and can't get a relay to start unless I sudo. When I attempt to start tor as a non-privileged user I get a permissions error: Opening Jan 05 18:33:35.929 [notice] Opening OR listener on 0.0.0.0:443 Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0

Re: [tor-relays] Faravahar acting up again / "Bad Gateway" while uploading descriptor

On 1/5/2017 1:29 PM, anondroid wrote: > I just set up a handful of new relays, and all of them have something > like the following in their logs: > > [WARN] http status 502 ("Bad Gateway") reason unexpected while > uploading descriptor to server '154.35.175.225:80' > [WARN] Received http statu

Re: [tor-relays] Inconsistent BW measurements of unused relay

On 12/11/2016 1:43 PM, Rana wrote: >> On 12 Dec. 2016, at 01:56, Rana wrote: >> >> OK Tim thanks for the answers, I appreciate your patience with me >> [even though I "lack programming skills" :) ] >> >> The one answer of yours that still does not make sense to me is that >> arm actually means K

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

On 12/4/2016 7:39 AM, Rana wrote: >> For as little as $10.00 US there are VPS' with static ip's.. > > Attn: Kurt Besig > > Well I kind o' like my Raspberry Pi that cost me $40 including box and power > supply and SD card and door to door delivery, with fa

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

On 12/4/2016 1:03 AM, teor wrote: > >> On 4 Dec. 2016, at 01:06, Rana wrote: >> >> I have been running a relay with dynamic IP for a month now and quite >> obviously my relay is severely punished for having a dynamic IP. The IP may >> change once in several days (currently running over a week w

Re: [tor-relays] Questions regarding arm on Debian

On 11/12/2016 8:34 AM, r1610091651 wrote: > On Sat, 12 Nov 2016 at 12:41 Dennis Christ > wrote: > > Yes that is what i tried to do. But it does not work in my case. > > $ arm > [Errno 13] Permission denied: '/var/lib/tor/control_auth_cookie' > > Even if my

Re: [tor-relays] proper way to insert PGP key in torrc?

On 11/3/2016 11:15 PM, grarpamp wrote: > On Thu, Nov 3, 2016 at 6:39 AM, Toralf Förster wrote: >> Not too much fun with such a lame relay I fear > > He's running a relay because what he believe and it's fun > without hurting nobody.. and you bash him not running > with big dogs. Wtf bro. > > Pro

Re: [tor-relays] ISP, Abuses , Intrusion Prevention etc.

On 10/11/2016 1:53 AM, Moritz Bartl wrote: > On 10/11/2016 12:51 AM, Kenneth Freeman wrote: > I set up my own ISP (AS28715) so I could run Tor exits etc without any > trouble. Could you share a bit more about what is involved in doing that? >>> I'd also be very interested in learning m

Re: [tor-relays] Exit relay funding

On 8/3/2016 10:13 PM, Roger Dingledine wrote: > On Wed, Aug 03, 2016 at 03:29:01PM +0200, t...@as250.net wrote: >> Absolutely. Most of the infrastructure we provide on that basis and it >> is ok! The reason for running that exit node was that we believed it >> would contribute towards a positive im

Re: [tor-relays] biggest guard operator apparently left the tor network

On 2/28/2016 5:00 AM, nusenu wrote: > Looks like SG.GS stopped their guard relays. They had >3% guard probability. > > +---++--+ > | Con5 | lastseen | fingerprint | > +---++-

Re: [tor-relays] tor middle node question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/26/2016 12:58 AM, Markus Koch wrote: > hi, > > as a good TOR support peon I got a dedicated server and set up TOR > 3-4 weeks ago. Everything went great, I got my Guard, Fast and > Stable etc. Flag and my little server was busy & happy. After > r

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

On 12/17/2015 6:07 AM, Nick Mathewson wrote: > TL;DR: Stable non-exit relays can help tor clients use the Tor > network. Please opt-in! > > We want to run a trial of fallback directory mirrors (fallbacks) > in Tor. Tor clients contact fallbacks to download the consensus > during initial bootstrap

[tor-relays] VPS/Tor Final Thoughts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I thought it might be helpful to any other volunteer that may have been silently following this thread to quickly post the issues with my VPS Tor server that were resolved. 1. Setting up iptables allowed connections to my server. 2. Adding my server'

[tor-relays] VPS/Tor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I want to thank everyone for the multitude of great suggestions regarding getting my relay up on a VPS. I reviewed every email and all the input was useful. The relay is up and running: E65D 300F 11E1 DB12 C534 B014 6BDA B697 2F1A 8A48 As well as my ho

[tor-relays] VPS/Tor Almost There

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks again for all the support everyone has bee extremely helpful. So, I reinstalled the OS on the VPS: lsb_release -d Description: Ubuntu 14.04.3 LTS uname -r 2.6.32-042stab102.9 Finally solved all the permissions problems, paths are correct, tor

Re: [tor-relays] Unbelieveable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/5/2015 3:20 PM, Sean Greenslade wrote: >>> Dec 05 21:17:46.000 [notice] Your IP address seems to have >>> changed to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05 >>> 21:17:46.000 [notice] Our IP Address has changed from >>> 142.4.217.95 to

Re: [tor-relays] Unbelieveable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/4/2015 8:25 PM, Damian Johnson wrote: > For what it's worth process permissions aren't at play here. Arm > is failing to talk with the control port - permissions could cause > us to be unable to read the authentication cookie, but that would > be

Re: [tor-relays] Unbelieveable

it as a life lesson (or not, I don't really care that much) > but you'll get a lot more support from people if you don't act like > an entitled jerk who deserves other peoples' time and expertise for > free. > > > > On 2015-12-04 10:21, Kurt Besig wrote: &g

Re: [tor-relays] Unbelieveable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/4/2015 9:29 AM, AMuse wrote: > Looks like you got more than you paid for. > > > > On 2015-12-03 18:46, Kurt Besig wrote: > > That I got two responses after posting to tor-relays regarding a > fairly simple, I thought

Re: [tor-relays] VPS Connection Refused

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/3/2015 7:04 PM, Tim Wilson-Brown - teor wrote: > >> On 3 Dec 2015, at 09:44, Kurt Besig > <mailto:kbe...@socal.rr.com>> wrote: >> >> After setting up Tor and tor-arm on the VPS I'm not able to >>

Re: [tor-relays] Unbelieveable

t a few random answers, > at best. -k0nsl > > Den 12/4/2015 kl. 3:46 AM, skrev Kurt Besig: >> That I got two responses after posting to tor-relays regarding a >> fairly simple, I thought, CntrolPort question on a new VPS

[tor-relays] Unbelieveable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That I got two responses after posting to tor-relays regarding a fairly simple, I thought, CntrolPort question on a new VPS relay.. That's pathetic. Thanks for all your input. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAG

Re: [tor-relays] VPS Connection Refused

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/2/2015 7:09 PM, Michael McConville wrote: > Kurt Besig wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 12/2/2015 3:06 PM, Michael McConville wrote: >>> Kurt Besig wrote: >>>> I just

Re: [tor-relays] VPS Connection Refused

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/2/2015 3:06 PM, Michael McConville wrote: > Kurt Besig wrote: >> I just set up a VPS on PulseServers as I noticed quite a few >> running relays had mostly good things to say about the service. >> So Far the people operating

Re: [tor-relays] VPS Connection Refused

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/2/2015 4:54 PM, I wrote: > Doesn't Arm look for 9051? > > Robert > > > ___ tor-relays mailing > list tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relay

[tor-relays] VPS Connection Refused

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just set up a VPS on PulseServers as I noticed quite a few running relays had mostly good things to say about the service. So Far the people operating the servers seem very cooperative and responsive. Anyway I've been running a middle relay for 1.5 y

Re: [tor-relays] Tor Weather not working?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/20/2015 10:41 AM, tor-server-crea...@use.startmail.com wrote: > whos then receiving home-addresses from longtime relay-owners > earned t-shirts?! > > > Am Dienstag, 17. November 2015 21:00 schrieb nusenu > : > >>> >> >> tor weather hasn't b

Re: [tor-relays] I.P. being Blocked?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/9/2015 10:00 AM, Zack Weinberg wrote: > On 08/09/2015 12:52 PM, Kurt Besig wrote: >> Without going into any detail at this point I'm wondering if >> others, running a simple middle relay, have encountered any >> go

[tor-relays] I.P. being Blocked?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Without going into any detail at this point I'm wondering if others, running a simple middle relay, have encountered any governmental harassment as a direct result of running a relay. The blocking of state agencies e.g, CA.SDI.gov, CA.DMV.gov? Over t

Re: [tor-relays] Giving away some "pre-warmed" relay keys for adoption

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/25/2015 7:13 PM, Roman Mamedov wrote: > On Sun, 26 Jul 2015 01:35:10 + Yawning Angel > wrote: > >> The relay identity key is sensitive cryptographic material. >> Sharing it means the private key is compromised and is an attempt >> to subvert

Re: [tor-relays] Unreachable ORPort - Potential ISP block?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/5/2015 12:31 PM, CJ Barlow wrote: > I'm attempting to run a Relay but I haven't been able to get it > the ORPort to be confirm as reachable. I've tried lots of things > but I'm hoping there is something I haven't thought of yet that can > make thi

Re: [tor-relays] Mozilla-Middles losing guard

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/17/2015 10:59 AM, lpwzi9...@use.startmail.com wrote: > at this very moment all of them got the flag, right. But theyre > loosing it at seemingly random order. I kept an eye on Atlas for > some time, at 18:00 (UTC+1) Mozilla13 was at 1.51 MB/s with

Re: [tor-relays] New Arris TG1672 Cable Modem, relay not reachable...help!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/19/2015 10:45 AM, kbesig wrote: > > On 01/18/2015 02:18 PM, Kurt Besig wrote: >> I'm trying to narrow down my connectivity problem and am >> wondering if anyone is runniing a relay, or knows of someone >> successf

[tor-relays] New Arris TG1672 Cable Modem, relay not reachable...help!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been running a middle relay for nine months with great success, however yesterday my ISP, TWC, upgraded my cable modem and everything went south. Then unfortunately there was a firmware upgrade for my Asus RT-N66U router. Perfect storm, now My rel

[tor-relays] Unexpected sendme cell from...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I this was discussed awhile back through the mailing list and online to some extent, however I never grasped the solutions or any real resolution to the issue. My relay is getting fairly hammered daily and I'd appreciate any input regarding the, "[WARN

Re: [tor-relays] Why did my relay fall out of the consensus?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/4/2014 7:06 AM, Steve Snyder wrote: > On June 9th my relay, which was established about 20 months ago, > fell out of the cached consensus. > > There are no errors in the logs, just notices that the relay is not > in the cached consensus. Apart f

Re: [tor-relays] Tor-relay - IP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/18/2014 8:54 AM, Rui Branco wrote: > hello, I'm a new user of the Tor-relay and I have many doubts. > Sorry about that. > > In the atlas project why the tor-relays ip are discovered? isn't > it dangerous? > When I first starting using Tor and l

[tor-relays] One server, Two open tor connections

Hi all, I'm currently running a Linux relay on one LAN machine. I recently set-up a dual boot win7/Ubuntu 14.04 LTS machine, also on the LAN. For now I'd just like to browse the tor network on the second machine and not run a relay on it for the present. I'm concerned my ISP might give me problems

Re: [tor-relays] SSH scans from Tor exit

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/30/2014 9:01 PM, I wrote: > The original point has drifted over the horizon. > > I asked what could be done, in my case, to stop SSH attacks > originating FROM my VPS which is running as an exit. There was > another VPS emanating SQL injection at

Re: [tor-relays] Relay down, "rejected", help

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/30/2014 11:38 AM, Delton Barnes wrote: > Roger Dingledine: >> You're using arm dangerously. See item #14 on >> https://www.torproject.org/docs/tor-relay-debian for the safer >> way to run arm with your Debian / Ubuntu relay. > > Followed item #1