Your server has not managed to confirm reachability for its ORPort(s)

Support Relay Operator
1

Hello,
I am attempting to set up a bridge to help contribute.
I am a gnu/linux CLI hobbyist but I lack knowledge in networking so please break it down to me barny-style…

I get the following message when attempting to initiate my bridge:

Your server has not managed to confirm reachability for its ORPort(s) at 89.187.175.144:8916.

Here is my /etc/tor/torcc file:

BridgeRelay 1

# Replace "TODO1" with a Tor port of your choice.
# This port must be externally reachable.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
Address
ORPort 8916 IPv4Only
AddressDisableIPv6 1

ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy

# Replace "TODO2" with an obfs4 port of your choice.
# This port must be externally reachable and must be different from the one specified for ORPort.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ServerTransportListenAddr obfs4 0.0.0.0:443

# Local communication port between Tor and obfs4.  Always set this to "auto".
# "Ext" means "extended", not "external".  Don't try to set a specific port number, nor listen on 0.0.0.0.
ExtORPort auto

# Replace "<address@email.com>" with your email address so we can contact you if there are problems with your bridge.
# This is optional but encouraged.
ContactInfo <private>

# Pick a nickname that you like for your bridge.  This is optional.
Nickname macrohumanity

BandwidthRate 1 MBytes
PortForwarding 1

Here is the latest journalctl -e -u tor@default output from my most recent attempt:

Sep 12 22:36:55 macrohumanity Tor[945]: Opened OR listener connection (ready) on 0.0.0.0:8916
Sep 12 22:36:55 macrohumanity Tor[945]: Opening Extended OR listener on 127.0.0.1:0
Sep 12 22:36:55 macrohumanity Tor[945]: Extended OR listener listening on port 46001.
Sep 12 22:36:55 macrohumanity Tor[945]: Opened Extended OR listener connection (ready) on 127.0.0.1:46001
Sep 12 22:36:57 macrohumanity Tor[945]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 12 22:36:57 macrohumanity Tor[945]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 12 22:36:57 macrohumanity Tor[945]: Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Sep 12 22:36:58 macrohumanity Tor[945]: Your Tor server's identity key  fingerprint is <private>
Sep 12 22:36:58 macrohumanity Tor[945]: Your Tor bridge's hashed identity key  fingerprint is <private>
Sep 12 22:36:58 macrohumanity Tor[945]: Your Tor server's identity key <private> fingerprint is <private>
Sep 12 22:36:58 macrohumanity Tor[945]: You can check the status of your bridge relay at https://bridges.torproject.org/status?id=<private>
Sep 12 22:36:58 macrohumanity Tor[945]: Bootstrapped 0% (starting): Starting
Sep 12 22:36:58 macrohumanity Tor[945]: Starting with guard context "default"
Sep 12 22:37:11 macrohumanity Tor[945]: Signaled readiness to systemd
Sep 12 22:37:11 macrohumanity systemd[1]: Started Anonymizing overlay network for TCP.
Sep 12 22:37:11 macrohumanity Tor[945]: Registered server transport 'obfs4' at '[::]:443'
Sep 12 22:37:12 macrohumanity Tor[945]: Bootstrapped 5% (conn): Connecting to a relay
Sep 12 22:37:12 macrohumanity Tor[945]: Opening Socks listener on /run/tor/socks
Sep 12 22:37:12 macrohumanity Tor[945]: Opened Socks listener connection (ready) on /run/tor/socks
Sep 12 22:37:12 macrohumanity Tor[945]: Opening Control listener on /run/tor/control
Sep 12 22:37:12 macrohumanity Tor[945]: Opened Control listener connection (ready) on /run/tor/control
Sep 12 22:37:12 macrohumanity Tor[945]: Unable to find IPv4 address for ORPort 8916. You might want to specify IPv6Only to it or set an explicit address or set Address.
Sep 12 22:37:12 macrohumanity Tor[945]: Bootstrapped 10% (conn_done): Connected to a relay
Sep 12 22:37:12 macrohumanity Tor[945]: Bootstrapped 14% (handshake): Handshaking with a relay
Sep 12 22:37:12 macrohumanity Tor[945]: External address seen and suggested by a directory authority: 89.187.175.144
Sep 12 22:37:12 macrohumanity Tor[945]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Sep 12 22:37:12 macrohumanity Tor[945]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Sep 12 22:37:12 macrohumanity Tor[945]: Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Sep 12 22:37:12 macrohumanity Tor[945]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Sep 12 22:37:12 macrohumanity Tor[945]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Sep 12 22:37:13 macrohumanity Tor[945]: Bootstrapped 100% (done): Done
Sep 12 22:38:12 macrohumanity Tor[945]: Now checking whether IPv4 ORPort 89.187.175.144:8916 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Sep 12 22:57:12 macrohumanity Tor[945]: Your server has not managed to confirm reachability for its ORPort(s) at 89.187.175.144:8916. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Sep 12 23:17:12 macrohumanity Tor[945]: Your server has not managed to confirm reachability for its ORPort(s) at 89.187.175.144:8916. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

Notes:

  • Have tried searching this topic for several hours on the StackExchange and Tor forum but all of the resolutions are helpful but do not work.
  • I searched my ISP blocked port list. 443 and 8916 are not blocked.
  • I have configured my local firewall to allow incoming and outging traffic from ports 443 and 8916
    *I have also set up a static DHCP address and NAT port-forwarding for ports 443 and 8916 on my DD-WRT router

My biggest worry is that I set up the static DHCP address and NAT port-forwarding incorrectly.
I used my computers MAC address, my computers hostname and internal/private IP address when setting up the static DHCP.
Please see the attached image for a screenshot of my DD-WRT port-forwarding set up in which I used my internal\private IP.

port-forwarding
port-forwarding744×289 20.3 KB

Any other ideas as to why I get the “Your server has not managed to confirm reachability for its ORPort(s) at 89.187.175.144:8916.” message?

2

I would remove “PortForwarding 1” from the torrc config to see if it works.

3

Given the logs, and UI for that port forward, im going to assume your running a relay on a machine on a private network behind a firewalled router.
Note this line:

Sep 12 22:36:55 macrohumanity Tor[945]: Opened OR listener connection (ready) on 0.0.0.0:8916

This indicates the machine is listening in the blind, sometimes Tor doesn’t like this. Why? Dunno. Just wonky sometimes.
Change this line in your torrc file to reflect your external public facing IP address, if its static all the better, if not, a Dynamic DNS solution will also work.
w

ServerTransportListenAddr obfs4 0.0.0.0:443

NoIP offers single hostnames for free, Ive used them for my bridge before. Works great.

The second issue I see right off the bat, is in the forwarding settings. The TLDR is you dont want to specify an internal port for forwarding. Setting 8916 FROM is fine, but replace the PORT TO 8916 with either a 0, or just blank out that line.
The reason you dont want an internal port specified is it may cause some funky interactions if your not just passing the traffic through another firewall. Blanking or zeroing it out lets the router serve as many sockets as your relay will need internally and only accept connections externally on 8916, which is what you want. Probably wanna do the same thing with 443 tbh.

You should probably edit the Address line on your torrc to reflect your external IP address or the Dynamic Hostname I mentioned earlier. Leaving that blank will force Tor to attempt to figure out its own IP address, which its sometimes shitty at.

4

First, I looked up your username and that is pretty cool.

My DD-WRT does not have it’s firewall enabled but the computer that I plan to run the bridge on is a Ubuntu machine, which uses ufw.
Here is the output of sudo ufw status , if you are curious:
ufw13SEP

I changed ServerTransportListenAddr obfs4 0.0.0.0:443 to ServerTransportListenAddr obfs4 89.187.175.144:443.
I can see this being an issue in the future because I suppose that my public-facing IP stays constant… until I disable or change the active OpenVPN Client that is currently running on my DD-WRT router. I will use my current public IP to try to remedy the situation and go from there. Will take note of NoIP.

I attempted to replace PORT TO 8916 and PORT TO 443 with zeros or blanks and got this message:
“Port value is out of range [1-65535].”
Any ideas?

By “external IP address”, I assume that you mean public-facing IP address.
Will do! I replaced Address with Address 89.187.175.144

Here is my updated etc/tor/torrc file:

BridgeRelay 1

# Replace "TODO1" with a Tor port of your choice.
# This port must be externally reachable.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
# Note to self: Pulic IPv4 Address: 174.63.120.155
# Alternative public IP?: 127.0.1.1
Address 89.187.175.144
ORPort 8916 IPv4Only
AddressDisableIPv6 1

ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy

# Replace "TODO2" with an obfs4 port of your choice.
# This port must be externally reachable and must be different from the one specified for ORPort.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
# Robbie's backup port: 3818
ServerTransportListenAddr obfs4 89.187.175.144:443

# Local communication port between Tor and obfs4.  Always set this to "auto".
# "Ext" means "extended", not "external".  Don't try to set a specific port number, nor listen on 0.0.0.0.
ExtORPort auto

# Replace "<address@email.com>" with your email address so we can contact you if there are problems with your bridge.
# This is optional but encouraged.
ContactInfo <1rcummin@protonmail.com>

# Pick a nickname that you like for your bridge.  This is optional.
Nickname macrohumanity

BandwidthRate 1 MBytes

I also removed PortForwarding 1 , which was suggested by saxon above.

Here is the latest journalctl -e -u tor@default output:

Sep 13 18:40:30 macrohumanity systemd[1]: Starting Anonymizing overlay network for TCP...
Sep 13 18:40:30 macrohumanity tor[942]: Sep 13 18:40:30.838 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Sep 13 18:40:30 macrohumanity tor[942]: Sep 13 18:40:30.838 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Sep 13 18:40:30 macrohumanity tor[942]: Sep 13 18:40:30.839 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 13 18:40:30 macrohumanity tor[942]: Sep 13 18:40:30.839 [notice] Read configuration file "/etc/tor/torrc".
Sep 13 18:40:30 macrohumanity tor[942]: Sep 13 18:40:30.848 [notice] Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this by setting MaxMemInQueues by hand.
Sep 13 18:40:30 macrohumanity tor[942]: Configuration was valid
Sep 13 18:40:30 macrohumanity tor[947]: Sep 13 18:40:30.999 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Sep 13 18:40:30 macrohumanity tor[947]: Sep 13 18:40:30.999 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Sep 13 18:40:30 macrohumanity tor[947]: Sep 13 18:40:30.999 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 13 18:40:30 macrohumanity tor[947]: Sep 13 18:40:30.999 [notice] Read configuration file "/etc/tor/torrc".
Sep 13 18:40:31 macrohumanity tor[947]: Sep 13 18:40:31.018 [notice] Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this by setting MaxMemInQueues by hand.
Sep 13 18:40:31 macrohumanity tor[947]: Sep 13 18:40:31.021 [notice] Opening Socks listener on 127.0.0.1:9050
Sep 13 18:40:31 macrohumanity tor[947]: Sep 13 18:40:31.021 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Sep 13 18:40:31 macrohumanity tor[947]: Sep 13 18:40:31.021 [notice] Opening OR listener on 0.0.0.0:8916
Sep 13 18:40:31 macrohumanity tor[947]: Sep 13 18:40:31.021 [notice] Opened OR listener connection (ready) on 0.0.0.0:8916
Sep 13 18:40:31 macrohumanity tor[947]: Sep 13 18:40:31.021 [notice] Opening Extended OR listener on 127.0.0.1:0
Sep 13 18:40:31 macrohumanity tor[947]: Sep 13 18:40:31.021 [notice] Extended OR listener listening on port 41117.
Sep 13 18:40:31 macrohumanity tor[947]: Sep 13 18:40:31.021 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:41117
Sep 13 18:40:31 macrohumanity Tor[947]: We compiled with OpenSSL 30000020: OpenSSL 3.0.2 15 Mar 2022 and we are running with OpenSSL 30000020: 3.0.2. These two versions should be binary compatible.
Sep 13 18:40:31 macrohumanity Tor[947]: Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Sep 13 18:40:31 macrohumanity Tor[947]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Sep 13 18:40:31 macrohumanity Tor[947]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 13 18:40:31 macrohumanity Tor[947]: Read configuration file "/etc/tor/torrc".
Sep 13 18:40:31 macrohumanity Tor[947]: Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this by setting MaxMemInQueues by hand.
Sep 13 18:40:31 macrohumanity Tor[947]: Opening Socks listener on 127.0.0.1:9050
Sep 13 18:40:31 macrohumanity Tor[947]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Sep 13 18:40:31 macrohumanity Tor[947]: Opening OR listener on 0.0.0.0:8916
Sep 13 18:40:31 macrohumanity Tor[947]: Opened OR listener connection (ready) on 0.0.0.0:8916
Sep 13 18:40:31 macrohumanity Tor[947]: Opening Extended OR listener on 127.0.0.1:0
Sep 13 18:40:31 macrohumanity Tor[947]: Extended OR listener listening on port 41117.
Sep 13 18:40:31 macrohumanity Tor[947]: Opened Extended OR listener connection (ready) on 127.0.0.1:41117
Sep 13 18:40:33 macrohumanity Tor[947]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 13 18:40:33 macrohumanity Tor[947]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 13 18:40:33 macrohumanity Tor[947]: Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Sep 13 18:40:35 macrohumanity Tor[947]: Your Tor server's identity key  fingerprint is <private>
Sep 13 18:40:35 macrohumanity Tor[947]: Your Tor bridge's hashed identity key  fingerprint is <private>
Sep 13 18:40:35 macrohumanity Tor[947]: Your Tor server's identity key <private> fingerprint is <private>
Sep 13 18:40:35 macrohumanity Tor[947]: You can check the status of your bridge relay at https://bridges.torproject.org/status?id=<private>
Sep 13 18:40:35 macrohumanity Tor[947]: Bootstrapped 0% (starting): Starting
Sep 13 18:40:36 macrohumanity Tor[947]: Starting with guard context "default"
Sep 13 18:40:57 macrohumanity Tor[947]: Signaled readiness to systemd
Sep 13 18:40:57 macrohumanity systemd[1]: Started Anonymizing overlay network for TCP.
Sep 13 18:40:57 macrohumanity Tor[947]: Server managed proxy encountered a method error. (obfs4 listen tcp 89.187.175.144:443: bind: cannot assign requested address)
Sep 13 18:40:57 macrohumanity Tor[947]: Managed proxy '/usr/bin/obfs4proxy' was spawned successfully, but it didn't launch any pluggable transport listeners!
Sep 13 18:40:58 macrohumanity Tor[947]: Bootstrapped 5% (conn): Connecting to a relay
Sep 13 18:40:58 macrohumanity Tor[947]: Opening Socks listener on /run/tor/socks
Sep 13 18:40:58 macrohumanity Tor[947]: Opened Socks listener connection (ready) on /run/tor/socks
Sep 13 18:40:58 macrohumanity Tor[947]: Opening Control listener on /run/tor/control
Sep 13 18:40:58 macrohumanity Tor[947]: Opened Control listener connection (ready) on /run/tor/control
Sep 13 18:40:58 macrohumanity Tor[947]: Bootstrapped 10% (conn_done): Connected to a relay
Sep 13 18:40:58 macrohumanity Tor[947]: Bootstrapped 14% (handshake): Handshaking with a relay
Sep 13 18:40:58 macrohumanity Tor[947]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Sep 13 18:40:58 macrohumanity Tor[947]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Sep 13 18:40:58 macrohumanity Tor[947]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Sep 13 18:40:58 macrohumanity Tor[947]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Sep 13 18:41:00 macrohumanity Tor[947]: Bootstrapped 100% (done): Done
Sep 13 18:41:00 macrohumanity Tor[947]: Now checking whether IPv4 ORPort 89.187.175.144:8916 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Sep 13 18:58:00 macrohumanity Tor[947]: Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 146 buildtimes.
Sep 13 19:00:58 macrohumanity Tor[947]: Your server has not managed to confirm reachability for its ORPort(s) at 89.187.175.144:8916. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
5

Thank you, saxon!
The issue actually existed before I added PortForwarding 1 , which was one of the last things that I tried prior to posting to Tor Forum.
I will try this removal in combination with Mephistopheles suggestions.

6

This is not your Alternative public IP, all ip addresses within the 127.0.0.0/8 block are reserved for loopback testing, and are not accessible externally (most of the time)

You’ll also want to change your ORPort line to have your public IPV4 as well, so it reads like 89.187.175.144:8916 IPv4Only

VPN clients and connections can be really finicky sometimes, and if your entire bridge is running behind a VPN, that may be part of your problem. If the router knows its IP given by your ISP is 89.187.175.144, but is tunneling traffic to a VPN first, responses coming back are going to be wrapped for the VPN and may not reach all the way back to your bridge, and its very possible that the VPN providers have firewalls and sniffers on the wire that are throttling or dropping suspicious traffic. So that’s something to consider.

My own router did this actually, wouldn’t let me change it to zero or blank after the rule was made, might try deleting the rule, saving, refresh the page, and make a new one and just leave the internal side blank and see if that works.

However, 443 is considered a privileged port, and that may be responsible for what’s going on here. I won’t go into tech details on privileged vs non privileged because that’s another topic, the TLDR is ports ranging from 1-1024 are privileged, and require root/superadmin privs for a lot of shit, and raw socket access is one of them. Pretty sure its hardcoded into TCP actually. Might try swapping 443 with another high port that isn’t privileged, like 1443 or 8443 or something and see if that helps.
Source: Tor Project | Debian / Ubuntu

7

Thanks, I needed a good smile today. Cheers mate

8

Thank you for the knowledge!
I also learned throughout this process that 192.168.xxx.xxx IP addresses are internal/private. Nice little light bulb.

Great point about the VPN. I should have considered that since my VPN’s have generally made my general internet experience more finicky in the past and present, haha. I have noticed that Tor seems to lean towards TCP.

I changed from ORPort 8916 IPv4Only to ORPort 89.187.175.144:8916 IPv4Only but there was no resolution. I just got done testing for a couple of hours (VPN on/off, TCP vs. UDP, forwarding-port number tinkering and combinations of all mentioned) which eventually lead to this successful configuration:

Sep 16 00:17:24 macrohumanity Tor[959]: We compiled with OpenSSL 30000020: OpenSSL 3.0.2 15 Mar 2022 and we are running with OpenSSL 30000020: 3.0.2. These t>
Sep 16 00:17:24 macrohumanity Tor[959]: Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 a>
Sep 16 00:17:24 macrohumanity Tor[959]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Sep 16 00:17:24 macrohumanity Tor[959]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 16 00:17:24 macrohumanity Tor[959]: Read configuration file "/etc/tor/torrc".
Sep 16 00:17:24 macrohumanity Tor[959]: Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this by setting MaxMemInQueues by>
Sep 16 00:17:24 macrohumanity Tor[959]: Opening Socks listener on 127.0.0.1:9050
Sep 16 00:17:24 macrohumanity Tor[959]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Sep 16 00:17:24 macrohumanity Tor[959]: Opening OR listener on 0.0.0.0:8675
Sep 16 00:17:24 macrohumanity Tor[959]: Opened OR listener connection (ready) on 0.0.0.0:8675
Sep 16 00:17:24 macrohumanity Tor[959]: Opening Extended OR listener on 127.0.0.1:0
Sep 16 00:17:24 macrohumanity Tor[959]: Extended OR listener listening on port 40633.
Sep 16 00:17:24 macrohumanity Tor[959]: Opened Extended OR listener connection (ready) on 127.0.0.1:40633
Sep 16 00:17:25 macrohumanity Tor[959]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 16 00:17:25 macrohumanity Tor[959]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 16 00:17:25 macrohumanity Tor[959]: Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 h>
Sep 16 00:17:26 macrohumanity Tor[959]: Your Tor server's identity key  fingerprint is <private>
Sep 16 00:17:26 macrohumanity Tor[959]: Your Tor bridge's hashed identity key  fingerprint is <private>
Sep 16 00:17:26 macrohumanity Tor[959]: Your Tor server's identity key <private> fingerprint is <private>
Sep 16 00:17:26 macrohumanity Tor[959]: You can check the status of your bridge relay at https://bridges.torproject.org/status?id=<private>
Sep 16 00:17:26 macrohumanity Tor[959]: Bootstrapped 0% (starting): Starting
Sep 16 00:17:27 macrohumanity Tor[959]: Starting with guard context "default"
Sep 16 00:17:41 macrohumanity Tor[959]: Signaled readiness to systemd
Sep 16 00:17:41 macrohumanity systemd[1]: Started Anonymizing overlay network for TCP.
Sep 16 00:17:41 macrohumanity Tor[959]: Registered server transport 'obfs4' at '[::]:1443'
Sep 16 00:17:42 macrohumanity Tor[959]: Bootstrapped 5% (conn): Connecting to a relay
Sep 16 00:17:42 macrohumanity Tor[959]: Opening Socks listener on /run/tor/socks
Sep 16 00:17:42 macrohumanity Tor[959]: Opened Socks listener connection (ready) on /run/tor/socks
Sep 16 00:17:42 macrohumanity Tor[959]: Opening Control listener on /run/tor/control
Sep 16 00:17:42 macrohumanity Tor[959]: Opened Control listener connection (ready) on /run/tor/control
Sep 16 00:17:42 macrohumanity Tor[959]: Bootstrapped 10% (conn_done): Connected to a relay
Sep 16 00:17:42 macrohumanity Tor[959]: Bootstrapped 14% (handshake): Handshaking with a relay
Sep 16 00:17:42 macrohumanity Tor[959]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Sep 16 00:17:42 macrohumanity Tor[959]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Sep 16 00:17:42 macrohumanity Tor[959]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Sep 16 00:17:42 macrohumanity Tor[959]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Sep 16 00:17:43 macrohumanity Tor[959]: Bootstrapped 100% (done): Done
Sep 16 00:17:43 macrohumanity Tor[959]: Now checking whether IPv4 ORPort 174.63.120.155:8675 is reachable... (this may take up to 20 minutes -- look for log >
Sep 16 00:17:45 macrohumanity Tor[959]: Self-testing indicates your ORPort 174.63.120.155:8675 is reachable from the outside. Excellent. Publishing server de>
Sep 16 00:17:51 macrohumanity Tor[959]: Performing bandwidth self-test...done.

Here is my /etc/tor/torcc:

BridgeRelay 1

# Replace "TODO1" with a Tor port of your choice.
# This port must be externally reachable.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
Address 174.63.120.155
ORPort 8675 IPv4Only
AddressDisableIPv6 1

ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy

# Replace "TODO2" with an obfs4 port of your choice.
# This port must be externally reachable and must be different from the one specified for ORPort.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ServerTransportListenAddr obfs4 0.0.0.0:1443

# Local communication port between Tor and obfs4.  Always set this to "auto".
# "Ext" means "extended", not "external".  Don't try to set a specific port number, nor listen on 0.0.0.0.
ExtORPort auto

# Replace "<address@email.com>" with your email address so we can contact you if there are problems with your bridge.
# This is optional but encouraged.
ContactInfo <private>

# Pick a nickname that you like for your bridge.  This is optional.
Nickname <private>

BandwidthRate 1 MBytes

Here are my DD-WRT port forwarding settings:

port16SEP2022
port16SEP2022740×199 12.3 KB

Additionally, my OpenVPN client is now disabled on my router. Note: I tried to re-enable my VPN in combination with the above successful port forwarding settings and I received the original error message Your server has not managed to confirm reachability for its ORPort(s) at 173.244.209.91:8675..

Another interesting change that was made is that I removed the static DHCP address that I began with at the beginning of this forum post. I am a bit confused about this because many similar situations online recommend that, if you are port forwarding, you must set up a static DHCP address outside of the range of 192.168.1.100 - 192.168.1.198.

Slightly confusing but it was a nice little project lol glad to contribute to the network.
Thanks again for the help, Mephistopheles!

1 Like
9

Nice! Smiles are good. Cheers

10

Wtih your current DD-WRT configuration you don’t have any OBFS4 port. 1443 should point at 1443.

2 Likes
11

Thank you!
Here are my port forwarding settings before pointing from 1443 to 1443:

porttest1
porttest1742×197 12.5 KB

Here is my /etc/tor/torrc output before pointing from 1443 to 1443:

Sep 16 01:55:10 macrohumanity systemd[1]: Starting Anonymizing overlay network for TCP...
Sep 16 01:55:10 macrohumanity tor[961]: Sep 16 01:55:10.490 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, L>
Sep 16 01:55:10 macrohumanity tor[961]: Sep 16 01:55:10.490 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproje>
Sep 16 01:55:10 macrohumanity tor[961]: Sep 16 01:55:10.494 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 16 01:55:10 macrohumanity tor[961]: Sep 16 01:55:10.494 [notice] Read configuration file "/etc/tor/torrc".
Sep 16 01:55:10 macrohumanity tor[961]: Sep 16 01:55:10.498 [notice] Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this>
Sep 16 01:55:10 macrohumanity tor[961]: Configuration was valid
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.619 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, L>
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.619 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproje>
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.619 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.619 [notice] Read configuration file "/etc/tor/torrc".
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.621 [notice] Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this>
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.667 [notice] Opening Socks listener on 127.0.0.1:9050
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.667 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.667 [notice] Opening OR listener on 0.0.0.0:8675
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.667 [notice] Opened OR listener connection (ready) on 0.0.0.0:8675
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.667 [notice] Opening Extended OR listener on 127.0.0.1:0
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.667 [notice] Extended OR listener listening on port 46857.
Sep 16 01:55:10 macrohumanity tor[964]: Sep 16 01:55:10.667 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:46857
Sep 16 01:55:10 macrohumanity Tor[964]: We compiled with OpenSSL 30000020: OpenSSL 3.0.2 15 Mar 2022 and we are running with OpenSSL 30000020: 3.0.2. These t>
Sep 16 01:55:10 macrohumanity Tor[964]: Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 a>
Sep 16 01:55:10 macrohumanity Tor[964]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Sep 16 01:55:10 macrohumanity Tor[964]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 16 01:55:10 macrohumanity Tor[964]: Read configuration file "/etc/tor/torrc".
Sep 16 01:55:10 macrohumanity Tor[964]: Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this by setting MaxMemInQueues by>
Sep 16 01:55:10 macrohumanity Tor[964]: Opening Socks listener on 127.0.0.1:9050
Sep 16 01:55:10 macrohumanity Tor[964]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Sep 16 01:55:10 macrohumanity Tor[964]: Opening OR listener on 0.0.0.0:8675
Sep 16 01:55:10 macrohumanity Tor[964]: Opened OR listener connection (ready) on 0.0.0.0:8675
Sep 16 01:55:10 macrohumanity Tor[964]: Opening Extended OR listener on 127.0.0.1:0
Sep 16 01:55:10 macrohumanity Tor[964]: Extended OR listener listening on port 46857.
Sep 16 01:55:10 macrohumanity Tor[964]: Opened Extended OR listener connection (ready) on 127.0.0.1:46857
Sep 16 01:55:12 macrohumanity Tor[964]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 16 01:55:12 macrohumanity Tor[964]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 16 01:55:12 macrohumanity Tor[964]: Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 h>
Sep 16 01:55:13 macrohumanity Tor[964]: Your Tor server's identity key  fingerprint is <private>
Sep 16 01:55:13 macrohumanity Tor[964]: Your Tor bridge's hashed identity key  fingerprint is <private>
Sep 16 01:55:13 macrohumanity Tor[964]: Your Tor server's identity key <private> fingerprint is 'macrohumanity <private>
Sep 16 01:55:13 macrohumanity Tor[964]: You can check the status of your bridge relay at https://bridges.torproject.org/status?id=<private>
Sep 16 01:55:13 macrohumanity Tor[964]: Bootstrapped 0% (starting): Starting
Sep 16 01:55:14 macrohumanity Tor[964]: Starting with guard context "default"
Sep 16 01:55:26 macrohumanity Tor[964]: Signaled readiness to systemd
Sep 16 01:55:26 macrohumanity systemd[1]: Started Anonymizing overlay network for TCP.
Sep 16 01:55:26 macrohumanity Tor[964]: Registered server transport 'obfs4' at '[::]:1443'
Sep 16 01:55:27 macrohumanity Tor[964]: External address seen and suggested by a directory authority: 174.63.120.155
Sep 16 01:55:27 macrohumanity Tor[964]: Bootstrapped 5% (conn): Connecting to a relay
Sep 16 01:55:27 macrohumanity Tor[964]: Opening Socks listener on /run/tor/socks
Sep 16 01:55:27 macrohumanity Tor[964]: Opened Socks listener connection (ready) on /run/tor/socks
Sep 16 01:55:27 macrohumanity Tor[964]: Opening Control listener on /run/tor/control
Sep 16 01:55:27 macrohumanity Tor[964]: Opened Control listener connection (ready) on /run/tor/control
Sep 16 01:55:27 macrohumanity Tor[964]: Bootstrapped 10% (conn_done): Connected to a relay
Sep 16 01:55:28 macrohumanity Tor[964]: Bootstrapped 14% (handshake): Handshaking with a relay
Sep 16 01:55:28 macrohumanity Tor[964]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Sep 16 01:55:28 macrohumanity Tor[964]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Sep 16 01:55:28 macrohumanity Tor[964]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Sep 16 01:55:28 macrohumanity Tor[964]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Sep 16 01:55:30 macrohumanity Tor[964]: Bootstrapped 100% (done): Done
Sep 16 01:55:30 macrohumanity Tor[964]: Now checking whether IPv4 ORPort 174.63.120.155:8675 is reachable... (this may take up to 20 minutes -- look for log >
Sep 16 01:55:32 macrohumanity Tor[964]: Self-testing indicates your ORPort 174.63.120.155:8675 is reachable from the outside. Excellent. Publishing server de>
Sep 16 01:55:41 macrohumanity Tor[964]: Performing bandwidth self-test...done.
Sep 16 07:55:27 macrohumanity Tor[964]: Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 2.38 MB and received 7.19 MB. I've received 23>
Sep 16 07:55:27 macrohumanity Tor[964]: While not bootstrapping, fetched this many bytes: 4669117 (server descriptor fetch); 355 (server descriptor upload); >
Sep 16 07:55:27 macrohumanity Tor[964]: Heartbeat: Since last heartbeat message, I have seen 0 unique clients.
Sep 17 18:46:34 macrohumanity Tor[964]: Your system clock just jumped 106173 seconds forward; assuming established circuits no longer work.
Sep 17 18:46:34 macrohumanity Tor[964]: Our directory information is no longer up-to-date enough to build circuits: We have no recent usable consensus.
Sep 17 18:46:42 macrohumanity Tor[964]: We now have enough directory information to build circuits.

Here are my port forwarding settings after pointing from 1443 to 1443:

porttest2
porttest2742×203 12.5 KB

Here is my /etc/tor/torrc output after pointing from 1443 to 1443:

Sep 17 21:48:42 macrohumanity systemd[1]: Starting Anonymizing overlay network for TCP...
Sep 17 21:48:42 macrohumanity tor[964]: Sep 17 21:48:42.878 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Sep 17 21:48:42 macrohumanity tor[964]: Sep 17 21:48:42.879 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Sep 17 21:48:42 macrohumanity tor[964]: Sep 17 21:48:42.880 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 17 21:48:42 macrohumanity tor[964]: Sep 17 21:48:42.882 [notice] Read configuration file "/etc/tor/torrc".
Sep 17 21:48:42 macrohumanity tor[964]: Sep 17 21:48:42.891 [notice] Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this by setting MaxMemInQueues by hand.
Sep 17 21:48:42 macrohumanity tor[964]: Configuration was valid
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.005 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.008 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.008 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.008 [notice] Read configuration file "/etc/tor/torrc".
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.010 [notice] Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this by setting MaxMemInQueues by hand.
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.020 [notice] Opening Socks listener on 127.0.0.1:9050
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.020 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.020 [notice] Opening OR listener on 0.0.0.0:8675
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.021 [notice] Opened OR listener connection (ready) on 0.0.0.0:8675
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.021 [notice] Opening Extended OR listener on 127.0.0.1:0
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.021 [notice] Extended OR listener listening on port 39189.
Sep 17 21:48:43 macrohumanity tor[969]: Sep 17 21:48:43.022 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:39189
Sep 17 21:48:43 macrohumanity Tor[969]: We compiled with OpenSSL 30000020: OpenSSL 3.0.2 15 Mar 2022 and we are running with OpenSSL 30000020: 3.0.2. These two versions should be binary compatible.
Sep 17 21:48:43 macrohumanity Tor[969]: Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Sep 17 21:48:43 macrohumanity Tor[969]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Sep 17 21:48:43 macrohumanity Tor[969]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Sep 17 21:48:43 macrohumanity Tor[969]: Read configuration file "/etc/tor/torrc".
Sep 17 21:48:43 macrohumanity Tor[969]: Based on detected system memory, MaxMemInQueues is set to 5769 MB. You can override this by setting MaxMemInQueues by hand.
Sep 17 21:48:43 macrohumanity Tor[969]: Opening Socks listener on 127.0.0.1:9050
Sep 17 21:48:43 macrohumanity Tor[969]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Sep 17 21:48:43 macrohumanity Tor[969]: Opening OR listener on 0.0.0.0:8675
Sep 17 21:48:43 macrohumanity Tor[969]: Opened OR listener connection (ready) on 0.0.0.0:8675
Sep 17 21:48:43 macrohumanity Tor[969]: Opening Extended OR listener on 127.0.0.1:0
Sep 17 21:48:43 macrohumanity Tor[969]: Extended OR listener listening on port 39189.
Sep 17 21:48:43 macrohumanity Tor[969]: Opened Extended OR listener connection (ready) on 127.0.0.1:39189
Sep 17 21:48:45 macrohumanity Tor[969]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 17 21:48:45 macrohumanity Tor[969]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 17 21:48:45 macrohumanity Tor[969]: Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Sep 17 21:48:45 macrohumanity Tor[969]: Your Tor server's identity key  fingerprint is 'macrohumanity 6CF1FA5CB4FEA1C9A739BCBC55619402FD1564BD'
Sep 17 21:48:45 macrohumanity Tor[969]: Your Tor bridge's hashed identity key  fingerprint is 'macrohumanity 2D803B83F0038B24C77A16FC5196790AB1BD6093'
Sep 17 21:48:45 macrohumanity Tor[969]: Your Tor server's identity key ed25519 fingerprint is 'macrohumanity VzOOpB2OlPwO1+vuYxzA5Y1AKZyTG1ZCtbnvRR2JXVM'
Sep 17 21:48:45 macrohumanity Tor[969]: You can check the status of your bridge relay at https://bridges.torproject.org/status?id=2D803B83F0038B24C77A16FC5196790AB1BD6093
Sep 17 21:48:45 macrohumanity Tor[969]: Bootstrapped 0% (starting): Starting
Sep 17 21:48:46 macrohumanity Tor[969]: Starting with guard context "default"
Sep 17 21:49:00 macrohumanity Tor[969]: Signaled readiness to systemd
Sep 17 21:49:00 macrohumanity systemd[1]: Started Anonymizing overlay network for TCP.
Sep 17 21:49:00 macrohumanity Tor[969]: Registered server transport 'obfs4' at '[::]:1443'
Sep 17 21:49:02 macrohumanity Tor[969]: Bootstrapped 5% (conn): Connecting to a relay
Sep 17 21:49:02 macrohumanity Tor[969]: Opening Socks listener on /run/tor/socks
Sep 17 21:49:02 macrohumanity Tor[969]: Opened Socks listener connection (ready) on /run/tor/socks
Sep 17 21:49:02 macrohumanity Tor[969]: Opening Control listener on /run/tor/control
Sep 17 21:49:02 macrohumanity Tor[969]: Opened Control listener connection (ready) on /run/tor/control
Sep 17 21:49:02 macrohumanity Tor[969]: Bootstrapped 10% (conn_done): Connected to a relay
Sep 17 21:49:02 macrohumanity Tor[969]: Bootstrapped 14% (handshake): Handshaking with a relay
Sep 17 21:49:02 macrohumanity Tor[969]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Sep 17 21:49:02 macrohumanity Tor[969]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Sep 17 21:49:02 macrohumanity Tor[969]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Sep 17 21:49:02 macrohumanity Tor[969]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Sep 17 21:49:04 macrohumanity Tor[969]: Bootstrapped 100% (done): Done
Sep 17 21:49:04 macrohumanity Tor[969]: Now checking whether IPv4 ORPort 174.63.120.155:8675 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Sep 17 21:49:05 macrohumanity Tor[969]: Self-testing indicates your ORPort 174.63.120.155:8675 is reachable from the outside. Excellent. Publishing server descriptor.
Sep 17 21:51:06 macrohumanity Tor[969]: Performing bandwidth self-test...done.
Sep 18 03:49:01 macrohumanity Tor[969]: Heartbeat: Tor's uptime is 6:00 hours, with 22 circuits open. I've sent 301.93 MB and received 299.02 MB. I've received 70 connections on IPv4 and 0 on IPv6. I've made 222 connections with IPv4 and 0 with IPv6.
Sep 18 03:49:01 macrohumanity Tor[969]: While not bootstrapping, fetched this many bytes: 4142846 (server descriptor fetch); 363 (server descriptor upload); 372199 (consensus network-status fetch); 26963 (microdescriptor fetch)
Sep 18 03:49:01 macrohumanity Tor[969]: Heartbeat: Since last heartbeat message, I have seen 5 unique clients.
Sep 18 05:01:04 macrohumanity Tor[969]: No circuits are opened. Relaxed timeout for circuit 224 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.
Sep 18 05:22:33 macrohumanity Tor[969]: Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 656 buildtimes.
Sep 18 09:49:01 macrohumanity Tor[969]: Heartbeat: Tor's uptime is 12:00 hours, with 16 circuits open. I've sent 353.13 MB and received 358.56 MB. I've received 136 connections on IPv4 and 0 on IPv6. I've made 351 connections with IPv4 and 0 with IPv6.
Sep 18 09:49:01 macrohumanity Tor[969]: While not bootstrapping, fetched this many bytes: 9119901 (server descriptor fetch); 741 (server descriptor upload); 808990 (consensus network-status fetch); 96025 (microdescriptor fetch)
Sep 18 09:49:01 macrohumanity Tor[969]: Heartbeat: Since last heartbeat message, I have seen 5 unique clients.

5 unique clients! Very awesome.
Aside from this change, an active DD-WRT OpenVPN client seemed to be a culprit during testing. My next project will be to find a way to run my bridge along side of an DD-WRT OpenVPN client.
Thank a lot, everyone