HassIO Websocket configuration via LetsEncrypt Docker on Unraid (linuxserver letsencrypt) - cajuncoding/HomeAssistant GitHub Wiki

My system is fully configured for external access and everything worked well except for the HassIO plugins that attempt to establish web socket connections to /api/hassio_ingress.... I identified these failures by looking at the debug console of developer tools in my Chrome browser.

I was having a similar issue as those in the discussion on the HassIO issue here: https://github.com/home-assistant/hassio-addons/issues/1043#issuecomment-656590946

And, also similar question posted in the HomeAssistant forum here: https://community.home-assistant.io/t/unable-to-connect-with-nginx-reverse-proxy/14875

However from tips on the HomeAssistant forum as well as the issue (above) I realized that if I access directly via IP address on my local network then the add-ons suprisingly worked. The developer tools in Chrome were no longer showing the web-socket errors... So finally I had a clue that it was in fact related to my routing and reverse-proxy setup!

My particular issues were with the Terminal add-on & the Visual Studio Code add-on which I could not get to work at all; so I ended up just un-installing them. But, I'm sure the root cause to many of these are all the same issue related to HassIO and reverse proxy configuration.

In my latest setup, I'm using LetsEncrypt Docker (linuxserver/letsencrypt) on an Unraid server for all reverse-proxy routing, and had gotten it all working well, using the sample configuration for HomeAssistant provided in the docker: .../nginx/proxy-conf/homeassistant.subdomain.conf.sample

However, that sample was setup for the standard core HomeAssistant install and not HassIO, which I've finally figured out requires additional proxy configuration for websockets to the api/hassio_ingress route.

So, I finally got my add-ons working by adding the following location handler/configuration to my Nginx proxy configuration (in addition to the other one for the default HomeAssistant websockets api route: api/websockets; just add this below the first in your configuration):

Note: For security & best practices (narrow scope), I added this section to specifically only hanlde the hassio_ingress route, as opposed to just allowing all requests at my root location (wildcard for any request to my HomeAssistant) to be upgraded as websockets which was mentioned in the HomeAssistant forum.

# Duplicate websocket configuration specifically for HassIO add-ons (e.g. /api/hassio_ingress)
# Details of how this config works can be read here:
# https://www.serverlab.ca/tutorials/linux/web-servers-linux/how-to-proxy-wss-websockets-with-nginx/
location /api/hassio_ingress {
        resolver 127.0.0.11 valid=30s;
        set $upstream_app 192.168.1.???;
        set $upstream_port 8123;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_set_header Host $host;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
}

Et Voila! My add-ons were up and running and firing on all cylindars!

Now Geaux Code, CajunCoding