Hi, 1st post and totally newbie here.
I installed home assistant on proxmox and im trying to install mqtt but getting error.
Appreciate it i can get some help.
Thank you.
It’s saying that HA can’t reach the internet to download the broker.
I do not have experience with Proxmox or KVM
- Does your host computer have access to the internet?
- Is your router preventing the access of the VM?
- In reading the instructions, step 5 is Under Network Selection, select your bridge. Check to see if you did that.
You’re going to have provide a bit more information
- host operating system
- RAM and CPUs of VM (bare minimum is 2GB and 1, but not much will work, 4GB and 2 is really the min)
- Steps you’ve taken to get this far, like what other integrations have you installed?
You probably can install Mosquitto on your host computer and it will work much the same.
Hey thanks for your input.
I tried chatgpt and it was determined that it has something to do with proxmox as we did change the dns to 8888 and 1111, its still not working.
This is something that should be in the documentation. Perhaps you could provide feedback at the bottom of the Installation linux page. I can understand your reluctance to do so because you fear the same experience I’ve had providing feedback: two years of nothing and issue closed because there was no movement on the issue.
Is it though? A functional DNS is critical to every single thing that needs to reach the internet. If you have a misconfigured DNS you will have issues regardless of operating system, installation method and so on.
YES! It should be part of the documentation
This is my logic: @Botak 's installation apparently failed because DNS ip addresses were not provided (see below)… Like you and me, we assume that the DNS is going to be available. Clearly, in this case, it was not. Therefore, this requirement must be noted somewhere.
unnecessary rant follows:
We all try to write code that is bullet proof If we can’t, we fix it in the documentation. Failing that, in the FAQ’s and failing that, let someone in the forum figure it out.
Below: There are several reasons for DNS not being provided:
- the VM defaulted to the OS’s DNS. The OS’s DNS defaulted to the VM’s DNS
- The VM and OS were not configured or coded to accept DHCP DNS ip addresses
- The DHCP service did not or was not configured to provide DNS ip addresses
I, personally, am a relic from days long before the internet protocol. When we sent messages over the arpanet we had to know every machine name between the sender and the receiver. Names were separated with the “bang” character <!>. The internet protocol had a painful and precarious birth. At that time we only had to know the IP address of receiver. Several years later the Domain Name Server came on the scene and and it was not without its problems … Often times having to fall back on the end-node’s IP address.
When I check my internet connection I use ping 8.8.8.8 which doesn’t rely on a DNS. And the irony of your statement is that the DNS is only accessed with an ip addressed.
I agree. As part of a smooth installation process, any possibilities that cause the process to fail should be tested for and eliminated, or clearly identified and reported, rather than leaving the new user in limbo.
In this case the networking issue has been identified. The large number of threads related to faulty networking configuration in a VM/Proxmox environment would seem to indicate that this area needs a lot more attention.
Mantra: DNS - It’s always DNS!
Maybe it shouldn’t be?
Truly getting a bit sick of seeing the same issues day in day out, indicating the higher up bits are consistently inadequate to guide users in the right path. Even ChatGPT failing to offer solutions seems perplexing (maybe not in hindsight). These forums are overloaded with the same problem, again and again.
/rant (too) Sorry @Botak just had to vent - yours is such a common issue, and you shouldn’t have this pain
Ok, spin this off - the FAQ on how to robustly check DNS is working correctly needs to be in the installation documentation in the network section. Maybe it should be an added step, particularly with the recent advent of Matter and the prerequisites for IPv6 connectivity as well (that will be my excuse to push it)
-Is there a FAQ,
-is it adequate and up to date, and
-does the reference need to be slotted into the documentation, and
-can diagnostic tools be invoked to narrow down the target area to an easy solution?