TTS: Login attempt or request with invalid authentication

Configuration
1

Hello there,

Every time I’m using TTS (and at restart), I’ve a new persistent notification:

Login attempt or request with invalid authentication from mymodem.lan (192.168.0.100). See the log for details.

192.168.0.100 is my modem (as you can read)

Looking at the log I can’t see anything wrong, linked to that error.

TTS is working fine, so I don’t know what is wrong.
But the side effect is, that because I’ve enabled ip ban, my modem, which is also my nat device is banned.

So that’s a terrible situation here.

I’ve enabled aiohttp debug logs: nothing
I’ve enabled homeassistant.components.tts debug logs: nothing
As the targets are sonos and alexa, I’ve activated the debug on those as well: nothing

Please help me find the reason of those errors.

P.S.: I’m using exclusivelly the external address of HA, even from my internal devices, in https using letsencrypt and the DDNS from synology.

P.P.S: My tts configuration

tts:
  - platform: google_translate
    cache: false
    time_memory: 300
2

I see this sometimes, but only from HA on my android device.

I have a hostname that maps to internal addresses on my local network, and to a public IP address for remote access.

I’ve seen it happen both on internal and external networks.

It only happens about once every two weeks, but most of the time I use it on my local network.

Do you know how to disable the IP ban? It seems to be on by default.

Edit: OK found the setting, I didn’t specifically enable it but had login_attempts_threshold set to 10, setting it to -1 to see if that avoids getting banned.

I’d like to figure out what’s wrong, but this is so sporadic, and I think the HA android app logs need to be checked.

3

I’m on iPhone.
And almost everytime I’m triggering a TTS on my sonos/echo devices, I have a new alert about 192.168.0.100 (my modem, entry point of the DDNS)
I could disable the ban, but I like the feeling of safety it procurs :slight_smile: