Jeroen, Thank you. It did that but I can't see a change.
The VPS person said it is set to UTC. Previously on another VPS it was another relay in the ?circuit which had the time difference. Now I see this:- Our clock is 6 hours, 25 minutes behind the time published in the consensus network status document (2014-01-14 19:00:00 UTC). Tor needs an accurate clock... Jan 14 07:34:57.000 [notice] Bootstrapped 5%: Connecting to directory server. Jan 14 07:34:57.000 [notice] Bootstrapped 10%: Finishing handshake with directory server. Jan 14 07:34:57.000 [notice] We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make y$ Jan 14 07:34:57.000 [notice] To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features. Jan 14 07:34:57.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection. Jan 14 07:34:58.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus. Jan 14 07:34:58.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor. Jan 14 07:34:58.000 [notice] Bootstrapped 50%: Loading relay descriptors. Jan 14 07:37:11.000 [notice] New control connection opened. whereat it stays. Any ideas, please. Robert >> Does anyone know how to get past this to get the exit running on Debian >> 6, please? >> >> Our clock is 6 hours, 48 minutes behind the time published in the >> consensus network status document (2014-01-14 11:00:00 UTC). > > apt-get install ntp > > would be a good start. > > Greets, > _______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
