The HTTP YAML configuration is deprecated

Configuration
1

After upgrading to core 2026.8.0 I get a deprecation message for my http: block in configuration.yaml.

  The HTTP YAML configuration is deprecated

  Warning · Reported by HTTP
  
  This stops working in version 2027.2.0. Please address before upgrading.
  
  Your existing HTTP configuration from `configuration.yaml` has been imported. The `http` integration is now configured from the UI under **Settings** > **System** > **Network**.
  
  Please remove the `http:` block from your `configuration.yaml` and restart Home Assistant.

I have been using a cloudflare tunnel with the cloudflared app running in the background. I was under the impression that I needed to set use_x_forwarded_for and trusted_proxies for all of the cloudflare IP ranges in order to access through the tunnel properly.

I want to remove this deprecation, but I don’t see any options in Settings > System > Network for the reverse proxy configuration.

Thanks

2

Do a hard refresh on of your dashboards.

3

You need to remove the http: from your configuration.yaml, and then enter the Reverse proxy in Settings > System > Network > HTTP server.

4

The settings should have been auto-migrated, the were for all of the HA systems I run. The issue is that a lot of the system dashboards have long TTL caches so you have to force refresh them to see the new additions.

5

ahh that did it, it was a cache issue. Thanks!

6

Thank you. This was not clear to me from the warning in ha.

7

WHat about these options (I cant see them in UI) :
http:
ip_ban_enabled: true
login_attempts_threshold: 3

8

they are there, hard refesh the page.

9

So I am new at this and trying to understand what to do:

Do I remove this http from my config.yaml file

Screenshot 2026-08-12 at 7.29.49 PM
Screenshot 2026-08-12 at 7.29.49 PM626×184 13.6 KB

10

Yes that entire section.

11

@tykeal Thanks. I have Cloudflared Tunnel add-on inside Home Assistant and with a domain name purchased within it, so you think I can safely remove it. This is the only way I remotely access HA

12

It was migrated to the ui, those settings are still in place.

13

Thank you!

14

Maybe this should go in a whole new post, but: Is there anywhere we can read about the reasoning behind this deprecation?

Edit: Moved into a more appropriate on-topic post: HTTP YAML Deprecation: how to access new install behind proxy - #7 by Luana

Sorry if the post moving looked spammy, that post seems more related than posting this as a reply to a help request.

15

Ran into the same issue, it wasn’t until several ctrl+F5’s the SSL/TLS settings appeared, can this be added in the warning?

Also, I’m getting a warning about the internal url not matching the certificate on that page, well, they match, not sure why HASS claims they don’t.

16

I got this warning and removed the http block from my configuration.yaml. The Warning doesn’t appear to go away, despite rebooting the whole system. Do I have to “Ignore” it despite the fact that I removed that block?

17

Clear your cache and refresh the page.

18

I cleared site data and refreshed the page and the Warning was still there.

I also visited my Home Assistant in a browser that I never visited it in before and the warning was still there.

19

After you restarted after removing/commenting out the section?

I did this 2 weeks ago and didn’t have to ignore anything.

Comment/delete, restart, it’s gone after a page refresh.

20

Huh, looks like another reboot did the trick. Thanks.