If I check the Proxmox-WebUi everything seems fine:
The VM makes a Backup every 24h firstly I used the stop method. After some time I switched to snapshot this helped a little bit. I am now quite lost and I don’t know which things are the problem on this VM. The VM has 6GB of ram and 2 cores assigned which is more than enough (Hass is really snappy). The issue above is fixeable with a full reboot of the Vm.
The Proxmox node is running fine - all other LXC / VMs are running totally fine!.
Apple did not even pop-up in my mind , have been avoiding everything related to apple products since early Millennium, actually when they launched OS X 10.0 , which could be the only positive they did, around that time
The error message provided is a failure of the browser or client resolver to successfully resolve the name being connected to.
This isn’t HA, and it might not be Proxmox either, but you’ll need to check your DNS server and ensure there’s a record for the hostname you’re attempting to access. If you’re entirely reliant on the .local domain namespace and that’s the thing that’s failing, look at your network and how it handles mDNS/Bonjour.
which is in a mixed environment, mDNS with MAC, Linux and most likely also a Windows Machine involved, is not “trivial”
But as Nick mention, there is a lack of HA logfiles, and no mention what or where the logfile-pic comes from, or what he assume/think it indicates
I doubt it would be fairly simple to guide OP to “penetrate” possible mDNS issues, as he is not even familiar with HA-CLI, and/or still haven’t been able to retrieve logfiles from HA
Install-Method: Tteck script Console pictures: All of them are taken from the WebUI (Proxmox->Console)
Picture is from HA Companion app
Picture is from the Console accessed via ProxmoxWebUi
Picture the same as mentioned in 2.
Regarding the first Message I will try to do the fixes which I found online. Lets focus on the crashing
I checked the files and I can’t find any logs before 02.01.2024. I can restore the backup and try to get them. Which other information you need?
I didn’t post in the Proxmox posting - I don’t like crossposting.
Right, i guess you also read the log-pic carefully your self
It’s from an OS, which i don’t know (doo to your ways of presenting your use-case), the “audit” there mentioning something about “subj=unconfined key” … Prior to that you’ll notice the “command”, which lead you to /runc … in other words Container Handling … which i don’t know, as you haven’t “Spec” your environment either, I.e, add-onns, integrations etc. ( if it’s HA’s OS )
PS: The “crash” you experienced could then be caused by … what ever … " ha host update ", " ha core update ", " ha supervisor update " Should fix the “Native Default Parts”
If you still have issues, you have to dig into your add-ons, integrations, customization, and your imagination in regards which of these factors could cause the experienced behavior … And also try to “separate” Common Network related issues, even thou it might be related/caused by the same …
Don’t, atleast not before you have gone through your logfiles, you have host, core and supervisor in the UI ( And also available through the CLI ! , Beside you also have logfiles in ALL your ADD-Ons !, and there is the home-assistant.log and home-assistant.log.1 And .fault … in your config (homeassistant) folder
Do it now, do it after a crash (your definition) , and do it after a restart.
And if you don’t take the opportunity, to update host, core supervisor and all your add-ons, re-download your integrations and check the bunch of logfiles after this , you are basically requesting help/assistance upon neglective behavior
, have been avoiding everything related to apple products since early Millennium, actually when they launched OS X 10.0 , which could be the only positive they did, around that time
which is in a mixed environment, mDNS with MAC, Linux and most likely also a Windows Machine involved, is not “trivial”