Re: [tor-relays] VPS ports impassable

2014-01-19 Thread I
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.17

Re: [tor-relays] VPS ports impassable

2014-01-18 Thread nano
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. Plea

Re: [tor-relays] VPS ports impassable

2014-01-18 Thread Sebastian Bögl
-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 gre

Re: [tor-relays] VPS ports impassable

2014-01-18 Thread I
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

Re: [tor-relays] VPS ports impassable

2014-01-18 Thread Sebastian Bögl
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.

[tor-relays] VPS ports impassable

2014-01-18 Thread 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, ad