Opened 14 years ago

Last modified 7 years ago

#208 closed defect (Not a bug)

With ORPort uncommented, Tor shuts down immediately

Reported by: rumplesnitz Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.1.8-alpha
Severity: Keywords:
Cc: rumplesnitz Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

*I'm and end-user, not a code-writer, allright?*

I'm my own system administrator on my home-based wireless DSL network running
Windows XP Pro SP2 on a PIII 1200 MHz 512 MB mem laptop remote from the primary
desktop station; all firewall, popup blocker, and anti-virus software on this
laptop is turned off; Tor works fine as client but when I uncomment ORPort in
the Torrc and re-start Tor to attempt Server mode, all I get is a flash of the
startup box and then it is gone, as in shut down. I am not running in Daemon
mode, and my applications and processes lists do not show Tor running after
this happens (they do track Tor in client mode). I uninstalled 0.1.1.8 and
installed 0.1.1.9 tonight and get exactly the same behavior. I've looked for
other similar reports but this seems to be an isolated complaint, so I guess
the problem is on my end. I'd like to throw a little BW y'all's way - this
sounds like a worthy project and according to my system I've got 11 MB/s to
play with - but I'm just not technically savvy enough to pull this off alone.

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Child Tickets

Change History (9)

comment:1 Changed 14 years ago by arma

Yeah. I'm afraid our interface on Windows is crappy. We're hoping somebody fixes that one day.

You might try the torcp program. See the FAQ entry on running your Tor in the system tray.

You might also try enabling logging to a file (see the FAQ entry), so it tells you what it's
complaining about before it disappears.

Probably your problem is that you need to do more than just uncomment ORPort. You need to set
a nickname, and fill in the rest of the stuff in the file that says it's required.

comment:2 Changed 14 years ago by rumplesnitz

I'll try the torcp program. I'll also read up some more and see if I can get
myself up to speed. I tried logging to a file as per the FAQ, but haven't yet
been able to find the log, if it was generated (I'm pretty sure I'm looking in
the right place (where the torrc tells me to look), and I've even run several
system searches - no joy). I assigned a nickname and provided my name and
e-mail on those lines also, maybe I'm screwing up the format somehow. I'm
trying real hard to read and follow the instructions and FAQ insights.

At any rate, my problem doesn't seem to be a Tor bug, does it? I'll play with
it some more, I like puzzles that challenge me to learn new stuff. Thanks!
Keep up the good work. Those Chinamen need us!

comment:3 Changed 14 years ago by arma

Another option is to open a dos window ("start -> run -> command.com") and then run torxxx.exe directly.
It will spit out whatever errors it has, and you'll still be able to see them.

The reason it's disappearing right now is because Windows opens a window for it, then decides that it's
done so it closes the window.

comment:4 Changed 14 years ago by euleralves

Great tip open a dos window. Here, there were identical problem. The DOS message is:

Nov 20 08:35:44.375 [warn] Address 'XXXX' resolves to private IP '10.0.0.2'. T
or servers that use the default DirServers must have public IP addresses.

I set Address line in torrc file to my real ip and the dos command run!
But I have dinamic ip. There is other way of set Address line than no-ip? I am behind hardware firewall in a home LAN.

comment:5 Changed 14 years ago by arma

no-ip or dyndns should work fine, but your problem seems to be that your no-ip address
was resolving to the private IP 10.0.0.2. This is not routable from the Internet, so
it's not going to be useful. You should configure your no-ip correctly and things should
work fine.

comment:6 Changed 14 years ago by nickm

Did the fix work?

comment:7 Changed 14 years ago by nickm

Okay, it looks like the TorCP+Tor bundle makes it easier to notice that your configuration
is broken. I'm closing this as not-a-bug.

comment:8 Changed 14 years ago by nickm

flyspray2trac: bug closed.

comment:9 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.