home-assistant.io/source/_docs/ecosystem/apache.markdown

layout, title, description, date, sidebar, comments, sharing, footer, redirect_from

layout	title	description	date	sidebar	comments	sharing	footer	redirect_from
page	Apache Proxy	Configure Apache to work with Home Assistant as a subdomain	2016-06-20 13:05	true	false	true	true	/cookbook/apache_configuration/

This example demonstrates how you can configure Apache to act as a proxy for Home Assistant.

This is useful if you want to have:

• a subdomain redirecting to your home assistant instance
• several subdomain for several instance
• HTTPS redirection

{% linkable_title Subdomain %}

So you already have a working Apache server available at example.org. Your Home Assistant is correctly working on this web server and available at http://localhost:8123

Enable mod_proxy_wstunnel by running if you encounter issues while serving Home Assistant through your proxy:

$ sudo a2enmod proxy_wstunnel

To be able to access to your Home Assistant instance by using https://home.example.org, add to following file to /etc/httpd/conf/extra/ as hass.conf

<VirtualHost *:443>
  ProxyPreserveHost On
  ProxyRequests Off
  ServerName home.example.org
  ProxyPass /api/websocket ws://localhost:8123/api/websocket
  ProxyPassReverse /api/websocket ws://localhost:8123/api/websocket
  ProxyPass / http://localhost:8123/
  ProxyPassReverse / http://localhost:8123/
</VirtualHost>

and make sure that this file is read by Apache's main configuration file /etc/httpd/conf/httpd.conf

...
Include conf/extra/hass.conf
...

If you don't want HTTPS, you can change <VirtualHost *:443> to <VirtualHost *:80> or better consider redirecting all HTTP to HTTPS.

In case you are getting occasional HTTP 504 error messages ("Gateway Timeout") when accessing the Web UI through your proxy, try adding disablereuse=on to both ProxyPass directives:

```text [...] ProxyPass /api/websocket ws://localhost:8123/api/websocket disablereuse=on [...] ProxyPass / http://localhost:8123/ disablereuse=on [...] ```

{% linkable_title Multiple Instance %}

You already have Home Assistant running on http://localhost:8123 and available at home.example.org as describe before. The configuration file for this Home Assistant is available in /home/alice/.homeassistant/configuration.yaml

You want another instance available at https://countryside.example.org

You can either :

• Create a new user, bob, to hold the configuration file in /home/bob/.homeassistant/configuration.yaml and run home assistant as this new user
• Create another configuration directory in /home/alice/.homeassistan2/configuration.yaml and run home assistant using hass --config /home/alice/.homeassistant2/

In both solution, change port number used by modifying configuration.yaml

http:
  server_port: 8124
  ...

Start Home Assistant: Now, you have another instance running on http://localhost:8124

To access this instance by using https://countryside.example.org add to /etc/httpd/conf/extra/hass.conf

<VirtualHost *:443>
  ProxyPreserveHost On
  ProxyRequests Off
  ServerName countryside.example.org
  ProxyPass /api/websocket ws://localhost:8123/api/websocket
  ProxyPassReverse /api/websocket ws://localhost:8123/api/websocket
  ProxyPass / http://localhost:8124/
  ProxyPassReverse / http://localhost:8124/
</VirtualHost>

{% linkable_title HTTP to HTTPS redirection %}

Add to your /etc/httpd/conf/extra/hass.conf

<VirtualHost *:80>
  ServerName example.org
  ServerSignature Off

  RewriteEngine on
  RewriteCond %{HTTPS} !=on
  RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [NE,R,L]
</VirtualHost>