Opened 6 years ago

Closed 6 years ago

#12764 closed defect (fixed)

openvz tor in node and in vps

Reported by: poiuty Owned by:
Priority: Medium Milestone: Tor: 0.2.4.x-final
Component: - Select a component Version: Tor: unspecified
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I use OpenVZ. On node I set tor relay.

In /etc/tor/torrc
ControlPort IP_NODE:9051
DirPort IP_NODE:9030
ExitPolicy reject *:*
ExitPolicy reject6 *:*
Nickname poiuty5
ORPort IP_NODE:443
RelayBandwidthRate 5 MB
RelayBandwidthBurst 5 MB
CookieAuthentication 1

/etc/init.d/tor restart

Restarting tor: /usr/bin/torctl stop: tor stopped
Aug 01 20:31:21.921 [notice] Tor v0.2.4.23 (git-e6dcb6c46a851422) running on Linux with Libevent 1.4.13-stable and OpenSSL 1.0.1e-fips.
Aug 01 20:31:21.921 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Aug 01 20:31:21.921 [notice] Read configuration file "/etc/tor/torrc".
Aug 01 20:31:21.933 [warn] You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That's pretty bad, since the controller protocol isn't encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Aug 01 20:31:21.934 [warn] You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That's pretty bad, since the controller protocol isn't encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Aug 01 20:31:21.934 [notice] Opening Socks listener on 127.0.0.1:9050
Aug 01 20:31:21.934 [notice] Opening Control listener on IP_NODE:9051
Aug 01 20:31:21.934 [notice] Opening OR listener on IP_NODE:443
Aug 01 20:31:21.934 [notice] Opening Directory listener on IP_NODE:9030
/usr/bin/torctl start: tor started

[ OK ]

In log
Aug 01 18:37:54.000 [warn] Your server (IP_VPS:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Aug 01 18:37:54.000 [warn] Your server (IP_VPS:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Aug 01 18:57:54.000 [warn] Your server (IP_VPS:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Aug 01 18:57:54.000 [warn] Your server (IP_VPS:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

On VPS -> also tor work, but not relay.


Child Tickets

Change History (1)

comment:1 Changed 6 years ago by poiuty

Resolution: fixed
Status: newclosed

Oh, its my mistake in /etc/hosts

Note: See TracTickets for help on using tickets.