addon-cloudflared: Unable to connect to Home Assistant. Retrying in __ seconds -

The problem

very similar to Issue 263, I am unable to login to Home Assistant via external URL. Internal URL remains functional. No Reverse Proxy Manager involved.

My domain name was registered thru CloudFlare, and I use CloudFlare’s DNS & Dynamic DNS. I have uninstalled, re-installed and re-set this add-on many times, with the result always the same. I have been researching on HA community, reddit, and here on GitHub. I have pasted in the bits you have requested from others in this thread and the HA Community site. I am happy to work with you in any way you wish to help resolve this. Please let me know if you need any additional Info

What version of Cloudflared has the issue?

4.0.10 (and earlier)

What was the last working version of Cloudflared?

No response

What type of installation are you running?

Home Assistant OS

Add-on YAML Configuration

external_host_name: subdomain.domain.com     #(anonomized!)
additional_hosts: []

Anything in the logs that might be useful for us?

HA Log:  
WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from *** (xxx.xxx.xxx.xxx). Requested URL: '/auth/token'.   (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36)

Cloudflared Startup Log: 
Add-on: Cloudflared
 Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
 
 Add-on version: 4.0.10
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.2.2
 Home Assistant Supervisor: 2023.01.1
 
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
 
[15:21:51] INFO: Checking add-on config...
[15:21:52] INFO: Checking for existing certificate...
[15:21:52] INFO: Existing certificate found
[15:21:52] INFO: Checking for existing tunnel...
[15:21:52] INFO: Existing tunnel with ID *** found
[15:21:52] INFO: Checking if existing tunnel matches name given in config
[15:21:53] INFO: Existing Cloudflare Tunnel name matches config, proceeding with existing tunnel file
[15:21:53] INFO: Creating config file...
[15:21:55] INFO: Validating config file...
Validating rules from /tmp/config.json
OK
[15:21:55] INFO: Creating DNS entry ***...
2023-02-07T20:21:56Z INF *** is already configured to route to your tunnel tunnelID=***
[15:21:56] INFO: Finished setting up the Cloudflare Tunnel
[15:21:57] INFO: Connecting Cloudflare Tunnel...
2023-02-07T20:21:57Z INF Starting tunnel tunnelID=***
2023-02-07T20:21:57Z INF Version 2023.2.1
2023-02-07T20:21:57Z INF GOOS: linux, GOVersion: go1.19.3, GoArch: arm64
2023-02-07T20:21:57Z INF Settings: map[config:/tmp/config.json cred-file:/data/tunnel.json credentials-file:/data/tunnel.json loglevel:info metrics:0.0.0.0:36500 no-autoupdate:true origincert:/data/cert.pem]
2023-02-07T20:21:57Z INF Generated Connector ID: 6157411c-9374-42d2-932e-6693ecf9a0fd
2023-02-07T20:21:57Z INF Initial protocol quic
2023-02-07T20:21:57Z INF ICMP proxy will use 172.30.33.3 as source for IPv4
2023-02-07T20:21:57Z INF ICMP proxy will use :: as source for IPv6
2023-02-07T20:21:57Z INF Starting metrics server on [::]:36500/metrics
2023-02-07T20:21:57Z INF Connection f6e0fd34-0c6c-49d1-939e-757759fd2121 registered with protocol: quic connIndex=0 ip=198.41.200.13 location=ORD
2023-02-07T20:21:58Z INF Connection 3d316fa8-cc94-444c-adf8-b330000e1955 registered with protocol: quic connIndex=1 ip=198.41.192.7 location=EWR
2023-02-07T20:21:59Z INF Connection f5f7a0cd-c35a-4b53-8093-d55f36c2b584 registered with protocol: quic connIndex=2 ip=198.41.192.67 location=EWR
2023-02-07T20:21:59Z INF Connection 99e7e1f2-abe9-43b1-8d3a-74285555027f registered with protocol: quic connIndex=3 ip=198.41.200.43 location=ORD

Steps to reproduce the issue

1. Access external url via any device: android, desktop, etc, over WiFi, LTE, etc
2. See HA Login Page
3. Provide Username & password
4. Receive Error on screen and in log file

Additional information

No response