This repository was archived by the owner on Nov 2, 2024. It is now read-only.
Homeassistant OS VM - virtual network interface get's wrong IP on install #1339
Replies: 2 comments 6 replies
-
You're looking at the internal Docker network. |
Beta Was this translation helpful? Give feedback.
6 replies
-
Just tried to use Version 10.0 RC of Homeassistant instead V9.X. No problem here... For sure no issue with your script. Thank you very much for your work and help. You can mark the topic as resolved. :-) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
first of all thank you so much for these great scripts that make working with Proxmox a breeze!
Thank you for all the work you invested and still do!
I used many of your scripts already, mostly containers, and now I tried to install the homeassistant OS VM.
The installation went smooth and the VM started with no obvious issues.
But when I tried to look up the ip address of the VM in the dashboard, I recognized, that the ip it received uses a completely different ip address range than I use in my network.

My network is at 192.168.x.x
The "nmcli con show" command doesn't list any network interfaces.
I am running Proxmox 7.4-3 on a supermicro server with 128 GB RAM, 16 cores, and 8 network ports installed.
I didn't experience the behavior with my other VM's on the same server.
I'm pretty sure the problem is sitting in front of the screen ;-) But can somebody assist me in seeing able to access the home assistant dashboard?
Thank you very much in advance!
Simon
Beta Was this translation helpful? Give feedback.
All reactions