From db3b3942e5f707cd26fbff437bdc0a077ebe0639 Mon Sep 17 00:00:00 2001 From: DubhAd Date: Fri, 19 Oct 2018 19:48:41 +0100 Subject: [PATCH] Added note about nmap (#6962) * Added note about nmap Added note about nmap * Minor change --- source/_docs/authentication.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_docs/authentication.markdown b/source/_docs/authentication.markdown index f2e984cf30a..8d711c416af 100644 --- a/source/_docs/authentication.markdown +++ b/source/_docs/authentication.markdown @@ -40,6 +40,10 @@ As a user, you can setup multi-factor authentication with time-based one-time pa ## {% linkable_title Troubleshooting %} +### {% linkable_title Authentication failures from `127.0.0.1` %} + +If you're seeting authentication failures from `127.0.0.1` and you're using the `nmap` device tracker, you should [exclude the Home Assistant IP](/components/device_tracker.nmap_tracker/#exclude) from being scanned. + ### {% linkable_title Bearer token warnings %} Under the new authentication system you'll see the following warning logged when the [legacy API password](/docs/authentication/providers/#legacy-api-password) is supplied, but not configured in Home Assistant: