"Unable to connect" after the login page to HA

[bellaf]

Hi all,
Tobias, excellent Add-on, discovered Cloudflare a few weeks ago, its a game changer!
I am, however, having issues with getting past the Homeassisant Login screen using this add-on.
I have been through the Wiki and the setup of the tunnel (Its Active, and not showing any errors, and I am accessing Proxmox using a subdomain without any issues at all)
Before logging an Issue request (its probably something I've missed), thought I would throw myself on the mercy of this community and see what options I have.

HA is runing on a Proxmox VM (Not container) and locally is fully operational.
It has a local IP of 10.10.20.100
There is no Letsencypt or Duckdns add-ons installed (I removed them..) so am accessing HA using HTTP (Lets encrypt certificates will follow, but wanted to start with simple steps first)

This is the display I get after I sign in to HA using the homeassistant authentication (default one)

"Unable to connect to Homeasistant, retrying...."

The following is the Log entry for the attempted login:

Logger: homeassistant.components.http.ban
Source: components/http/ban.py:81
Integration: HTTP (documentation, issues)
First occurred: 07:39:13 (9 occurrences)
Last logged: 07:46:39

Login attempt or request with invalid authentication from webdefence-pool-02.cluster-lonb.forcepoint.net (85.115.53.202). Requested URL: '/auth/token'. (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0)

configuration.yaml:
auth_providers:
- type: homeassistant
allow_bypass_login: true

allowlist_external_dirs:
- /config/images
http:
use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24

cloudflared configuration (I've "tampered" with the Token here, dont want everyone to see it :-)

additional_hosts: []
external_hostname: ""
tunnel_name: ha-tunnel
tunnel_token: >-
eyJh...MiJ9

and the add-on log file is as follows:

Add-on: Cloudflared
Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports

Add-on version: 4.0.9
You are running the latest version of this add-on.
System: Home Assistant OS 9.5 (amd64 / qemux86-64)
Home Assistant Core: 2023.1.7
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.

[07:56:21] INFO: Using Cloudflare Remote Management Tunnel
[07:56:21] INFO: All add-on configuration options except tunnel_token will be ignored.
2023-02-01T07:56:21Z INF Starting tunnel tunnelID=xxx-xxxetc
2023-02-01T07:56:21Z INF Version 2023.1.0
2023-02-01T07:56:21Z INF GOOS: linux, GOVersion: go1.19.3, GoArch: amd64
2023-02-01T07:56:21Z INF Settings: map[loglevel:info metrics:0.0.0.0:36500 no-autoupdate:true token:*****]
2023-02-01T07:56:21Z INF Generated Connector ID: 8cd6.....f98d
2023-02-01T07:56:21Z INF Will be fetching remotely managed configuration from Cloudflare API. Defaulting to protocol: quic
2023-02-01T07:56:21Z INF Initial protocol quic
2023-02-01T07:56:21Z INF ICMP proxy will use 172.30.33.6 as source for IPv4
2023-02-01T07:56:21Z INF ICMP proxy will use :: as source for IPv6
2023-02-01T07:56:21Z INF Starting metrics server on [::]:36500/metrics
2023-02-01T07:56:21Z INF Connection 1fdec727-b6bf-46dc-88be-76310e447161 registered with protocol: quic connIndex=0 ip=198.41.192.47 location=LHR
2023-02-01T07:56:22Z INF Connection 64fd6def-adfe-4151-b955-174fa3061df3 registered with protocol: quic connIndex=1 ip=198.41.200.33 location=BRU
2023-02-01T07:56:22Z INF Updated to new configuration config="{"ingress":[{"hostname":"ha.xxxxxxxx.net","originRequest":{},"service":"http://homeassistant:8123"},{"service":"http_status:404"}],"warp-routing":{"enabled":false}}" version=5
2023-02-01T07:56:23Z INF Connection bbf89cbf-c33d-4b26-a273-33a0ddeac372 registered with protocol: quic connIndex=2 ip=198.41.200.23 location=BRU
2023-02-01T07:56:24Z INF Connection 58a0ada1-420b-41ad-8ab0-7517a8769f09 registered with protocol: quic connIndex=3 ip=198.41.192.7 location=LHR

I would appreciate any observations or suggestions on how to resolve this....

Many thanks
(Appologies for the HUGE highlighted text above, cant see any modifiers in the text.......)
Tony Bell

[bellaf]

I think I may have answered my own question.......
I was using browsers that were being protected by corporate web firewall appliances, and while it let me fill in details in the Login page, it wouldn't allow any further traffic.
Using this at home, none of the above firewall stuff, all is absolutely fine......

So will mark this as answered.....