On Fri, Apr 11, 2014 at 9:58 AM, Cyrus <[email protected]> wrote: > This problem seems to have returned, though now the clock is set properly.
Your clock will drift unless you use ntpd, ntpdate, or some other method like whonix uses. > Apr 11 13:56:33.000 [notice] Tor 0.2.4.20 (git-3cb5c70beec5bf46) 2.4.21 is out. And for some reason the libevent and ssl version didn't show up in this log. > OpenSSL 1.0.1 or later, but wit > uilding openssl with such support (using the enable-ec_nistp_64_gcc_128 > ld make ECDH much faster. This openssl option is actually called '[no-]ec_nistp_64_gcc_128', there is no 'enable' in the string. Someone can trac that. > Apr 11 13:56:38.000 [notice] Your Guard Unnamed > ($A0306CADEE237E9A3CD766F9858FC73EE8D70CF2) is failing > ($E2CFC6A603232D0EA3452B80170D7257417DC7A1) is failing > Can someone please assist? All my services are down. You probably don't want to go around posting your guards and node id's/ip's, otherwise you might as well run it on clearnet. There's not enough to go on. Just look over your configs, your HiddenServicePort accessible locally, webserver bound to the interface, etc. -- tor-talk mailing list - [email protected] To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
