No access to HAS via Domain

Installation
1

Hi all,

now im a complete noob managed to get most of this running by trial and error.

I’ve just installed my server running Cloudflare DDNS and NGINX.

I have got Nextcloud running via nextcloud.mydomain.com, even via iPhone with calendar sync etc.

  • So that means DDNS and NGINX are working.

I can reach my HAS instance over homeassistant.mydomain.com fine, though it doesn’t want to let me log in.

I can access it fine through the internal IP 192.168.178.4:8123.
Externally it gives me:

image

Logs show this:
2024-08-11 17:44:08.630 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from xxxxxx.dip0.t-ipconnect.de (my.public.ip.add). Requested URL: ‘/auth/token’. (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 OPR/111.0.0.0)

my .yaml looks like this currently:

http:
use_x_forwarded_for: true
trusted_proxies:
- 172.17.0.1 # Add the IP address of the proxy server
- 172.18.0.4 (SWAG Container)

I tested different settings in the .yaml but nothing worked.

What could be the cause of this?

2

Does anyone have a idea?

3

Indentation ?

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.17.0.1 # Add the IP address of the proxy server
    - 172.18.0.4 (SWAG Container)

And make sure you forward websockets too in NGINX