Opened 14 years ago

Last modified 14 years ago

#262 closed defect (Won't fix)

Tor starting though not connecting on restart

Reported by: anonimouse Owned by:
Priority: Low Milestone:
Component: Tor - Tor Control Panel Version:
Severity: Keywords:
Cc: anonimouse Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tor 0.1.1.14 on Win2000 SP4, when machine starts from cold or just a restart, tor starts, yet it cannot connect to the
outside world until i send a kill signal then restart tor manually, even though there is a green tick in the torCP tray.
Nothing appears in the log either. Privoxy gives the 503 too.
Once killed it then connects and server starts and says accepting connections and orport reachable etc. and all back to normal

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (4)

comment:1 Changed 14 years ago by nickm

I don't understand, could you be more specific about what

you mean by all of this? MAtt: since he mentions a green tick,
i'm guessing this is a torcp problem. Reassigning.

comment:2 Changed 14 years ago by edmanm

I don't understand either.

TorCP will show a green tick if it sees that Tor is running and TorCP has connected to its control port,
which usually means all is well with Tor and TorCP.

How are you sending this kill signal? Through TorCP? If so, then that means that Tor is indeed running
and able to talk to TorCP.

What do you mean by "restart tor manually"? Do you mean running it in a console window? Are you trying
to run Tor as a service? Have you tried the latest Tor 0.1.1.15-rc?

Also, if you're convinced that TorCP is broken, you might try Vidalia (www.vidalia-project.net).
It's new so it could have some of its own problems too, but it will probably work better for you.

comment:3 Changed 14 years ago by edmanm

Any update, original reporter? Did trying Vidalia help? Or can you provide some
more details about your problem?

comment:4 Changed 13 years ago by edmanm

flyspray2trac: bug closed.
I'm assuming that this was due to a broken TorCP and that using Vidalia worked, since the reporter disappeared.

Note: See TracTickets for help on using tickets.