2

I'm relatively new to Tor, having read about it in my newspaper so I thought I'd give it a go. Having read about relays and bridges and so forth I thought I'd try it out.

I managed to get a relay running by editing the Torrc file like so,

BandwidthRate 204800
ContactInfo [email protected]
DataDirectory C:\Users\Martin\Desktop\Tor Browser\Data\Tor
ExitPolicy reject *:*
GeoIPFile C:\Users\Martin\Desktop\Tor Browser\Data\Tor\geoip
GeoIPv6File C:\Users\Martin\Desktop\Tor Browser\Data\Tor\geoip6
Nickname HAVANASUN
ORPort 443

Then I tried to set it up as a bridge. I entered these lines instead which I found on-line.

SocksPort 0
ORPort 443
BridgeRelay 1
Exitpolicy reject *:*

Won't connect! I'm sure it's something simple but to be honest I'm not all that sharp with computers.

Can some kind soul help me out please?

PS, I'm using the Tor Browser, not Vidalia.

Thanks chaps

Improve this question
5
  • What errors are you experiencing?
    – cubecubed
    Aug 30, 2014 at 17:17
  • Thank you, if I use the configuration I showed you Tor simply won't connect. I avoided using the Vidalia bundle as the Tor site recommended using the browser and editing the torrc file. What I'm after chaps is a simple walk-through of how to allow a bridge to run whilst still using the browser. Thanks
    – user3513
    Aug 31, 2014 at 18:46
  • Do you have DirPort enabled? If yes, what port did you set it? Are there any other services running on port 443? I think you can't just simply set the ORPort to 443. You have to use Port forwarding instead. try using another port.
    – DerTorSteher
    Oct 1, 2014 at 11:36
  • Is your bridge achievable from the net? Did you setted up port forwarding?
    – user3524
    Nov 30, 2014 at 10:01
  • Slightly off topic: Note that ContactInfo is public; if you're redacting it here, you should be aware that it will be viewable to anyone looking through the list of relays. Just wanted to make sure you're aware.
    – user5
    Feb 2, 2015 at 17:22

1 Answer 1

Reset to default
2

The reason that Tor isn't working is very simple. When you added the bridge configuration lines, there were duplicate lines that already existed in your relay configuration lines. Mainly, it is ORPort 443 duplication is what is causing the issue, because Tor will try to listen to this port a second time and will find it occupied, exiting thus with an error!

Your full torrc file should look like this:

BandwidthRate 204800 ContactInfo [email protected] DataDirectory C:\Users\Martin\Desktop\Tor Browser\Data\Tor ExitPolicy reject *:* GeoIPFile C:\Users\Martin\Desktop\Tor Browser\Data\Tor\geoip GeoIPv6File C:\Users\Martin\Desktop\Tor Browser\Data\Tor\geoip6 Nickname HAVANASUN ORPort 443 SocksPort 0 BridgeRelay 1

and that will hopefully solve your problem.

Improve this answer
1
  • and no need to remove SocksPort - it's a common role coexistance
    – Alexey Vesnin ♦
    Jan 29, 2016 at 17:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .