I have no error from Apparmor and I dont believe obfs4 proxy is the issue as I have obfs4 installed and confirmed running
dpkg -l | grep obfs4 ii obfs4proxy 0.0.7-4
ps ax | grep obfs4 5501 ? Sl 0:01 /usr/bin/obfs4proxy
netstat -nap | grep obfs4 tcp 0 0 X.X.X.X:12345 0.0.0.0:* LISTEN 5501/obfs4proxy
Tor logs
Apr 18 17:00:33 pi Tor[5497]: Registered server transport 'obfs4' at 'X.X.X.X:12345'
torrc
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 X.X.X.X:12345
[ https://bridges.torproject.org/scan/ ]( https://bridges.torproject.org/scan/ )
also reports my ORPort is reachable via IPv4 and IPV6
Tor logs
Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort [X:Y:Z::A]:993 is reachable from the outside. Excellent. Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort A.B.C.D:993 is reachable from the outside. Excellent. Publishing server descriptor.
What am I missing ?
Thanks again
Ross
Probably because obfs4 is not installed or not running properly.> Check your logs for obfs4 errors, and for Apparmor error messages as well.> On Mon, Apr 18, 2022 at 09:07, Ross Camm ross@whyza.net wrote:> I have been up and running with my Tor Bridge for a number of months now, yet Tor Metrics reports that the Bridge Distribution Mechanism for my server is stuck on 'none'.>> Consequently I see no incoming connections to my Bridge.>> I have tried altering the following>> BridgeRelay 1>> PublishServerDescriptor bridge> BridgeDistribution moat>> with no success.>> The mechanism is always none....and I have left the changes for a week to see if Metrics updates to no avail.>> I have a static IPv4 address and functional IPv6 and have confirmed my ports are publicly accessible for both protocols>> Self-testing indicates your ORPort [XXXX:XXXX:XXXX::XXX]:993 is reachable from the outside. Excellent.> Self-testing indicates your ORPort XXX.XXX.XXX.XXX:993 is reachable from the outside. Excellent. Publishing server descriptor.>> I am running raspberry pi os buster which had an obsolete Tor version.>> I subsequently upgraded and stay up to date with the latest bullseye version via bullseye backports,>> Currently Tor 0.4.6.10-1~bpo10+1>> Any ideas of why my servers Bridge Distribution Mechanism is always reported and behaving as none ?>> Thanks in advance ;)>> Ross
On Wednesday, April 20, 2022 10:22:54 AM CEST Ross Camm wrote:
I have no error from Apparmor and I dont believe obfs4 proxy is the issue as I have obfs4 installed and confirmed running
dpkg -l | grep obfs4 ii obfs4proxy 0.0.7-4
ps ax | grep obfs4 5501 ? Sl 0:01 /usr/bin/obfs4proxy
netstat -nap | grep obfs4 tcp 0 0 X.X.X.X:12345 0.0.0.0:* LISTEN 5501/obfs4proxy
Tor logs
Apr 18 17:00:33 pi Tor[5497]: Registered server transport 'obfs4' at 'X.X.X.X:12345'
torrc
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 X.X.X.X:12345
[ https://bridges.torproject.org/scan/ ]( https://bridges.torproject.org/scan/ )
also reports my ORPort is reachable via IPv4 and IPV6
Tor logs
Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort [X:Y:Z::A]:993 is reachable from the outside. Excellent. Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort A.B.C.D:993 is reachable from the outside. Excellent. Publishing server descriptor.
What am I missing ?
Just to test, not 'PublishServerDescriptor bridge' try 1 (default):
BridgeRelay 1 PublishServerDescriptor 1 BridgeDistribution moat
If that doesn't work I would try the default 'any' here too: BridgeDistribution any
tor-relays@lists.torproject.org