[tor-relays] Relay configuration issue "Could not bind to 0.0.0.0:443: Permission denied"
*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* tcpLISTEN 0 128*:443 > *:* > tcpLISTEN 0 128 :::443 > :::* ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Relay configuration issue "Could not bind to 0.0.0.0:443: Permission denied"
Removed and reinstalled Tor. Now works fine. Appreciate your prompt answers guys! On Fri, Jan 22, 2016 at 10:42 AM, Louie Cardone-Noott <l...@fastmail.net> wrote: > Try restart instead of reload. > > It looks like you've installed from a package, which allows the daemon to > bind to any port then "drop privileges" (according to the FAQ). > > https://www.torproject.org/docs/faq.html.en#PackagedTor > > > On Mon, 18 Jan 2016, at 12:26 AM, AJ NOURI wrote: > > *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* > > > tcpLISTEN 0 128*:443 > *:* > tcpLISTEN 0 128 :::443 > :::* > > > > *___* > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > Email had 1 attachment: > >- image.png > 61k (image/png) > > > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Please enable IPv6 on your relay!
Hi, I set IPv6 tor relay *ORPort [::]:9050* getting this error when restarting: ### *sudo tor restartMay 13 16:01:53.021 [notice] Tor v0.2.5.12 (git-3731dd5c3071dcba) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1f and Zlib 1.2.8.May 13 16:01:53.021 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning https://www.torproject.org/download/download#warningMay 13 16:01:53.021 [warn] Command-line option 'restart' with no value. Failing.May 13 16:01:53.021 [err] Reading config failed--see warnings above.* ### On Wed, May 13, 2015 at 3:27 PM, JovianMallard t...@sec.gd wrote: [::1] is the IPv6 loopback address - use [::] to listen on any address. On 05/13/2015 03:09 AM, torser...@ittk.it wrote: I have enabled it at 1 VPS and 1 Root. And I enabled it on 2 instances which are connected via broadbandconnections with dynamic addresses for IPv4 and IPv6. There I got that information after applying the configuration: 07:05:49 [WARN] Unable to use configured IPv6 address [::1] in a descriptor. Skipping it. Try specifying a globally reachable address explicitly. 07:05:49 [NOTICE] Your Tor server's identity key fingerprint is 'xxx' 07:05:49 [NOTICE] Opening OR listener on [::1]:2342 I hope that will work as desired. Marcel Brian Kroll br...@fiberoverethernet.com hat am 13. Mai 2015 um 07:45 geschrieben: I just enabled four relays, who has the next two? ^_^ //Brian Ana Lucia Cortez: On Wed, May 13, 2015 at 12:09:45AM +0200, Moritz Bartl wrote: Come on guys, we only need 6 more IPv6 relays to help Moritz out of his depression ... We still have a depressingly low number of relays that support IPv6 (currently only ~120 of ~1900 relays). Thats 6.3% IPv6 adoption rate amongst Tor relays, while todays global overall IPv6 adoption rate is 6.6% according to https://www.google.com/intl/en/ipv6/statistics.html. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
