[tor-relays] . obfsproxy not working on bridge relay

[Jan Nielsen]

I believe that error means obfsproxy was either not installed correctly or
your torrc is not pointing to the correct location. Follow the below link's
instructions.

Also, a quick google search for that error provided resukts from this
mailing list. Follow its instructions as well.

https://lists.torproject.org/pipermail/tor-relays/2014-February/003892.html
On Oct 8, 2014 6:00 AM, <tor-relays-request at lists.torproject.org> wrote:

> Send tor-relays mailing list submissions to
>         tor-relays at lists.torproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> or, via email, send a message with subject or body 'help' to
>         tor-relays-request at lists.torproject.org
>
> You can reach the person managing the list at
>         tor-relays-owner at lists.torproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tor-relays digest..."
>
> Today's Topics:
>
>    1. obfsproxy not working on bridge relay (jchase)
>    2. Re: obfsproxy not working on bridge relay (George Kadianakis)
>
>
> ---------- Forwarded message ----------
> From: jchase <jchase at riseup.net>
> To: tor-relays at lists.torproject.org
> Cc:
> Date: Wed, 08 Oct 2014 10:36:39 +0000
> Subject: [tor-relays] obfsproxy not working on bridge relay
> Hi,
> Due to m limited bandwidth I've decided to turn my relay into a bridge.
> I seem to have everything right except if I restart tor I get a warning
> that "managed proxy obfsproxy is 'closed'". I'm sure this has come up in
> the past but I can find it in the archives.
> In torrc I have:
> SocksPort 0
> ORPort 9001
> Exitpolicy reject *:*
> Log notice file /var/log/tor/notices.log
> Contact info []
> Nickname rasptorholland
> BridgeRelay 1
> ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
> ServerTransportListenAddr obfs3 0.0.0.0:9030
> DisableDebuggerAttachment 0
>
> Both ports are forwarded, though I can't find proof that tor is actually
> using port 9030.
>
> Any suggestions?
> -J. Chase
>
>
>
>
> ---------- Forwarded message ----------
> From: George Kadianakis <desnacked at riseup.net>
> To: tor-relays at lists.torproject.org
> Cc:
> Date: Wed, 08 Oct 2014 11:41:22 +0100
> Subject: Re: [tor-relays] obfsproxy not working on bridge relay
> jchase <jchase at riseup.net> writes:
>
> > Hi,
> > Due to m limited bandwidth I've decided to turn my relay into a bridge.
> > I seem to have everything right except if I restart tor I get a warning
> > that "managed proxy obfsproxy is 'closed'". I'm sure this has come up in
> > the past but I can find it in the archives.
> > In torrc I have:
> > SocksPort 0
> > ORPort 9001
> > Exitpolicy reject *:*
> > Log notice file /var/log/tor/notices.log
> > Contact info []
> > Nickname rasptorholland
> > BridgeRelay 1
> > ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
> > ServerTransportListenAddr obfs3 0.0.0.0:9030
> > DisableDebuggerAttachment 0
> >
>
> Hello,
>
> how did you install obfsproxy? Which installation instructions did you
> follow? Seems like you didn't follow:
> https://www.torproject.org/projects/obfsproxy-instructions.html.en
>
> What happens if you run '/usr/bin/obfsproxy managed' in a terminal?
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20141009/478ccec2/attachment.html>