Hello! Set this up in Unraid to use the VM for compatibility with Bluetooth drivers (seems to work a lot better than the official Docker). All working okay, however when I set it up to use the reverse proxy, it just takes me to a "nocache" page with an SSL PROTOCOL ERROR message.

Any way we can get this to work? It worked with the standard Docker install but I guess the redirect to the VM is making it a little more complicated...

My configuartion is as follows

Cloudflare DDNS > Zero Trust tunnel > Swag > Homeassistant Docker, all protected by Authelia.

 

Thanks!


***Edited to remove the "Windows" part out as I meant to put "Unraid"!

Edited October 30, 20241 yr by Adamtiley

3 hours ago, Adamtiley said:

Set this up to use the "Windows" VM for compatibility

 

Isn't that completely out of scope for this thread? SI1's container is a tool to install HA's own HAOS VM. HA on Windows is very different, and IMO, not something I'd ever trust to run any kind of home automation setup.

 

If you want to do yourself a huge favor, use SpaceInvaderOne's container to install and start the expected HAOS VM. Set up a Tailscale account, install the Tailscale plugin in Unraid and set it up to use your account. Install Tailscale on your mobile devices.  Stop using DDNS,  and the tunnel, plus you won't need Authelia for HA.

 

 

Edited October 30, 20241 yr by Espressomatic

J

21 minutes ago, Espressomatic said:

 

Isn't that completely out of scope for this thread? SI1's container is a tool to install HA's own HAOS VM. HA on Windows is very different, and IMO, not something I'd ever trust to run any kind of home automation setup.

 

If you want to do yourself a huge favor, use SpaceInvaderOne's container to install and start the expected HAOS VM. Set up a Tailscale account, install the Tailscale plugin in Unraid and set it up to use your account. Install Tailscale on your mobile devices.  Stop using DDNS,  and the tunnel, plus you won't need Authelia for HA.

 

 

I actually didn't mean to put that in there. It's set up in Unraid, I'll update my comment accordingly!

5 hours ago, Adamtiley said:

however when I set it up to use the reverse proxy, it just takes me to the "lovelace" landing page.

 

Just to confirm...  Have you done both of the following?

 

1. Set up your reverse proxy to point to Home Assistant's IP:port?

2. Set Home Assistant to allow proxy connections by adding something like below to your configuration.yaml?

 

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 10.8.8.2
    - 10.8.8.0/23

 

In above example, a specific proxy IP or an entire CIDR range.

 

 

Edited October 30, 20241 yr by Espressomatic

I had an issue with it since my original comment, where it wouldn't load the display when I VNC'd onto the VM, so I reinstalled it and now it shows an ERR_SSL_PROTOCOL_ERROR, and a message saying it sent an invalid response.

 

The proxy.conf for homeassistant in Swag/nginx is correct (it was working before when I was just using the official docker), and I've added my network's CIDR range to the configuration.yml from within the VM using the file editor plugin so that all looks correct.

Edited October 30, 20241 yr by Adamtiley

Swag and Authelia are seemingly working. The external URL is hitting the Docker container because it redirects to the VM, testing with a different browser, it hits Authelia so that's all working. But something in the Homeassistant config isn't liking HTTPS and SSL.
The external URL redirects, It hits it, and for a split second shows the Homeassistant logo, and then throws the SSL error.

 

Firefox shows: SSL_ERROR_RX_RECORD_TOO_LONG

 

 

Edited October 30, 20241 yr by Adamtiley

Also one more thing, here is the entry in the log on the HA VM: when I attempt to connect from the external URL:

 

2024-10-30 21:04:54.284 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 377, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 563, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:

    b'\x16\x03\x01\x06\xc0\x01'
      ^

On 10/30/2024 at 5:06 PM, Adamtiley said:

Also one more thing, here is the entry in the log on the HA VM: when I attempt to connect from the external URL:

 

In your reverse proxy setup did you make sure to specify the HA host URL (on port 8143) as HTTP and not HTTPS?

 

Because that error sounds like you're trying to load an unencrypted resource using HTTPS.

 

 

 

Edited November 2, 20241 yr by Espressomatic

So all of my other apps are "http" and Cloudflare connects to Swag using SSL and then forwards onto the relevant app with the upstream settings in the conf files from my understanding. This makes them accessible from an external URL using SSL.

The linuxserver HA docker I was using before worked perfectly but I decided to switch to this because it seems to work better in general. 
I've since set up a separate NGINX server using the add-ons in HA and that works if I direct the Cloudflare tunnel directly to the ip:port. The issue with that is that it's not going through the host server, and thus Authelia is unable to see it. 

 

I wanted to set it up so that Cloudflare points directly at SWAG and then SWAG passes through to the docker which then connects to the VM, all while being using SSL and being protected by Authelia. 

 

Unsure if this is possible but please let me know if it is.

 

Thanks

Edited November 3, 20241 yr by Adamtiley

Actually never mind, it's sorted haha

 

I have it set now so that Cloudflare points directly to the VM, with NGINX doing it's thing on it.

Authelia does work I just needed to make a slight change in the setup.

 

All working as it should!  Thanks for your help

Sounds fine and should work like you mention at the end.

 

SSL/HTTPS with FQDN from browser to auth and proxy. Proxy to Home Assistant HTTP (no SSL) IP:port

 

 

Hello, I am really REALLY sorry for posting this here as I know it's offtopic, I just wanted to get spaceinvaderones attention regarding nextcloud-aio-mastercontainer as it doesn't have it's own support page.

I just wanted to ask, if I have the linuxserver.io nextcloud container up and running, is there a guide/simple way for me to migrate everything to the nextcloud-aio-mastercontainer container?

Again, apologies for it being offtopic, just the nextcloud docker doesn't have it's own forum page, and I don't know any discords or anything spaceinvaderone is in.

Hello everybody,

 

Now posting in the right thread. 😛

 

First time post. Installed UNRAID today 🙂 I got my first array running and thought homeassistant in a box was right up my ally 🙂

 

Unfortunately it didn't work. I didn't change any settings and i got: 

 

HomeAssistantinabox: 08-11-2024 16:45 Home Assistant 6 Failed to setup the VM. Required files are missing.

 

Did I do something wrong?

 

Many thanks for the feedback

 

EDIT: something else is wrong:

when doing the manual way of installing the VM (

) i get

"Waiting for the Home assistant CLI to be ready.

[WARN] Home assistant CLI not starting! Jump into emergency console..."

setup is 2 drives in pool, 1 cache drive, nothing else really changed.

Edited November 9, 20241 yr by stekkes

Something broke, does not work anymore. It did work earlier today, but then a update came, that could not be installed. So since I was just installing it at not even done configuring anything, I just deletet everything and installed from scratch... Now I only get this with a fresh install:

Same update that failed on the first installation, 2024.11.3, that came today:

Edited November 11, 20241 yr by Cirion

Yes, looks like a lot of people with same problem:
Cannot install supervisor 2024-11-3 hassos - Installation - Home Assistant Community

Guess I'll hold off updating for now then! Thanks guys!

They must have pulled the 11.3 update as I'm on 11.2 and don't see any update notifications for 11.3.

 

This is a perfect example of why the Supervisor update process in Home Assistant is flawed and needs to be replaced. I gave up arguing about it over a year ago, hopefully this latest development brings the issues/dangers back to light.

 

 

Edited November 11, 20241 yr by Espressomatic

For the life of me I cannot seem to access the homeassistant gui to complete the setup, When I click on web ui I get "this site cannot be reached" took too long to respond. I've tried re-installing and uninstalling both the home assistant in a box container and vm as well. Just kind of at a loss as to what's going on and am looking for any possible guidance. I am not sure what if any logs to provide at the moment but I can provide them as needed. Thanks!

i have troubles installing the app.

 

everytime single time this error occurs:

 

 

 

Hi, first of all - awesome container and VM! It installed without problem, restored HA from backup, and away you go! I had some discovery around enabling my old Conbee II as /dev/serial/by-id/, but that was just a wrinkle.

 

I did run into one issue to let you know about. The default VM Name is "Home Assistant", which presented a problem when I tried to install the vm-babysitter app to back up my VMs. That app, and I'm guessing perhaps others, does not work with spaces in the VM Name and the VM path. I tried to rename the VM and paths to "Home-Assistant" but in  the end it was easier to nuke the whole container + VM and re-install from fresh with the name with a dash in it. Save yourself some trouble and create the VM name with no spaces in it.

Edited December 11, 20241 yr by WalkerZ

I have installed and removed this combination multiple times. It will not get an IPV4 address. I tried adding a static ip in pfsense using both the docker macs and the vm machines mac addresses. No joy.

 

I gave up on that and installed a qcow2 image directly. In one configuration it did get an ipv4 address and I could load the observer page at 4357 but it still would not load 8123. So that was a fail again.

 

I pretty much gave up.

I don't have any experience with this container for setup, but WRT Home Assistant, it's always been as simple as downloading their image, configuring a basic VM (OVMF bios!) in Unraid and firing it up. IMO, the most important part of the VM config to not overlook is this:

 

 

Always Bridge network.

 

The one potential hiccup can be at startup, where Unraid may not boot the image - that can be solved by turning off Secure Boot in the boot manager. Once it boots, it always gets an IP - if it doesn't then something's wrong with one's DHCP server or Network config in Unraid isn't set up correctly (br0 bridge).

 

 

Hey, I have a small problem. I have activated the usb passthrough for my zigbee usb stick in the virtual machine as described in the video. It works like a charm.
However every the VM is rebooted, I have to edit the VM config. How do I save this permanently?

On 12/18/2024 at 4:30 PM, Espressomatic said:

I don't have any experience with this container for setup, but WRT Home Assistant, it's always been as simple as downloading their image, configuring a basic VM (OVMF bios!) in Unraid and firing it up. IMO, the most important part of the VM config to not overlook is this:

 

 

Always Bridge network.

 

The one potential hiccup can be at startup, where Unraid may not boot the image - that can be solved by turning off Secure Boot in the boot manager. Once it boots, it always gets an IP - if it doesn't then something's wrong with one's DHCP server or Network config in Unraid isn't set up correctly (br0 bridge).

 

 

I do get an IPv4 address but I can not open the WebUI. I was thinking, if it was to the IPv4 address the VM gets: 192.168.122.154 - normally my Range ist 19.168.178.xxx . I am to much of an noob to know, if that could be the problem. Note that I have a Fritzbox and ran into the mac vlan problem when I startet with unraid some month ago.

So I looked into the settings of the VM, It shows me:

 

 

For the Docker I gave a static IP:

 

Also here is my unraid routing table:

 

 

I was thinking about changing in the VM the network source from virbr0 to vhost0, but I am unsure what to do with the network model.

 

Can anyone help me? :)

 

Edit:

OK. I know that some of you have told me, not to change settings, if I don't know, what would happen... But I just changed the network source to vhost, and let the network modell unchaged. The VM now got an IPv4 from my fritzbox within the range I mentioned before. I can now open the WebUI of Home Assisstant. Thats great

Now I will have to get into Home Assisstant. For starters I have only two light bulbs from "Paulmann", one "delock" wifi socket outlet with tasmota and a zigbee/matter/tuya gateway. Hopefully I will get them to run

Edited December 20, 20241 yr by BastiKA84
Solved my problem myself.