I love my #raspberrypi army (1xPi1, 1xPi2, 2xPi3, 1xPi4, all running different things), but on a drunken whim I ended up sniping a bare bone Intel nuc5i5ryh for $20 and threw in ram/HDD i had sitting around and that thing is a beast
threw #proxmox on it and have basically consolidated the functions of all those #Pi boxes into one VM with processing and memory to spare
I have two choices to run Home Assistant on my future #Pi5. With HAOS and as a Docker container. My idea was initially HAOS, but the Pi5 will be equipped with an SSD, have 8GB and may be able to take on other tasks. That's why a OS Lite 64 bit might be more flexible. Are there any major advantages to HAOS (apart from being efficient with resources)?
This past week I got to learn all about Proxmox Helper Scripts, a wonderful collection of scripts to help you automate common tasks with Proxmox along with LXC container installs!
@technotim I’m new to #Proxmox and can’t live without these scripts :-). I’m installing my Debian VMs too. Thanks for the video, I learned a few things.
Current #HomeLab status: I‘m making progress very slowly. The server is assembled and up and running Proxmox 8. Yesterday I‘ve build a custom NixOS installiert that has my SSH key pre-loaded. That way I can boot a VM and set it up using nix-anywhere. Tonight I‘m planning to try this out the first time. #proxmox#NixOS#linux#SysAdmin
#Proxmox just generates a #UUIDv4 like
3b7d2d2c-3732-41db-a678-8bc4aeaf9155 as a secret for auth tokens? 😱
This looks a lot like a bad security practice to me, especially when RFC4122 says:
"Do not assume that UUIDs are hard to guess; they should not be used as security capabilities (identifiers whose mere possession grants access), for example. A predictable random number source will exacerbate the situation."
Inzwischen läuft #Homeassistant als VM in #Proxmox stabil und nahezu komplett in der Funktion.
Auch die USV ist verbunden.
Es fehlt eigentlich nur noch Bluetooth.
Gefühlt läuft es deutlich stabiler und performanter als auf dem @homeassistant blue.
For quite a while now, I have relied on terminal into my Windows Subsystem for Linux on my main workstation, as my daily driver. While it works all right for most cases, there are certain compatibility issues that requires a "... in WSL" search term for documentations/issues.
Close to a month now I have been using a #Ubuntu#terminal only VM on my #homelab#Proxmox cluster. For ones who can roll this out, this seems the best approach.
Upgraded the homelab’s 10gb switch to the UniFi EnterpriseXG. Not only do I have more 10gb ports now, I also have far fewer SFP+ modules in use, and the switches are all matchy matchy.
Also, I swear the whole rig has less latency now. I can’t prove it, but it sure feels snappier.
Okay. So despite everything, I have been successful in giving my main proxmox server more votes. That should make it okay to just have 2 nodes from what I've been told and have read in their forums.
I did read the documentation for un-clustering. I have a hot take for the #proxmox devs: it should be as easy to uncluster as it is to cluster.
Am gestrigen Regentag nahm ich meinen Mut zusammen wollte meinen #Heimserver von #Proxmox 6.4 auf 7.x updaten. Viel zu spät war ich dran, aber es lief seit Jahren alles so schön fehlerfrei. Leider fror das Upgrade bei 58 % ein. Ich konnte herausfinden, dass es etwas mit „memtest“ zu tun hat. Nachdem ich diesen Prozess abschoss, lief das Upgrade bis zum Ende durch jedoch nicht fehlerfrei: Ich kam nicht mehr ins Proxmox-Gui, da „pveproxy“ und „pveservice“ (oder so) nicht mehr starteten. 😞 1/3
Ich steuere meinen 3D-Drucker mithilfe von OctoPrint, welches als LXC auf Proxmox läuft. Proxmox hat dabei seinen eigenen Desktop, mit dem man auf den Webhost von OctoPrint zugreifen kann.
Just added #Ubuntu Server 24.04 - https://github.com/dustinrue/proxmox-packer. I need to update the page on my site with some details about how to configure cloud-init in Proxmox yet. But long story short, you must set the ip config to enable DHCP. RHEL variants don't need this.
This post is really a small collection of thoughts about Proxmox when used in a home lab situation and home labs in general. I was originally going to post this to Mastodon only but it didn't fit in a single post.
A lot of people (at least what I see on reddit) build Proxmox systems with shared file systems like ceph, even for home lab use.
DO NOT #update to #ubuntu#24.04 on #LXC if you use #proxmox, the containers will NOT start. I believe this is something that needs to be fixed by the proxmox team as they seems to be checking for ubuntu version manually in a startup script
Today I pondered something: Proxmox and others boast native ZFS integration as one of their strengths. Many Proxmox features rely on ZFS's unique capabilities, and many setups are built around them. If Oracle were to send a cease and desist tomorrow, how would the situation unfold?
I've got the 192.168.1.x network with HA in there. Now, I've got an #OpenWrt router with the IP 192.168.1.190 creating 2 new networks: 192.168.100.x. I now want to get the HA into the 192.168.100.x network, but I can't connect it physically, as both the OpenWrt and HomeAssistant run in containers/VMs on #proxmox. I tried experimenting with IP routes, but no success. Does anyone have a clue for me?
Bon, je suis complètement à court d'idées, j'ai besoin d' #aide sur du #reseau sur ce serveur... Si vous avez une idée ou si vous pouvez partager, j'en peux plus là
Le serveur qui fait tourner cette instance est sur un #proxmox. Jusqu'ici, tout allait bien.
Hier, suite à un plantage, j'ai du reboot le serveur (VPS chez Ionos). Après redémarrage, impossible d'accéder à quoi que ce soit : Interface Proxmox, services dans les conteneurs, rien.
La configuration était la suivante :
Interface externe (ens6) et 2 bridges :
vmbr0, en bridge-port sur ens6 (avec donc son ip publique), utilisé pour l'administration
vmbr1, avec une ip dans un réseau en 192.168.2.0/24 qui sert les conteneurs (reverse proxy pour un et docker pour l'autre)
J'ai dans mon fichier d'interfaces pour vmbr1 ceci :
Après debug, j'ai vu que le trafic passait à nouveau lorsque je foutais en down VMBR0.
J'ai donc, dans l'urgence, changé mes règles pour retirer vmbr0 et le changer par ens6, qui est le nom d'interface "physique".
J'ai pu constater que tout était revenu : accès à l'interface de proxmox, accès aux conteneurs... tout sauf, un point important : impossible depuis le serveur d'utiliser sa propre ip publique.
Par exemple, impossible pour l'instance d'envoyer un mail (le conteneur de mailing est situé derrière la même ip), impossible même depuis le shell de proxmox... ou encore impossible de renouveler les certificats sur le conteneur qui fait reverse.