Bridge Docker, ORport not reachable

Hi. I have used this Tor Project | Docker instruction to install a bridge on my Synology Nas.

The problem i am facing is:
[warn] Your server has not managed to confirm reachability for its ORPort(s) at my.public.ip.address:8443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

Ah telnet to my.public.ip.address 8443 works fine. Verifying that the ports are functional and a three way handshake can be established.
I have been infromed that my obfs4 bridge can be used from a user on the tor-network.

Here is my .env:

# Your bridge's Tor port.
OR_PORT=8443
# Your bridge's obfs4 port.
PT_PORT=8080
# Your email address.
EMAIL=<redacted>

# If you want, you could change the nickname of your bridge
NICKNAME=<redacted>
# If needed, activate additional variables processing
OBFS4_ENABLE_ADDITIONAL_VARIABLES=1
# and define desired torrc entries prefixed with OBFS4V_
# For example:
OBFS4V_AddressDisableIPv6=1

I have made some changes to the torrc file, here it is in its current from:

RunAsDaemon 0
# We don't need an open SOCKS port.
SocksPort 0
BridgeRelay 1
Nickname <redacted>
Log notice file /var/log/tor/log
Log notice stdout
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ExtORPort auto
DataDirectory /var/lib/tor

Address <redacted>

# The variable "OR_PORT" is replaced with the OR port.
ORPort 8443 IPv4Only

# The variable "PT_PORT" is replaced with the obfs4 port.
ServerTransportListenAddr obfs4 0.0.0.0:8080

# The variable "EMAIL" is replaced with the operator's email address.
ContactInfo <redacted>

# Additional properties from processed 'OBFS4V_' environment variables
AddressDisableIPv6 1

Logs:

Starting tor.
Sep 09 11:24:20.784 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc.
Sep 09 11:24:20.784 [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 09 11:24:20.784 [notice] Read configuration file "/etc/tor/torrc".
Sep 09 11:24:20.786 [notice] Based on detected system memory, MaxMemInQueues is set to 2832 MB. You can override this by setting MaxMemInQueues by hand.
Sep 09 11:24:20.788 [notice] Opening OR listener on 0.0.0.0:8443
Sep 09 11:24:20.788 [notice] Opened OR listener connection (ready) on 0.0.0.0:8443
Sep 09 11:24:20.788 [notice] Opening Extended OR listener on 127.0.0.1:0
Sep 09 11:24:20.788 [notice] Extended OR listener listening on port 45243.
Sep 09 11:24:20.789 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:45243
Sep 09 11:24:21.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 09 11:24:21.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 09 11:24:22.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Sep 09 11:24:22.000 [notice] Your Tor server's identity key  fingerprint is '<redacted>'
Sep 09 11:24:22.000 [notice] Your Tor bridge's hashed identity key  fingerprint is '<redacted>'
Sep 09 11:24:22.000 [notice] Your Tor server's identity key ed25519 fingerprint is '<redacted>'
Sep 09 11:24:22.000 [notice] You can check the status of your bridge relay at https://bridges.torproject.org/status?id=<redacted>
Sep 09 11:24:22.000 [notice] Bootstrapped 0% (starting): Starting
Sep 09 11:24:23.000 [notice] Starting with guard context "default"
Sep 09 11:24:42.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Sep 09 11:24:42.000 [notice] Registered server transport 'obfs4' at '[::]:8080'
Sep 09 11:24:42.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Sep 09 11:24:42.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Sep 09 11:24:43.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Sep 09 11:24:43.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Sep 09 11:24:43.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
Sep 09 11:24:43.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Sep 09 11:24:43.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Sep 09 11:24:44.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Sep 09 11:24:44.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Sep 09 11:24:44.000 [notice] Bootstrapped 100% (done): Done
Sep 09 11:24:44.000 [notice] Now checking whether IPv4 ORPort <redacted>:8443 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Sep 09 11:44:42.000 [warn] Your server has not managed to confirm reachability for its ORPort(s) at <redacted>:8443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Sep 09 12:04:42.000 [warn] Your server has not managed to confirm reachability for its ORPort(s) at <redacted>:8443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Sep 09 12:22:44.000 [warn] Received http status code 404 ("Not found") from server <redacted>:9001 while fetching "/tor/keys/fp/<redacted>".
Sep 09 12:24:42.000 [warn] Your server has not managed to confirm reachability for its ORPort(s) at <redacted>:8443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Sep 09 12:44:42.000 [warn] Your server has not managed to confirm reachability for its ORPort(s) at <redacted>:8443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Sep 09 12:59:44.000 [warn] Received http status code 404 ("Not found") from server <redacted>:9001 while fetching "/tor/keys/fp/<redacted>".
Sep 09 13:00:44.000 [warn] Received http status code 404 ("Not found") from server <redacted>:9001 while fetching "/tor/keys/fp/<redacted>".
Sep 09 13:04:42.000 [warn] Your server has not managed to confirm reachability for its ORPort(s) at <redacted>:8443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Sep 09 13:24:42.000 [warn] Your server has not managed to confirm reachability for its ORPort(s) at <redacted>:8443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

Have you tried contacting your Bridge from another host outside of your network? There might be some NAT/Port forwarding issues involved.

Depending on your router software your public IP might be reachable from inside your network, even if it is not reachable from outside.

Hi. To be clear, I have verified the communication from off site.