I did my HA was ruyning just fine for 1 year installed on myu ubuntu server 20 witch that scrip and watchtower!
It may continue to still run fine, however, it also may break at any time if the Supervisor checks for software, like Watchtower, that shouldnāt be installed.
So was mine but if you want your HA to be in a supported state, lose watchtower. It doesnāt work any better than docker compose with a crib job anyway
Is anyone using a gnome version of Debian rather than headless. Any reason this wouldnāt work?
I get stuck on 2.2. I get
The following packages have unmet dependencies:
network-manager : Depends: libpam-systemd but it is not going to be installed
Depends: policykit-1 but it is not going to be installed
My source list looks like this.
deb http://deb.debian.org/debian buster main contrib non-free
deb-src http://deb.debian.org/debian buster main contrib non-free
deb http://security.debian.org/debian-security buster/updates main contrib
deb-src http://security.debian.org/debian-security buster/updates main contrib
And Iāve tried āsudo apt-get -f installā but always get this error. How do I solve it?
I followed the guide today and had the same problem.
The error is at step 1.14 not configuring the package manager.
I had to enter then manually into sources.list
After that it all worked fine.
I see youāve updated the guide now @kanga_who, thanks for your work on this.
I was dreading moving from lubuntu to Debian but it wasnāt too bad at all.
Trickiest part was getting Plex working again, as my media drive is NTFS and I had to install drivers for NTFS to get Debian to see it.
I hadnāt anticipated that as Ubuntu / lubuntu picked it up straight out of the box
I received my new SSD and thought the installation of Debian 10 would be a cakewalk ā¦ but Iāve encountered an unexpected hurdle.
The problem is Debianās installation process stops immediately after configuring the network connection via DHCPv6. In contrast, if I boot Debian Live (from the same attached USB flash drive), it quickly displays the gnome desktop and the machine has established a network connection with both IPv4 and IPv6 addresses (and I can browse the web).
- Iām installing Debian 10 on an old laptop from an ISO image of Debian Live burned to a USB flash drive.
- The machine needs ānon-freeā firmware so I have all of the most current drivers located (as per Debianās instructions) in a āfirmwareā directory in a second USB flash drive.
- It breezes through the installation process, identifies the laptopās internal Ethernet and Wi-Fi adapters (I select Ethernet) and proceeds to get the ānon-freeā firmware from the second USB key (its light flashes).
- After it completes āConfiguring network via DHCPv6ā, it displays no further progress. I let it sit for several minutes but it does nothing else.
Iāve tried both the Graphical and non-graphical installation options, in the hope the non-graphical one gives me more options, but thereās no difference. Both get stuck at the same point. Iāve repeated the installation process several times with the same result.
As a point of reference, I had previously installed Ubuntu 20.04.1 on the same PC (with a different hard-drive) and it didnāt experience this problem. Whatever is stopping the Debian installer didnāt stop the Ubuntu installer.
What can I do to either get past this āsticking pointā or diagnose the problem more thoroughly?
I had this problem as well. I found the fix here:
Install hangs at āConfiguring the Networkā : crunchbangplusplus (reddit.com)
Even though that fixed this issue for me, I still didnāt get past my other problems. After trying for a few days, I moved back to my trusty Pi 3. I hope you can get it up and running.
1 Like
Are you able to press ALT+F2 and get a new prompt open and issue this command? If so, will it proceed with the install?
kill-all-dhcp
1 Like
Thank you both for the prompt replies and suggestions.
I followed the instructions in rvoosterhoutās link and that helped to nudge it past the āwaiting forever for DHCPv6ā and on to acquiring an IPv4 address. I suspect kanga_whoās suggestion would have done the same (with fewer steps).
I now understand why it was stuck (just not sure why Debian Live doesnāt get stuck in the same spot). Iām happy to report itās now churning through the process of installing itself on the SSD.
Thank you both! Soon my HA server will get a major technology bump ā¦ from running on an 11-year old laptop (Core2 Duo, USB2, hard-drive) to a 9-year old laptop (Core i3 2350m, USB3, SSD). 
2 Likes
When i was following this guide and installed HA my machine was on wifi with manually defined ip address (i defined it in ui)). Is there a way to force this machine to use ethernet without changing ip address?
After the installation is there a way to preserve it so if something goes wrong i can go to the working version? Ive got snapshots sure but how can i avoid reinstalling debian in the future?
Is there a method somewhat similar to VM when you can just copy the state of the drive in the file?
I wonder if it is quite probable or unlikely that something may goes wrong with HA after running this command every months:
sudo apt update && sudo apt upgrade -y && sudo apt autoremove āy
Can this command be run from terminal addon within ha?
I did it with nmtui via ssh terminal.
Fixed IP address in the router.
thanks!
could you share any more details please?
With me, all devices in the LAN get an address from the router.
You can also specify a fixed address in the supervisor.
(I havenāt tested it yet)
Also check out nmcli. nmtui is such a small surface, operated by arrow keys, tab and enter.
Iām trying to install HA on a zotac mini pc. Iāve gotten through all the debian installation but get an error when I get to the actual HA installation script. It looks like itās telling me that the network is unreachable, but Iām pretty sure itās not considering the internet was working just fine during the installation process. Any thoughts?
[info]
[info] This script is taken from the official
[info]
[info] Home Assistant Supervised script available at
[info]
[info] https://github.com/home-assistant/supervised-installer
[info]
[info] Creating NetworkManager configuration
[warn] Changes are needed to the /etc/network/interfaces file
[info] If you have modified the network on the host manually, those can now be overwritten
[info] If you do not overwrite this now you need to manually adjust it later
[info] Do you want to proceed with that? [N/y]
y
[info] Replacing /etc/network/interfaces
[info] Restarting NetworkManager
[info] Install supervisor Docker container
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.1.1:53: dial udp 192.168.1.1:53: connect: network is unreachable
Could be a DNS issue on the Debian machine. Try this.
sudo nano /etc/resolv.conf
Change nameservers to 8.8.8.8, Ctrl+X to save, reboot the machine, then try running the script again.
Interesting, I tried editing resolv.conf, but when I look at it after a reboot (or even after I edit it and then look at it immediately after saving), it looks like NetworkManager has overwritten it and defaulted back to my router ip address for the nameserver.
# Generated by NetworkManager
nameserver 192.168.1.1
The file /etc/network/interfaces is the one to edit. Look at the CLI example in this article. Itās consistent with your output from the installation script.
https://linuxconfig.org/how-to-set-a-static-ip-address-on-debian-10-buster
I did not install resolveconf (an option in the CLI steps), but the following reference describes why your file is being overwritten. It also provides other options for configuring static IP addresses.
2 Likes