ExitNodes with obfs4 not working

Tor successfully connects with obfs4 bridges but when I add strict ExitNodes to my torrc:

ExitNodes {nl},{de},{fi},{se},{no},{pl},{us},{it},{fr},{es}
StrictNodes 1

Tor cannot connecting and starts echoing [notice] Application request when we haven't used client functionality lately. Optimistically trying known bridges again. in logs.

I don’t know if this problem is caused by using obfs4 because I cannot connect to tor without bridges (because of censorship).

Looks like the bridges you have configured your tor to use are either offline and/or there are some potential errors in the torrc.

Please share the complete torrc as that might help in diagnosing what’s going wrong.

Bridges I use are working when I remove ExitNodes and StrictNodes lines.

My current torrc:

SocksPort 127.0.0.1:9015
HTTPTunnelPort 127.0.0.1:9018

UseBridges 1

Bridge obfs4 ...
Bridge obfs4 ...

# ExitNodes {nl},{de},{fi},{se},{no},{pl},{us},{it},{fr},{es}
# StrictNodes 1

ServerDNSResolvConfFile resolv.conf
AvoidDiskWrites 1

Bridge information is replaced with ...

When I uncomment ExitNodes and StrictNodes lines, tor stops connecting. When I comment them back, tor connects successfully.

Does your tor have path to geoip and geoip6?

Already found solution on NTC forum: Tor: ExitNodes with obfs4 not working - Censorship circumvention methods & software - NTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.