Hej, [WARNING - if you don't want to see another Tor relay get going stop reading now.] After installing Tor on a VPS running Ubuntu 12.04.4 LTS it reports [warn] Your server (173.208.211.179:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address,... The VPS operator is trying his best but says the ports are open and is asking others. In the meantime does anyone have anything to offer? Robert
Hey, usually this problem is due to a wrong set fqdn hostname and hosts file. In /etc/hostname set the hostname: relay.example.com and run the command "hostname relay.example.com" In /etc/hosts change the current hostname 127.0.0.1 current.example.com to: 127.0.0.1 relay.example.com Though this is obvious run end edit with sudo and replace the example with the real hostname. Sebastian Am 18.01.2014 11:22, schrieb I:
Hej,
[WARNING - if you don't want to see another Tor relay get going stop reading now.]
After installing Tor on a VPS running Ubuntu 12.04.4 LTS it reports
[warn] Your server (173.208.211.179:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address,...
The VPS operator is trying his best but says the ports are open and is asking others.
In the meantime does anyone have anything to offer?
Robert
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Sebastian, That's the spirit! To me that feels like the right thinking. In etc/hostname there is just ubuntu. In the details for the VPS the hostname is VM#16 which I can't change there. Therefore what would be correct to put in the etc/hostname file? Is it useful to know that the ip address I PuTTY into is 38.68.15.116 but the one in Tor's log with blocked ports is 173.208.211.179? They traceroute to different places but I can log in through either. Robert
Hey,
usually this problem is due to a wrong set fqdn hostname and hosts file.
In /etc/hostname set the hostname: relay.example.com and run the command "hostname relay.example.com"
In /etc/hosts change the current hostname 127.0.0.1 current.example.com to: 127.0.0.1 relay.example.com
Though this is obvious run end edit with sudo and replace the example with the real hostname.
Sebastian
Am 18.01.2014 11:22, schrieb I:
Hej,
[WARNING - if you don't want to see another Tor relay get going stop reading now.]
After installing Tor on a VPS running Ubuntu 12.04.4 LTS it reports
[warn] Your server (173.208.211.179:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address,...
The VPS operator is trying his best but says the ports are open and is asking others.
In the meantime does anyone have anything to offer?
Robert
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Robert You should set your Address in /etc/tor/torrc to 38.68.15.116. Your configured DirPort and OrPort seems to work for me. Your hostname should be set in a nameserver though your current one (116-15-68-38-static.reverse.queryfoundry.net) is great. Sebastian
Sebastian,
That's the spirit!
To me that feels like the right thinking.
In etc/hostname there is just ubuntu. In the details for the VPS the hostname is VM#16 which I can't change there. Therefore what would be correct to put in the etc/hostname file?
Is it useful to know that the ip address I PuTTY into is 38.68.15.116 but the one in Tor's log with blocked ports is 173.208.211.179? They traceroute to different places but I can log in through either.
Robert -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJS2wzkAAoJELJfPcDoaw7r6FgH+gIOiZKTJlFYyNwNTbwtnNkQ 5Eyu9FFjTkzvmTDXQUVWIl9ZR4IsOzJacobRxATS/BbBymvNBp9fvwGHWMyGtBIt XoJ+khz+2x1eO18CIgFWBvOF3Y/3s+CJtpdDN2/oeX2WXv3fDDm407i5a7oqPDWA e1HiDZ//0b9xz39o6ojq+iC5gzHeP9eZPN+gINOCWQripNwNRdzh+7FfCt/C+MQp VOVVpCBK1xL385TrRqJYOrhJ2KLl+YCzj4XaUQ7HJapxIxB9oykkaWiqe4b8JQS8 0DwpDggrGgPcXjCMtcjQzlXFj9PuOAivmhknchFH/3xKlmLf78rnsUf4GTW6n+E= =v09A -----END PGP SIGNATURE-----
On 18/01/2014 9:22 PM, I wrote:
Hej,
[WARNING - if you don't want to see another Tor relay get going stop reading now.]
After installing Tor on a VPS running Ubuntu 12.04.4 LTS it reports
[warn] Your server (173.208.211.179:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address,...
The VPS operator is trying his best but says the ports are open and is asking others.
In the meantime does anyone have anything to offer?
Robert
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi, Robert. I would try setting your VPS IP as the Address value in torrc. -- syn.bsdbox.co
nano, That fixed it thanks nano. I've learned another piece of the Tor puzzle. Robert
[WARNING - if you don't want to see another Tor relay get going stop reading now.]
After installing Tor on a VPS running Ubuntu 12.04.4 LTS it reports
[warn] Your server (173.208.211.179:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address,...
Hi, Robert.
I would try setting your VPS IP as the Address value in torrc.
participants (3)
-
I -
nano -
Sebastian Bögl