I installed HA up to 20 times now as a Proxmox VM and in every case the same issue occured: the addon-store remains empty. I worked hard on the forum and found a lot of comments, hints, advice and different installation methods and I gave them all a try.
What I tried:
installation with tteck’s script (HAOS)
installation without script using guides in this form based on actual ISO as provided on home-assistant.io (qcow2 and vmdk as an alternative)
installation as supervised as provided in this forum
installation as supervised as provided in this forum (incl. network-manager configuration on dns)
set dns servers to 1.1.1.1 / 8.8.8.8 or 8.8.4.4
edited resolved.conf as provided in this forum
Fritz.Box DNS config: tried recommended IP by ISP and Cloudflare or Google alternatively
Fritz.Box: tried with enabled and disabled IPv6
disabled IPv6 in HA
Technologies:
Proxmox native installation with 8 different VM up and running (one Win 11 and mostly Debian 12 Bookworm)
VM configuration follows standard recommendations
DSL-connection with Fritz.Box (actual image, no VPN), set to DHCP
fully wired connection
Results:
every installation method ends with same result:
git with an error code 128 can mean a lot of things. It is sort of a catch all that have not been catched by other error handling.
Basic checks are the first ones to be made, like
space on your disk. HA should have at least 32Mb and I would suggest 64 to hold a few backups too (off-site backups should still be done!)
ram. HAOS should have at least 4Gb to run with addons
time. Make sure that HAOS can retrieve the correct time, because encryption will fail if the difference is more than a few minutes off and that will kill the encrypted connections, like the HTTPS ones.
cores. These might not be that important, but if you go down to only one, then you might have connections time out, because the system is so bugged down at times, that it will miss a reply in the allowed time set by the other end.
DNS. HAOS normally use the ones provided by your router, but at times these are misconfigured and then HAOS might revert to some hardcoded fallback servers, which you might have blocked in your firewall.
You can get it to run on 2Gb, but you have to be selective in your addon choice.
Grafana can easily eat over .5Gb alone and influxdb can go even further.
Node Red is also a hungry.
ESPHome does not seem to use that much memory, but I have not watched in during a compile.
I would guess its usage increases then.
With all due respect, running any of the add-ons you suggest in HA (grafana, influx, node-red, MQTT) is counterproductive. Under Proxmox, you would run these outside HA, in their own LXC as you then have full system management and observability control.
In a virtualised environment you run most add-ons outside HA, reasons I hope are self explanatory from a systems/data management and high availability perspective.
Followed your instructions in detail - except DHCP MAC reservation due to my fritzbox which doesn’t support that. Static IP-address done by IPv4-address reservation.
Hmm, the fd00 name server is a link-local address, but it is not the same as your gateway.
This might be an issue, but it is hard to tell without a proper overview of your IPv6 network.
For now try to disable IPv6 and reboot the host (not just the core).
Then check the “ha network info” again to see if the IPv6 settings have changed.
IPv6 always have preference over IPv4.
There’s no EERO or similar in use. Just my fritzbox as DSL modem. As an attempt I set it to “exposed host” to disable its firewall. unfortunately no success.