With the HTTP block deprecation as of 2027.2, what is the supported method of configuring HomeAssistant access settings declaratively? How can I define my trusted_proxy IP without remote access to the GUI, either for an initial installation or for recovery after a changed remote proxy IP?
It has movedf to the UI.
There are a couple of posts in this search (in this forum) that might help:
https://community.home-assistant.io/search?q=http%20dep
OR
Type this into the search engine of your choice:
site:home-assistant.io http deprecat
Your best bet is to make sure you can access the web UI from within your local network. I keep a WireGuard VPN connection in my back-pocket for such instances, whatever reason they may be.
From what has been replied in other posts, it seems that there’s no way to recover if your webUi ever becomes inaccessible. Apparently in that situation you’d need a full reinstall, and that’s if the default configuration even works for you. Otherwise I guess maybe manually changing some database or something and praying that it doesn’t corrupt?
I’ve seen some nonsense changes before in many places, but this one is definitely way high up in the top of the list. I hope they end up reverting this deprecation.
Other posts about this include:
I haven’t looked, but HAOS CLI commands also may have happened. Wouldn’t surprise me.
You can access the settings the same way you accessed yaml files. It’s a json file inside the hidden .storage folder. Don’t know the name of the file off the top of my head.
Petro, you’ve mentioned this before, and I think it’s going to be a direction many of us are forced to go as the removal of YAML from HA progresses.
But, to be fair to anyone stumbling across this thread, we should also mention that doing this is unsupported and not recommended. If I understand correctly, the JSON files in that folder may contain both static configuration data the user selects, and dynamic data which the system manages. Manual changes could impact whichever component is using that file, possibly even causing it to fail.
Oh, and the settings in those files are apparently not documented anywhere.
I know this has all been hashed over before, so I won’t pontificate. But I do think anyone coming here for advice ought to know.
You’re making it sound way scarier than it is. Just take a look at the http file, adjust the settings as needed. Use a JSON validator if you’re unsure. Don’t change the structure. The file is human readable and very easy to understand.
Great, this is what I wanted to know. Thanks.
It’s still suboptimal, as there is the possibility of this location being changed without notice in a way that eventually affects new installs, but it’s the best option currently and should work for a long time.