[tor-talk] Tor hidden services not working

[Cyrus]

FYI: It seemed to take the 24 hours the clock was out to go back to
normal. I think I upset the network with the clock error. Unlike other
clock errors, it didn't immediately show in the log. I think that is
because it was exactly 24 hours out, and the time was correct but not
the date.

On 04/12/2014 09:19 AM, grarpamp wrote:
> On Fri, Apr 11, 2014 at 9:58 AM, Cyrus <cyrus_the_great at riseup.net> 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.
I use ntp, but the clock was far enough out that I had to set it
manually. I did a typo on the date, and set it 24 hours exactly in the
future.

> 
>> 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.
It's the Tor build in Gentoo portage. They must be behind, that error
seems new with the latest OpenSSL.

> 
>> 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.
I'll keep that in mind in the future, I thought it might be useful. I
cleared the datadir to stop using them right after posting to be safe.

> 
> There's not enough to go on. Just look over your configs,
> your HiddenServicePort accessible locally, webserver
> bound to the interface, etc.
Well, it's all working now. I checked all this to be sure, and the
webserver was working and Tor was forwarding to the right ports.
Actually, nothing changed from a working setup from the date.