#Proxmox

Chris Hansoneschaton
2025-06-18
2025-06-17

The evenings this week have been a bit of an adventure with the home lab. I'm migrating a number of random services onto a pair of new VM's, one on each of my two Proxmox hosts. They'll become DNS servers (authoritative using nsd and recursive using Unbound), including basic DNS filtering of the bad stuff as well as DNS64/NAT64 services so I can move to more IPv6 mostly systems at home. They'll probably also pickup NTP and any other services that make sense along the way.

My challenge has been to perform as much of the setup as possible using Ansible. I'm still very much a beginner but I seem to be making good progress.

I've been fighting with NSD/Unbound and reverse DNS but after a couple of days that's on hold. Forward resolution is working so I've moved some of the home VLAN's over to add some load. Holy crap they are fast. There's a little delay for a new site not in the cache but it soon picks up. It feels like an order of magnitude faster than my venerable pi 3b+ running pihole with the same DNS filtered list.

I'll crack the reverse DNS stuff at some point and now I've realised the reason I couldn't restart NSD after a change (so I was rebooting the VM) was because I didn't realise the "remote control" options are also needed for local control on the VM, it's a lot faster to get updates on place.

More work tomorrow night on the Ansible playbook with some better tags to manage operations without updating everything.

#HomeLab #OpenBSD #Unbound #nsd #Proxmox #ipv6 #ansible

2025-06-17

Well I just done did a stupid.

I've been using the #proxmox root login since I set it up. I figured that's probably not a good idea, so I created a new user. I thought I set it up as an admin. I even added 2fA.

I checked and saw that the root login was in my password manager, so I deleted the autofill from Firefox.

Weeks go by. I decide to run updates. Turns out my user doesn't have the permissions for that and isn't a member of sudoers. I better fix that.

I try to login as root... and the password is wrong.

Oops. My server is headless so I need to find a small portable monitor so I can edit grub and reset the root password.

#selfhost #homelab

SPdevALK 🐘️ ☑️sjosjo@mas.to
2025-06-16

Nope spoke too soon, thought it was stable but 'QEMU[000000]: error: kvm run failed Bad address' fault showed up again after several VM start/stop cycles over several days, making the VM crash. This will be a hard one to pinpoint as breakage only occurs after a while with no apparent reason. Back to 6.11 #proxmox

Nouveau service public sur #Proxmox VE Blabla Linux 👍
#LibreTranslate 👉 github.com/LibreTranslate/Libr
Interface WEB et API public, plugin navigateur et application mobile 👌
Une vidéo vaut mieux qu'une longue explication 😉
Service LibreTranslate Blabla Linux 👉 ltranslate.blablalinux.be

2025-06-16

@elblogdelazaro

Me construí l mío también ahora ando con dos preocupaciones. Una s la integridad d datos y el uso d memorias ECC n equipos de bajo consumo.

La otra y es mas solucionable las cajas para NAS. Esto último es q tampoco me he puesto demasiado.

Tengo:
Placa Asrock para Intel J5005 mini-ITX
2x8GB de memoria
1xssd 500GB Samsung Sistema
2xhdd 4TB Seagate Datos en Raid1
1xhdd 8TB externo USB3.1 Seagate para copias de seguridad
Caja Thermaltake Core V21

Un saludo
#SelfHosting #proxmox

SPdevALK 🐘️ ☑️sjosjo@mas.to
2025-06-16

Turns out there was a uefi bios setting in the same category as ‘Above 4G decode’ and ‘Resizable BAR’ called ‘Above 4G mmio limit’ that had a default setting of 40-bit.

It needed to be set to 48-bit and now the 6.14 #kernel is not crashing anymore on gpu passthrough.

#proxmox

Recovery mit Proxmox, wenn mal ne Platte ausfällt und man die Backups auf nen anderen Host ziehen will geht echt super.

Migration direkt ging nicht, weil das eine zfs hat und der andere nicht. Das mögen die wohl nicht so.

Was aber geht:

Backup machen, alle Daten zu dem gerade erstellten Backup mit scp oder sowas von einem Host (liegen in /var/lib/vz/dump/ ) auf den anderen ziehen und dann aus dem Backup wiederherstellen und dabei das zfs auswählen. Starten, fertig.

Und ja, das war auch noch von Proxmox VE 7 auf Proxmox VE 8.

#Proxmox
Tymscar :linux:Tymscar@fosstodon.org
2025-06-15

Just shipped a new post on running Docker containers with secrets on NixOS! 🐳

Finally moved my homelab from #Proxmox to pure #Nix using Agenix for secret management. Everything's declarative, everything's public on GitHub, and the tokens stay encrypted.

blog.tymscar.com/posts/nixosdo

2025-06-15

@deadbeefdotmonster I was planning to write down my setup for years now, maybe I’ll finally get around to it 😅 I knew I’m not interested in off the shelf solutions from the get go and when I tried #TrueNAS it was getting in the way too much for my liking. Eventually I went with vanilla #FreeBSD and later on migrated to #Proxmox.

H/W wise I’m rocking scrap parts I had lying around dating back to 2012 or so. The only stuff I invested some cash into was the case (Fractal Node 804)… 1/2

Hobbyblogging.dehobbyblogging
2025-06-15

Mal ehrlich, die Installation von Home Assistant kann eine ziemliche Herausforderung sein, besonders wenn man nicht weiß, wo man ansetzen soll. Ich hab's für mich getestet und empfehle eine virtuelle Maschine auf Proxmox. Schneller und effizienter geht’s nicht! hobbyblogging.de/home-assistan

Linux Solutionslinuxsolutions
2025-06-15

🔑 **5 Recursos-Chave do Proxmox!** 🖥️🚀 Descubra como otimizar sua infraestrutura de TI com o Proxmox! 👉 Leia mais: linuxsolutions.com.br/5-recurs

2025-06-15

We've been hard at work the past few months!

1. Leaving the Westin datacenter in downtown Seattle and moving on from expensive co-location

2. Moving our gear to Fremont, California

3. Bringing on board a few new Advisory Board members, including @whil who has been an incredible help deploying our #Proxmox infrastructure, and @alexhaydock who has been instrumental in deploying our new #Ansible infra, new recursive #DNS resolution infra, and new #Tor exit relays in California! See: infosec.exchange/@alexhaydock/ with more updates to follow

4. Installing new co-location with some older low-power systems in Amsterdam for our self-hosted #ActivityPub infra @ disobey.net, where we just moved our #Mastodon profile to!

5. Deploying a new #XMTP node @ xmtp.disobey.net, and testing a new #DeltaChat relay!

6. Deploying some new #obfs4 private bridges for use in a country who's conducting heavy internet surveillance and censorship, blocking access to @torproject

and today is our birthday!!! we're 8 years old today ^_^ stay tuned for more updates to come!

Da lazy beardudereallylazybear
2025-06-15

I can't believe I've been running PiHole on the network for 2 years and a month now.

I asked the people at our home if they noticed anything and they said they had some trouble accessing very few websites. I just said they're probably malicious domains but otherwise, they noticed ads are gone.

I told them it's for security and privacy purposes. It's also to prevent them from being scammed. Don't want them getting scammed out of their money..

PiHole
2025-06-15

Links, the browser, even though it so small is not included in the installation ISO of MX Linux

I had to connect an internet gateway to fetch links

It took more bandwidth than I wanted, because I first had to do

sudo apt-get update

This eats MB here, on my metered connection

I'll include a toot with photographs RSN

#Links #browser #text #Bash #Hardware #failure #Gigabyte #enshittification #programming #remote #servers #Proxmox #OpenSource

2025-06-15

I'm first posting this before I do the actual test

I want to see if links comes pre installed on the Live MX Linux ENV:

I'm using the standard variant of MX Linux

I shall update the post with the results

#Links #browser #text #Bash #Hardware #failure #Gigabyte #enshittification #programming #remote #servers #Proxmox #OpenSource

2025-06-15

Went ahead and upgraded the Proxmox cluster from kernel version `6.8` to `6.14`. Seemed like a good idea, didn't have any issues with VM migrations so that was nice.

#proxmox #homelab

2025-06-15

@Dendrobatus_Azureus

I have to emphasize the following

  • I cannot work on the old notebook
  • I can only access my data.
  • I can't edit My Master Tapes so I can't do audio
  • I cannot run a gfx browser on the machine.
  • Only If the links browser is in the Live ENV: shall I be able to do text browsing, without JavaScript that is not suitable for the work that I have to do {NSFW}
  • I'm still working actively on a fix with a fallback

A good Plan of Action Plan Van Aanpak is

  • getting a AMD miniPC with a large fan
  • getting a Raspberry Pi with 8 gigs of RAM
  • configuring both machines for work

The Raspberry Pi shall be tight, very tight on memory however it'll still be able to browse with a scaled down version of Firefox.
With this plan van aanpak I shall not have a Single Point of Failure anymore, when it comes down to machine suitable for work.

Oh yes I've read the connection between the notebook computer and NSFW. However there is no joke that I can make, about the fact that I can't work on the remote servers for now.

I miss Proxmox

#Hardware #failure #Gigabyte #enshittification #programming #remote #servers #Proxmox #OpenSource

2025-06-15

Today's #selfhost project was updating #homarr with integrations instead of just apps. Got #Unifi, #Proxmox, #HomeAssistant, and #PiHole done. Couldn't get #Nextcloud to work, though.

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst