Login attempt or request with invalid authentication from router.lan

[mint kestrel]

@dense magnet replied in main channel:
"What are you trying to do here ? what is your config and why does your router try to access your HA ?
If you're using some port-forwards or so on your router to access your HA from elsewhere, maybe have a look at the https://github.com/brenner-tobias/addon-cloudflared addon, I recently switched to this and it really works great and easy."

@mint kestrel :

Ty, sry!

What I'm trying to do: Get rid of the (failed) login attempts (warnings); apparently 6 attempts within some seconds , then some minutes nothing, then warnings again..

Why does my router try to access my HA: I don't know and would like to find out

Network relevant Config:
Addons:
DuckDNS & NGINX Home Assistant SSL proxy
Remote (Remote access is working)
Router:
add action=dst-nat chain=dstnat dst-address-list=WAN-IP dst-port=443 log=yes log-prefix="dst-nat nginx rule" protocol=tcp to-addresses=<ipaddressofhomeassistant> to-ports=443
(no port 80)

Home Assistant:
config.yaml:

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24```
Network Settings  Assistant:
- Manual IPv4 outside of DHCP Pool /24;  Gateway&DNS set to Routers IP
- IPv6 automatic
- Home Assistant URL:
   Internet: https://samesomething.duckdns.org
   Local Network: Automatic

**Other maybe relevant things:**
- I started a second homeassistant instance on the same network from scratch to replace the first (which is still running) and used the same old duckdns url for the new one, changing the Port forward IP on the router
- I had Alexa and Withings integrations set up to be able to send things to my duckdns address (old homeassistant instance), but deleted the integrations in the mean time

Oh and iOS companion app will be communicatin with it as well I guess (enabled sharing location, SSID and charging status).

And was previously used logged in to the old instance.

[dense magnet]

Not really sure what your current issue is, but still the addon I pointed out might be a solution 😉
It doesn't require you to make any local config with nginx and duckdns, and it doesn't require a port-forward from your router.
It will create a tunnel from your ha towards cloudflare and then you can remote-access your ha from there, works great, very easy to setup and get's rid of an attack-vector you're exposing via the port-forware on your router

[mint kestrel]

does it work with integrations that expect a remotely accessible url? (withings, alexa, .. ?)

[dense magnet]

Alexa i don't know, but you'll get a https://ha.example.org which is accessible

[mint kestrel]

ok will read, ty

[dense magnet]

example.org should then be a domain-name you manage via cloudflare

for dns at least

[mint kestrel]

issue is that I dont know if theres something that i forgot to deactivate / correct from my previous homeassistant-instance(setup), that is leading to those failed login warnings,
or if it's someone else trying to access my home assistant 🙂

[dense magnet]

since you're doing a port forward in you router anyone who knows your public ip address can try to acces you ha

[mint kestrel]

at least the nginx on it, yes

[dense magnet]

that's why I switched to using the cloudflare tunnel