Installing Home Assistant OS using Proxmox 8

Community Guides
1036

NOTE: I feel like this is an appropriate thread to post, but let me know if there’s a better one out there.

Hi all, has anyone run into an issue where nothing installs because of “client.timeout exceeded while waiting for headers”? It started when I couldn’t install any add-ons on my instance, then the 23.7.2 HA update, then a fresh Home Assistant install on my Proxmox setup. This all is/has been running on a Proxmox 8.0 VM. This text file has the logs from my attempt to install HA from @tteck’s HA VM script.

Other things of note:

  • The DNS on the pve is fine, I can ping 8.8.8.8 and www.google.com
  • I’m not sure how to check or change the DNS on the HA vm - from the searching I’ve done it sounds like it could be a DNS issue?

Any help is appreciated! :slight_smile:

1037

You mean also any other OS?
Your not using any unusual characters for your settings (hostname/pw/…)?
Did you try the different installation types/options from the script?
Have you tried recreating the VM?

1038

I mean nothing related to Home Assistant installs (such as add-ons, supervisor updates, or new HA vms). I have installed a handful of LXCs with no issue, so maybe it has something to do do with vms?

My settings should all be normal. I didn’t do anything unusual that isn’t predefined in the script. I did try to recreate the vm a couple times, each time by varying the settings in the install script (write through vs. default, host vs its other option).

1039

(Client.Timeout exceeded while awaiting headers)

It’s not DNS
There’s no way it’s DNS
It was DNS

I’ve heard this so many times. :wink:

5 Likes
1040

Haha I was able to ping 8.8.8.8 and www.google.com in the HA console, which surprised me, so I don’t know what to check next.

1042

Not sure if this still is about installing the QEMU agent, but if so it is relatively simple:

Since using the noVNC viewer is impractical I added the studio code server addon to HA. In there you open up the terminal and run your usual install command e.g.
apt update
apt-get install qemu-guest-agent

After that you enable the agent in Proxmox and reboot HA.

After a bit of reading, it seems that this is no longer about the guest agent, but maybe it will help someone.
Fortunately, this allows me to ask an off-topic question myself:

I set up a new Proxmox server a few days ago. It uses an Asus Prime B550 Plus motherboard with an AMD R5 pro 4650G. My problem is that the “sensors-detect” command is unable to find any MB or CPU sensors.

It seems that Asus doesn’t provide any information about their motherboard chips and the community behind the lm-sensors program has given up on supporting them. Obviously I still want to know the CPU temps and if possible the HBA temps.

Does anyone here have a solution for getting temp readings from an Asus board?

1 Like
1043

Hello all, thanks for the Guide!

Currently I’m running Debian 12 in a mini PC (GEEKOM MiniAir 11) and installed Proxmox 8 following this Proxmox Wiki.

Following the guide here everything seems to work up until the end when the following error pops up and the HAOS VM is not created:

[ERROR] in line 427: exit code 255: while executing command qm start $VMID

Appreciate any help or guidance on troubleshooting.
Im new on the board and the automation scene, so Hello, World!

1044

My suggestion is to strictly adhere to the instructions provided in this guide for installing Proxmox.

1045

I’m curious to know the output when the command dpkg -l | grep qemu is executed in the Proxmox shell.

1046

Hi, 𝙩𝙩𝙚𝙘𝙠𝙨𝙩𝙚𝙧 for sure, here’s the Output:

ii  libproxmox-backup-qemu0                 1.4.0                              amd64        Proxmox Backup Server client library for QEMU
ii  pve-qemu-kvm                            8.0.2-3                            amd64        Full virtualization on x86 hardware
ii  qemu-server                             8.0.6                              amd64        Qemu Server Tools

Thanks!

1047

Looks correct, are you using SSH when you execute the script?

1048

Hmmm I would say no, as I don’t start with ssh, just run it as followed:

sudo bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/vm/haos-vm.sh)"

I did install Debian with SSH server enabled though.

1049

In my view, opting to install Proxmox as the operating system is the most straightforward approach and helps prevent potential future complications.

1 Like
1050

Yes, agree with you, I usually take the least hassle approach, but I’m aiming at a dual boot hence Proxmox over Debian.
I tried the Script these time avoiding Starting HAOS after install so it is in Proxmox but when starting… it won’t, sigh.

1051

I found my solution to this issue in this forum post: Solution to hanging “Preparing Home Installation” screen. Just want to close this issue for those troubleshooting in the future.

1052

I don’t remember if I got the same error message … but in my case it was because my hostname contained an invalid character - tried again with a hyphen instead of underline and it installed OK.

1 Like
1054

I only used step 2 to create the VM, since I already have a fresh Proxmox running on a NUC 13 and wanted to move Home Assiatant away from my Raspberry Pi 4. I encountered two issues:

1: The default VM starts with a 32GB disk. During the restore it appeared the disk ran out of storage and left me with a barely working HA. It took me a while to find out it was storage related instead of SSL. HAOS is very limited for troubleshooting.

2: is a Proxmox thing in combination with ZFS and RAM ballooning. I thought it would be nice to give HA a bunch of RAM (12 GB) to speed up the process. With a total of 32GB RAM and only this VM running, this shoud’ve been plenty. However, during the restore, the Linux Out Of Memory Killer kicked in and killed the VM.

After this, and a good night of sleep, I finally managed to move Home Assistant away from the RPI 4 with the “unsupported OS” Ubuntu and it’s 2 GB of memory.
Thanks for the script!!

1055

Worked like a charm for me. Proxmox 7.4-16 on an HP Mini PC. Thank you very much for this gentle onboarding.

1056

BTW: you have to --force the qmrestore to allow restoring onto another VM id.

1057

Responding to a post that’s nearly a year old, I’d like to clarify that the mentioned “backup” in that post pertains to the backup created within Home Assistant, not a backup of a virtual machine.