home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.14k stars 31.12k forks source link

Login Attempt of Request with Invalid Authentication from... #118173

Closed MrBogger closed 3 months ago

MrBogger commented 6 months ago

The problem

When trying to log in to HA locally on iOS app (2024.5), it connects but then comes up with a "The server has rejected your credentials" error.

IMG_6748

Sometimes, it will come up with a Response Status Code was unacceptable: 500. Error Code: AlamoFire.AFError9

IMG_6747

Checking HA Logs shows the error source as components/http/ban.py:138 and had occurred 7402 times in 8 minutes.

Screen Shot 2024-05-26 at 19 42 11

This seems to be an issue between current versions as this issue for me only started a few days ago when I upgraded from 2024.5.4 to 2024.5.5 but that also coincided with iOS 2024.5.5 being upgraded on the App Store. My main instance is running HA Supervised on HyperV and my second instance is running on RaspPi3B. Both I can not log into from iOS after upgrade. I have tried changing passwords, different phones etc. I have tried rolling back both my instanceds

What version of Home Assistant Core has the issue?

2024.5.5

What was the last working version of Home Assistant Core?

2024.5.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

HTTP / iOS App

Link to integration documentation on our website

No response

Diagnostics information

Perkins Home Versions.txt

iOS App logs: Home Assistant.txt HomeAssistant-Extensions-PushProvider.txt HomeAssistant-Extensions-Intents.txt HomeAssistant-Extensions-Widgets.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

issue-triage-workflows[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.