I'm running HA on a KVM virtual machine on Ubuntu. Recently my computer lost power and the VM ran fine, but I couldn't connect to HA through my browser. In the VM console I saw that there was no IP address assigned. I found this discussion that gave me a place to start https://community.home-assistant.io/t/no-ip-address-showing/290149/42. I tried binding the MAC to the IP in my router settings and using the command 'network update enp1s0 --ipv4-address x.x.x.x/24 --ipv4-gateway x.x.x.x --ipv4-method static' which did populate the IP address and gateway, but I'm still not able to connect in my browser. I used the same IP address I bounded in the router settings. I used the gateway address listed on my TPLink Router webpage under Advanced -> Internet -> Default Gateway, but 'm not sure if that's correct. Any thoughts on what to troubleshoot next?
#[CLOSED] Need help reconnecting to Home Assistant after IP address disappeared
1 messages · Page 1 of 1 (latest)
If you "bind" a ip address in the router you probably want DHCP/auto.
That gateway and ip combo look very weird. What ip does the device have that you try to visit HA from?
Where is the VM run off of? What ip does this machine have?
Thanks for your reply @idle adder it's taken me a while to come back to this project. I will remove the 'bind' and look for the IP of my machine vs. the virtual machine. I am running KVM on Ubuntu.
Okay I have 2 IP address for my machine.
Wired: 192.168.0.184
Wireless: 192.168.0.208
The configuration for my bridge br0 is
network:
version: 2
renderer: NetworkManager
ethernets:
enx00e04c36808c:
dhcp4: false
bridges:
br0:
interfaces: [enx00e04c36808c]
addresses: [192.168.0.184/24]
routes:
- to: 0.0.0.0/0
via: 192.168.0.1
nameservers:
addresses: [127.0.0.53]
parameters:
stp: true
forward-delay: 4
dhcp4: false
I'm using the wired connection for my bridge
The output of ifconfig -a is
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.184 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::386b:21ff:feb2:9c48 prefixlen 64 scopeid 0x20<link>
ether 3a:6b:21:b2:9c:48 txqueuelen 1000 (Ethernet)
RX packets 2777 bytes 205930 (205.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 588 bytes 38037 (38.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enx00e04c36808c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.184 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::fdeb:582f:37f0:c208 prefixlen 64 scopeid 0x20<link>
ether 00:e0:4c:36:80:8c txqueuelen 1000 (Ethernet)
RX packets 118706 bytes 105237844 (105.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 64750 bytes 10378429 (10.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3169 bytes 382694 (382.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3169 bytes 382694 (382.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:ef:48:5f txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether fe:54:00:f0:07:48 txqueuelen 1000 (Ethernet)
RX packets 2039 bytes 177483 (177.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2078 bytes 113741 (113.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp2s0b1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.208 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::b4f3:d060:def5:b54e prefixlen 64 scopeid 0x20<link>
ether 28:37:37:1d:55:38 txqueuelen 1000 (Ethernet)
RX packets 10215 bytes 2198463 (2.1 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1966 bytes 251999 (251.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
and here's my HomeAssistant output: https://imgur.com/a/wgUo5sU
The NIC itself should not have a ip but the bridge that's using it.
So far it's still showing no IP address after switching back to auto
I'm not sure what that means. Does that imply that my configuration is set up incorrectly?
I'd say so.
Unfortunately I'm not familiar with netplan or plain KVM/libvirt. I use the interfaces file on proxmox.
I checked the netplan docs and your config seems okay. Maybe something else is interfering.
I am not either 😢 I'm reviewing the directions I used to set up originally, and it said to use the IP address of the ethernet connection that comes up in 'ifconfig -a', which I think from my output is
enx00e04c36808c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.184 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::fdeb:582f:37f0:c208 prefixlen 64 scopeid 0x20<link>
ether 00:e0:4c:36:80:8c txqueuelen 1000 (Ethernet)
RX packets 118706 bytes 105237844 (105.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 64750 bytes 10378429 (10.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
which seems to have the correct matching IP address used in the config file of 192.168.0.184
thanks for checking
I wonder if I should just try setting the static IP address for HA again, but this time with the correct gateway
I'd check /etc/network/interfaces, systemd networking, networkmanager and libvirt configs.
I don't have the environment to test netplan and stuff like this right now.
I can recomment you to use Proxmox VE if you want a more pain free hypervisor solution.
Are you using ubuntu desktop?
there's no interfaces file in etc/network not sure if that's related to netplan. I am using Ubuntu installed on an old macbook air
Ubuntu 22.04.4 LTS
Desktop or server?
desktop
The interfaces file is pretty much on every OS as far as I know.
I think, I'm using an old laptop
I'm asking because the desktop might interfere as well.
I'd recommend you configure the bridge with the GUI in this case.
okay, that's fair. I haven't used Proxmox VE before but I can learn.
(assuming that's what you are referring to re: GUI)
Okay it's downloading, do you have any suggested references to get started with proxmox ve for this application?
No I meant the ubuntu GUI as in desktop.
Yeah hold on.
- Some information and a link from me: #hardware-archived message
- Playlist: https://www.youtube.com/watch?v=u8E3-Zy9NvI&list=PLT98CRl2KxKHnlbYhtABg6cF50bYa8Ulo&index=3
- Older but also good installation video: https://www.youtube.com/watch?v=Ce0uwBxbVRQ
- Post install: https://www.youtube.com/watch?v=VAJWUZ3sTSI
And of course their docs: https://pve.proxmox.com/pve-docs/
They're quite good.
Awesome, thank you for the suggestion. I'll get started there and come back when I have updates.
Hi @idle adder, I’ve run into some issues installing ProxMox that I’ve stalled out on. Wondering if you have any ideas.
I created a bootable usb with ventoy and installed proxmox, but when I try to reboot it gets stuck. I’m running Ubuntu on an old MacBook Air. Here are some videos of the behavior.
Screen where I get stuck rebooting after installation of ProxMox from USB Drive
Dang, for some reason discord isn’t letting me post pictures or videos
Now whenever I try to restart, I get a black screen with ‘Booting ‘Proxmox VE GNU/Linux’. Loading Linux 6.8.4-2-over … Loading initial ramdisk … and then nothing happens
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
Oh right, thank you for the reminder @idle adder! I tried to upload last weekend but Imgur crashed. I will try again.
At first I tried installing and I got an insecure boot platform error
https://imgur.com/a/nxJzMQ3
Then I tried installing with the GRUB method and got farther but it gets stuck after installation on reboot. At the beginning you can see the screen I get stuck on before trying again.
Photo of the screen I get stuck on
https://imgur.com/a/saZKtGD
Can't see shit. Turn around your laptop 😄
I'm not familiar with MacBooks but you might need the nomodeset boot flag. You can add it by pressing e at the boot menu.
Sorry about that, I will try your suggestion and give the screen a wipe and a turn for the next set of photos.
Hi @idle adder , I tried adding nomodeset, but got the same results. https://imgur.com/a/tE2Kv4U
I followed the directions on this page: https://pve.proxmox.com/wiki/Installation#:~:text=Adding the nomodeset Kernel Parameter,-Problems may arise&text=On the Proxmox VE bootloader,e to edit the entry.
At this point I wonder if I should abandon ProxMox and try going back to working with HA directly from KVM, or maybe try to start over on a Rasberry Pi or maybe even just a Home Assistant Green?
Or install debian and then install PVE on top.
I really don't like SBCs but if I have to use one I'd pick the pi and run HA as do ker container The green is too specialized.
You should have replaced quiet with debug btw. We want some information about what is happening.
I’ve spent 3 months trying to get a consistent HA setup to run, at this point I will take the simple but specialized option. I just want to get my little blinds project working. The issue I’m having now is that I can’t seem to start back up into my Ubuntu desktop.
Thank you for all of your input @idle adder ! I will close this thread now.