Recenbtly upgraded to the latest 2022.5 and 2022.5.1.
No longer able to login via external url, with nginx reverse proxy on non-standard port. All was working before the recent upgrade(s).
Also noticed, the internal_url and external_url in the http: section are now obselete! Removed them.
I cannot see why the external access is disabled, and I cannot see how to enable it. There are no log messages,. and I filled in the external URL under the neworking config section.
Anyone have any ideas around this?
I have the similar setup, and after updating home assistant core to 2022.5.1 I have noticed a new network tab on the settings->system page which says “external access disabled”
After entering my URL and saving, it still shows as disabled.
However, I’m able to access my instance externally. my implementation uses duckDNS & Nginx reverse proxy.
Another point to note, I did have an issue while accessing the instance with the companion app on IOS prior to the update, it was giving me an SSL error. Deleting the app on my phone and reinstalling helped resolve the issue.
Is your nginx on the same machine as home assistant?
Mine is not, and I am just wondering if the locally defined network config is specific to nginzx running locally…
Me neither… I had this all working great, then after upgrade I get this message… I cannot access HA from outside, but things like location updates work from mobile devices…
Having the same issue, can not access from outside, and Network indicates external access is disabled
Mine is a fresh install, HA running as a VM on ESXi.
port on my router is directed to my HA instance.
It is like the request never hits hits HA.
I have other VMs working the same way and they are all accessible from the outside.
need to try something like tcpdump on the server, but was hoping for a quick fix to this
I too show “External Access Disabled” under my “Network” header, but I am able still able to access from outside my network having entered my HTTPS URL in both the “Internet” and “Local Network” fields.
Running HA 2022.5.2 core in docker container, along side SWAG container for SSL management, connecting to DuckDNS.
Experiencing this as well. New VM install (haos_ova-8.0.rc4.qcow2 running on Unraid). Followed this post, then this one.
The remote https login page says “Logging in with Home Assistant Local”, takes my (correct) auth for my acct (which isn’t restricted to local network) then tries to load and fails. Initiates a 60s loop of waiting and retrying. Meanwhile, my homeassistant.local login reports:
Logger: homeassistant.components.http.ban
Source: components/http/ban.py:125
Integration: HTTP (documentation, issues)
First occurred: 00:41:19 (7 occurrences)
Last logged: 00:51:54
Login attempt or request with invalid authentication from <my device info>
There is no ip_bans.yaml in /config.
I am seeing “External access disabled” next to Network as well.
Had the same issue with the nginx reverse proxy, external access was unavailable out of nowhere (not after an update but at a random moment). Restarted the addon and external access was available again. After a complete restart, the network tab still shows external access disabled for some reason.
I’m having the same issues accessing my external URL since one of the recent updates. I’m using the Let’s Encrypt and Nginx Reverse Proxy add-ons within HA.
Home Assistant Core 2022.5.3
Home Assistant Supervisor 2022.05.1
Home Assistant OS 7.6
Running in VirtualBox from the official VDI
I’m not positive this resolved my issue (I haven’t backed out the change to confirm that it fails again), but I added the following to the homeassistant: section of my configuration.yaml:
Note: you will need to change the homeass.abc.net to be whatever your actual DNS name is .
I then restarted my homeassistant server and now I can once again connect to HomeAssistant using the app on my phone and connected via 5G (i.e. the internet).
It still says “External Access Disabled” from the system screen:
It also says “Editor disabled because config stored in configuration.yaml” so I assume it’s using the change that I made:
I’ve attached some images… not sure if they worked.
I have same setup and same issue. I’ve restarted server several times with no luck. However, I’ve restarted the nginx add-on and now I can access from outside once again (still having the “external access disabled” text on network settings).
