[tor-relays] VPS/Tor Almost There

[Tim Wilson-Brown - teor]

Hi Kurt,

You need to know the public IPv4 address of your relay.
Until you have the address correct, it's hard to tell whether you need to open any ports or not.
>  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
>  167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE).
>  Dec 05 21:18:42.000 [notice] Your IP address seems to have changed
>  to 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com <http://ca3.pulseservers.com/>).
>  Updating. Dec 05 21:18:42.000 [notice] Our IP Address has changed
>  from 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source:
>  METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com <http://ca3.pulseservers.com/>). Dec 05
>  21:18:43.000 [notice] Self-testing indicates your ORPort is
>  reachable from the outside. Excellent. Publishing server
>  descriptor. Dec 05 21:38:37.000 [warn] Your server
>  (142.4.217.95:9030) has not managed to confirm that its DirPort is
>  reachable. Please check your firewalls, ports, address, /etc/hosts
>  file, etc. Dec 05 21:58:37.000 [warn] Your server
>  (142.4.217.95:9030) has not managed to confirm that its DirPort is
>  reachable. Please check your firewalls, ports, address, /etc/hosts
>  file, etc.
> I've gotten this far, not being much good at networking I can't tell
> where the problem lies.. do I need to forward something?
> 

Tor is receiving two different IP addresses using two different methods of working out your VPS IP address:
* gethostname() on ca3.pulseservers.com <http://ca3.pulseservers.com/> returns 142.4.217.95
* an OS-specific interface address system call returns 167.114.35.28

Please find out from your admin which IPv4 address you should use, and specify it using the "Address" option in your torrc.
(Or, alternately, make a connection to http://www.myipaddress.com/show-my-ip-address/ <http://www.myipaddress.com/show-my-ip-address/> or similar from the VPS, and look at the address it returns.)

> On 7 Dec 2015, at 03:15, Kurt Besig <kbesig at socal.rr.com> wrote:
> 
> The VPS isn't allowing Ports 9001 and 9030
> Should I investigate further getting my iptables up and running or
> just contact the admin and have them allow the ports?


Once you know the correct IPv4 address, try launching Tor again, and give it 20 minutes to check reachability.
If it still complains that it can't reach your ORPort or DirPort, then ask your admin if they need to open ports to a VPS.
(From your previous posts, it looks like the ports are not being blocked on the VPS OS itself.)

Tim

Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP 968F094B

teor at blah dot im
OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20151207/9e7c392d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20151207/9e7c392d/attachment.sig>