The http component serves all files and data required for the Home Assistant frontend. You only need to add this to your configuration file if you want to change any of the default settings.

Don’t use option server_host on a installation!

# Example configuration.yaml entry
  api_password: YOUR_PASSWORD

Configuration Variables


(string)(Optional)Protect the Home Assistant API with a password - this password can also be used to log in to the frontend. Where your client or other software supports it, you should use long lasting access token instead, as shown in the REST API and websocket API documentation.


(string)(Optional)Only listen to incoming requests on specific IP/host. By default it will accept all IPv4 connections. Use server_host: ::0 if you want to listen to (and only) IPv6.

Default value:


(integer)(Optional)Let you set a port to use.

Default value: 8123


(string)(Optional)The URL that Home Assistant is available on the internet. For example: The iOS app finds local installations, if you have an outside URL use this so that you can auto-fill when discovered in the app.

Default value: Your local IP address


(string)(Optional)Path to your TLS/SSL certificate to serve Home Assistant over a secure connection.


(string)(Optional)Path to the client/peer TLS/SSL certificate to accept secure connections from.


(string)(Optional)Path to your TLS/SSL key to serve Home Assistant over a secure connection.


(string | list)(Optional)A list of origin domain names to allow CORS requests from. Enabling this will set the Access-Control-Allow-Origin header to the Origin header if it is found in the list, and the Access-Control-Allow-Headers header to Origin, Accept, X-Requested-With, Content-type, X-HA-access. You must provide the exact Origin, i.e. will allow requests from but not


(boolean)(Optional)Enable parsing of the X-Forwarded-For header, passing on the client’s correct IP address in proxied setups. You must also whitelist trusted proxies using the trusted_proxies setting for this to work. Non-whitelisted requests with this header will be considered IP spoofing attacks, and the header will, therefore, be ignored.

Default value: false


(string | list)(Optional)List of trusted proxies, consisting of IP addresses or networks, that are allowed to set the X-Forwarded-For header. This is required when using use_x_forwarded_for because all requests to Home Assistant, regardless of source, will arrive from the reverse proxy IP address. Therefore in a reverse proxy scenario, this option should be set with extreme care.


(string | list)(Optional)List of trusted networks, consisting of IP addresses or networks, that are allowed to bypass password protection when accessing Home Assistant. If using a reverse proxy with the use_x_forwarded_for and trusted_proxies options enabled, requests proxied to Home Assistant with a trusted X-Forwarded-For header will appear to come from the IP given in that header instead of the proxy IP.


(boolean)(Optional)Flag indicating whether additional IP filtering is enabled.

Default value: false


(integer)(Optional)Number of failed login attempt from single IP after which it will be automatically banned if ip_ban_enabled is true. When set to -1 no new automatic bans will be added.

Default value: -1


(string)(Optional)The Mozilla SSL profile to use. Only lower if you are experiencing integrations causing SSL handshake errors.

Default value: modern

The sample below shows a configuration entry with possible values:

# Example configuration.yaml entry
  api_password: YOUR_PASSWORD
  server_port: 12345
  ssl_certificate: /etc/letsencrypt/live/
  ssl_key: /etc/letsencrypt/live/
  use_x_forwarded_for: true
    - ::1
    - ::1
    - fd00::/8
  ip_ban_enabled: true
  login_attempts_threshold: 5

The Set up encryption using Let’s Encrypt blog post gives you details about the encryption of your traffic using free certificates from Let’s Encrypt.

Or use a self signed certificate following the instructions here Self-signed certificate for SSL/TLS.


On top of the http component is a REST API, Python API and WebSocket API available. There is also support for Server-sent events.

The http platforms are not real platforms within the meaning of the terminology used around Home Assistant. Home Assistant’s REST API sends and receives messages over HTTP.

HTTP sensors

To use those kind of sensors or binary sensors in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived.

All requests need to be sent to the endpoint of the device and must be POST.

IP filtering and banning

If you want to apply additional IP filtering, and automatically ban brute force attempts, set ip_ban_enabled to true and the maximum number of attempts. After the first ban, an ip_bans.yaml file will be created in the root configuration folder. It will have the banned IP address and time in UTC when it was added:
  banned_at: '2016-11-16T19:20:03'

After a ban is added a Persistent Notification is populated to the Home Assistant frontend.

Please note, that sources from trusted_networks won’t be banned automatically.

Hosting files

If you want to use Home Assistant to host or serve static files then create a directory called www under the configuration path (/config on, .homeassistant elsewhere). The static files in www/ can be accessed by the following URL http://your.domain:8123/local/, for example audio.mp3 would be accessed as http://your.domain:8123/local/audio.mp3.

If you’ve had to create the www/ folder for the first time, you’ll need to restart Home Assistant.