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 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] Relay configuration issue "Could not bind to 0.0.0.0:443: Permission denied"
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 Inline image 1 > > Port 443 locally opened: *ss -tunlp | grep 443* > >> tcp LISTEN 0 128 *:443 >> *:* tcp LISTEN 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
Re: [tor-relays] Relay configuration issue "Could not bind to 0.0.0.0:443: Permission denied"
On Mon, Jan 18, 2016 at 01:26:05AM +0100, AJ NOURI wrote: > *sudo service tor reload* > > * Reloading tor daemon configuration... [fail] > > > Jan 08 12:31:58.000 [notice] Received reload signal (hup). Reloading > > config and resetting internal state. > > Jan 08 12:31:58.000 [warn] **Could not bind to 0.0.0.0:443: > > Permission denied** See https://trac.torproject.org/projects/tor/ticket/918 for an explanation of why this happens. The easy fix is to pick an ORPort above 1024. --Roger ___ 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"
You must be root to bind at this port. Jan 08 12:31:58.000 [warn] **Could not bind to 0.0.0.0:443: Permission denied** Ursprüngliche Nachricht Von: AJ NOURI Gesendet: 18. Januar 2016 01:26:05 MEZ An: tor-relays@lists.torproject.org Betreff: [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 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[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