Okay, your remark was exactly what I needed; my plugin path was wrong for obfs4proxy. I wasn't expecting tor to be so happy without the plugin.
Works now - Thanks! --Torix Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, June 10, 2020 10:36 PM, <[email protected]> wrote: > Here is what I have for my torrc: > > Log notice file /var/log/tor/notices.log > DisableDebuggerAttachment 0 > ControlPort 9051 > CookieAuthentication 1 > DataDirectoryGroupReadable 1 > CookieAuthFileGroupReadable 1 > ExtORPortCookieAuthFileGroupReadable 1 > CacheDirectoryGroupReadable 1 > CookieAuthFile /var/log/tor/control_auth_cookie > ORPort 11340 > ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy > ServerTransportListenAddr obfs4 0.0.0.0:9730 > > Enable Extended ORPort > > ======================= > > ExtORPort auto > Nickname Aramis56 > ContactInfo torix[aT===]protonmail<dOT___>com > > ExitRelay 0 > IPv6Exit 0 > RunAsDaemon 1 > BridgeRelay 1 > > Hope I'm just missing a line here... > > --Torix > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Wednesday, June 10, 2020 10:27 PM, Philipp Winter [email protected] > wrote: > > > On Wed, Jun 10, 2020 at 10:18:45PM +0000, [email protected] wrote: > > > > > But when I use the bridge reach-ability test at > > > https://bridges.torproject.org/scan/ > > > It fails to find my obfs4 port. > > > > Your bridge doesn't seem to run obfs4. What does your torrc look like? > > tor-relays mailing list > > [email protected] > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays _______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
