Opened 7 years ago

Closed 2 years ago

#8303 closed defect (wontfix)

port.conf error

Reported by: RedStateGreen Owned by: erinn
Priority: Medium Milestone:
Component: Archived/Vidalia Version: Vidalia: 0.2.17
Severity: Normal Keywords: needs-triage, archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I keep getting an error message

Feb 21 16:59:13.335 [Warning] Couldn't open "../../Data/Tor/port.conf.tmp" (../../Data/Tor/port.conf) for writing: No such file or directory
Feb 21 16:59:13.335 [Warning] Writing ../../Data/Tor/port.conf failed: No such file or directory

Every time I try to start Tor. It worked once fine but now I can't get it to work.

Thanks for your help.

Child Tickets

Change History (10)

comment:1 Changed 7 years ago by nickm

How are you launching Tor?

comment:2 Changed 7 years ago by nickm

Component: TorVidalia
Owner: set to chiiph

comment:3 Changed 7 years ago by RedStateGreen

I'm launching it from a shortcut I put on the desktop.

When I launch it directly from the directory it seems to connect but then I get this error:

Unable to find the proxy server
Firefox is configured to use a proxy server that can't be found.

I closed Firefox and launched Tor again and got the same error.

comment:4 Changed 7 years ago by arma

Component: VidaliaTor bundles/installation
Owner: changed from chiiph to erinn
Version: Vidalia: 0.2.21

(This is pretty clearly not a Vidalia bug.)

What exactly are you running? Is it the Tor program? Or the script called 'Start Tor Browser'?

You should be running the start-tor-browser script.

comment:5 Changed 7 years ago by RedStateGreen

It says "start Tor browser". It is an application (.exe) in the Tor Browser folder.

comment:6 Changed 7 years ago by RedStateGreen

Was told by someone here it was the fault of the antivirus. Tried to contact Malware bytes and was told it was due to malicious websites. Avast never replied. Looks like I am going to have to uninstall this.

comment:7 Changed 6 years ago by erinn

Keywords: needs-triage added

comment:8 Changed 6 years ago by cypherpunks

Component: Tor bundles/installationVidalia
Version: Vidalia: 0.2.17

Connection Error
Vidalia can't figure out how to talk to Tor because it can't access this file: /path/to/data/directory/port.conf

Dec 17 03:48:30.299 [Warning] Couldn't open "../Data/port.conf.tmp" (../Data/port.conf) for writing: No such file or directory
Dec 17 03:48:30.299 [Warning] Writing ../Data/port.conf failed: No such file or directory

I see the above error message using Vidalia bridge bundle 0.2.21 and Tor 0.2.4.23. It appears to be related to setting ControlPort to auto. When ControlPort is set to auto, Vidalia looks for port.conf (a file it uses to determine the control port) in the Tor data directory, but Tor doesn't write this file by default.

As a workaround, change ControlPort from auto to 9051 (or any other unused port). You can do this by goint into Vidalia's Settings menu, clicking the Advanced button, and unchecking the box "Configure ControlPort automatically".

In order to fix this, I added the line "ControlPortWriteToFile /path/to/data/directory/port.conf" to my torrc without quotes. I then started Tor by itself. This caused Tor to successfully write a control port file to my Tor data directory.

However, Vidalia continued to give the same error if I started Vidalia and Tor together. This appears to be related to bug 3463, which was fixed in Vidalia 0.2.17. Bug 3463 says Vidalia deletes port.conf if it exists, so that an old control port from a previous run is not used.

I'm not sure how to get Vidalia to use Tor's control port automatically. Once the control port is set by Tor, Tor writes a control port file. Vidalia then deletes the control port file and tries to read it, in that order. This obviously fails, which means Vidalia doesn't learn Tor's new control port and never successfully connects to Tor.

I've also noticed other bugs regarding setting ControlPort to auto (outside the scope of this one), so I would recommend disabling that feature and just setting ControlPort manually.

The default port 9051 should work fine unless you have something already using that port, in which case you can easily change it to something else.

If someone who knows more about Tor could look at this for me, I would really appreciate it.

comment:9 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:10 Changed 2 years ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.