- tor-relays - lists.torproject.org

Relay configuration issue "Could not bind to 0.0.0.0:443: Permission denied"
by AJ NOURI 22 Jan '16

22 Jan '16

*sudo service tor reload* * Reloading tor daemon configuration... [fail] */var/log/tor/log* > > Jan 08 08:01:25.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd) > opening new log file. > Jan 08 10:19:40.000 [notice] Heartbeat: Tor's uptime is 3 days 0:00 > hours, with 0 circuits open. I've sent 1.17 MB and received 28.04 MB. > Jan 08 12:31:58.000 [notice] Received reload signal (hup). Reloading > config and resetting internal state. > Jan 08 12:31:58.000 [notice] Read configuration file > "/usr/share/tor/tor-service-defaults-torrc". > Jan 08 12:31:58.000 [notice] Read configuration file "/etc/tor/torrc". > Jan 08 12:31:58.000 [notice] Based on detected system memory, > MaxMemInQueues is set to 5988 MB. You can override this by setting > MaxMemInQueues by hand. > Jan 08 12:31:58.000 [notice] Opening OR listener on 0.0.0.0:443 > Jan 08 12:31:58.000 [warn] **Could not bind to 0.0.0.0:443: > Permission denied** > Jan 08 12:31:58.000 [warn] Failed to parse/validate config: Failed to > bind one of the listener ports. > Jan 08 12:31:58.000 [err] Reading config failed--see warnings above. > For usage, try -h. > Jan 08 12:31:58.000 [warn] Restart failed (config error?). Exiting. *Configuration /etc/tor/torrc* ORPort 443 > Nickname ididnteditheconfig > RelayBandwidthRate 1000 KBytes # Throttle traffic to 100KB/s (800Kbps) > RelayBandwidthBurst 2000 KBytes # But allow bursts up to 200KB (1600Kb) > ExitPolicy reject *:* Opened 443 port on the Internet box: http://i.stack.imgur.com/oVwzO.jpg [image: Inline image 1] Port 443 locally opened: *ss -tunlp | grep 443* tcp LISTEN 0 128 *:443 > *:* > tcp LISTEN 0 128 :::443 > :::*

4 4

[warn] Bad password or authentication cookie on controller.
by pa011 21 Jan '16

21 Jan '16

Hello, yesterday I got within a minute three times the above warning in my log file on Tor 0.2.7.6. Could somebody please explain to me what it means and how to solve? Is there a source where I can possibly find answers on this and other warnings? Thanks in advance Paul

2 1

Re: [tor-relays] what's up(down) with gablemoo?
by starlight.2016q1＠binnacle.cx 21 Jan '16

21 Jan '16

At 18:55 1/21/2016 +0100, you wrote: >Gabelmoo is running 0.2.7.6. . . Thank you for replying. I saw earlier that moria1 ran into this and decided to wait on 0.2.7 for my relay, though I suppose the issue is specific to authorities and does not apply to normal relays.

2 1

what's up(down) with gablemoo?
by starlight.2016q1＠binnacle.cx 21 Jan '16

21 Jan '16

Lately 'gabelmoo' had been bouncing down and up like a ping-pong ball. Because gabelmoo is a BWauth (of which only five exist) as well as a normal authority, the impact is greater than if it did not participate in bandwidth measurement. Disrupts the consensus median. Does anyone know anything about it? Thanks

2 1

Location of private key on Android?
by Christian Andersen 21 Jan '16

21 Jan '16

Hey guys, I'm running Orbot as a relay on my otherwise unused mobile. It works great! https://atlas.torproject.org/#details/B47A49120A51D28A6191BE9A67F102AA96F5F… But in case I ever need to move the relay to a real computer, or start using the mobile, I'll need the private key, but I can't seem to find it. My phone is Sony Xperia ZR, unrooted, running Android 5.1.1, 10.7.A.0.228 (possibly a Sony version number). Orbot is version 15.1.0-RC-2 (Tor 0.2.7.5-020120160125) I just updated from Google Play Store - I realize the version above (from the About-menu) doesn't reflect the Atlas-info. I don't know why. Root\Android\data shows no folders related to Orbot, I have unchecked "Hide system files" in the file managers I downloaded from Google Play store. - File Manager from ZenUI - File Manager from SAND STUDIO and - File Commander - File Manager from MobiSystems - - Which requires Premium to view hidden files(!). Any help is appreciated. Maybe i just need a non-sucky file manager? C A

1 0

arm /flags gives unknown
by Dr. Who 21 Jan '16

21 Jan '16

Since some months I monitored my tor instance via this one liner: echo "/info" | /usr/bin/arm -p | /bin/grep flags but it seems after updating to 0.2.7.6 it only gives my unknown as result. Has something changed the communication between tor and arm? Even manually I can only get this answer: >>> /info TeamTardis (330CD3DB6AD266DC70CDB512B036957D03D9BC59) address: 185.100.84.212:443 (ro) published: 06:28:21 2016-01-20 os: Linux version: 0.2.7.6 flags: unknown exit policy: reject 1-65535 contact: Team Tardis <drwho(a)posteo.is>

5 5

relays possible sybil
by tor-server-creator＠use.startmail.com 20 Jan '16

20 Jan '16

hi, just wondering whats the matter with these 66+ relays "cloudvps" ... guess they get vote, should we discard some iprages? thanks

3 3

Running a relay, only, in win7
by je suis 19 Jan '16

19 Jan '16

Hello all I'm sorry if I'm writing to the wrong list. Until recently and since some months back, I ran a tor relay under Linux, during daytime (only have my laptop), with 2.5/5MBps speed. Not much, it took an hour or two to really start, but it worked, I hope it helped a bit. Now I find I need to spend time in win7 more and I'd like to keep on running a relay, but I can't seem to get tor to work. Since the FAQ only says what Linux users should do and all my searches turned out to have Vidalia involved, I don't know how to make this work, so I'm asking for help: is there a place where I can read, or could you tell me what I need to do to run a relay in win7? Thank you in advance, Vlad

4 6

atlas not showing 3 days and 1 week graphs
by krishna e bera 19 Jan '16

19 Jan '16

Is atlas.torproject.org broken or changed? It seems to show only 1 month and longer graphs now.

5 6

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors
by starlight.2016q1＠binnacle.cx 19 Jan '16

19 Jan '16

I'd guess a bug in the version update script. At 19:20 1/12/2016 +0100, Aeris wrote: >> Are you *absoultely* certain that the config >> was not fiddled with at the time of this event? > >After grepping some logs, seems 13/12 was the day of a Tor >upgrade : > >2015-12-13 10:47:31 upgrade tor:amd64 0.2.7.5-1~d80.jessie+1 0.2.7.6-1~d80.jessie+1 >2015-12-13 10:48:39 configure tor:amd64 0.2.7.6-1~d80.jessie+1 > >Timing is good compare to the 10:48:46 of the consensus ! > >But I donât remember a config change after that, >perhaps only on /usr/share/tor/tor-service-defaults-torrc >or on a default config param change ? > >And perhaps the Tor reboot cause the DirPort to >be temporarily disabled (seems not human, only >2s duration) ? > >Regards, >-- >Aeris

2 4