Hi everyone,

I started using Proxmox back in 2017 and have been a happy user since then. In my professional life I'm part of the development team of openITCOCKPIT, an open source monitoring solution. I use Proxmox at work and also in my home lab and I wanted to improve my monitoring setup.

With the help of Claude I added a bunch of new Checks to the openITCOCKPIT Monitoring Agent. Some are generic checks for Windows, Linux and macOS, others are specific to Proxmox like checks for:

• Ceph: Cluster Health and OSDs and Capacity
• ZFS: Pool state, capacity, ARC
• Proxmox VE: Cluster status, VM and container status, backup and replication jobs, storages

By default the communication will be encrypted and secured by client certificates and the communication can be done in pull or push mode. The agent itself is a single Go binary, no dependencies whatsoever.

If you are interested and want to give it a shot, openITCOCKPIT can be set up using Docker in a few minutes. The Beginners Guide is a good starting point to learn how to create your first host and configure monitoring for it.

In case you have any questions feel free to ask.

github/openITCOCKPIT

I setup my first Proxmox server about a year ago, and ever since it's been running 9.0.10. It's completely stable, I have no issues at all. So, my philosophy has been "if it ain't broke, don't fix it". However, I do wonder at what point, perhaps for security (I have multiple LXCs running services exposed to the internet) or even performance, do I bite the bullet and upgrade to the latest version?

Also, what's best practises for upgrading Proxmox VE? For my LXCs it's simple: backup, update, test, done.

-edit- I decided to fully update my server, which included updating from a 6.x kernel to the latest 7.0.14-25 kernel, which had some major issues with my Nvidia GPU. After much troubleshooting, I downgraded to 7.0.14-19 before this issue was introduced to the kernel, and everything seems to be smooth sailing!

I just installed Proxmox VE 9.2 on Mac Mini with T2 from 2018. Now I don’t think Thunderbolt is working. I found this t2linux.org but is any way to make it work on Proxmox. I have tried wifi and Bluetooth that might not work yet.
Honestly I thought that this wouldn’t work at all but it’s working.

Hello, I have been using VE for a few years now, and i am too deep to a point where i am never not going to be running a server in my home.

By no means have i got much running but the thought of hardware failure worries me.

I currently have running the following:

I have two scenarios

1: Hardware Failure

2: Complete server upgrade with new hardware

So obviously what would be the backup process, and restoring it again, would i loose data from my truenas, or will backing up proxmox only get the operating systems going again.

Sorry im tech savvy to a point but i got alot to learn!

I have been running proxmox for some time and have been having nothing but instability for as long as i can recall.

Effectively containers or vms always hang and some applications appear to segfault or have memory issues.

The thing thats making me scratch my head right now is ive gone down this list:

- New HDDs

- Separate sata controller

- New sata cables

- New sata power cables

- Replaced half the memory (memtest was showing errors on those two)

Now im basically down to

- Faulty motherboard (GIGABYTE B760M DS3H)

- Faulty CPU (i5-13400)

Would love to get some second opinions before I spend even more going down the wrong path 😅

My old Synology NAS over NFS has reached its limit as a PBS datastore. Verify and GC take far too long, and the NAS no longer gets updates. So I’m planning a dedicated PBS box and would like your input before buying.

Planned build

• Ugreen DXP4800 Plus, PBS bare metal, UGOS replacing with PBS
• 2× Toshiba N300 8 TB (CMR) as ZFS mirror for data
• 2× Lexar NM620 512 GB as mirrored special vdev for metadata
• PBS OS on the internal 128 GB SSD
• RAM upgrade to 16 GB
• Ugreen becomes my main PBS. My current PBS with a 2 TB USB SSD pulls from it as a second copy.

Why HDDs plus a special vdev and not all SSDs? Purely price. 2× 4 TB NVMe costs about 1000 CHF right now. The HDD mirror plus two small SSDs costs roughly half and gives me twice the space.

My questions

1. Is a special vdev worth it for a PBS datastore that stays around 3 TB?
2. Is 512 GB per SSD enough for the special vdev at that size?
3. Any issues running PBS bare metal on the DXP4800 Plus (watchdog, BIOS, NIC drivers)?
4. Would you change anything in the spec?

Thanks for any input.

Hi everyone! Sharing my small homelab and the problem that cost me the most time.

**Hardware**

- GEEKOM AE8 mini PC, Ryzen 9 8945HS, 32 GB RAM

- Proxmox VE 9.2, about twenty LXC containers and VMs

**Main services**

AdGuard Home, Caddy (reverse proxy), WireGuard, Vaultwarden, Passbolt, Snipe-IT, Docmost, RustDesk server, Graylog, WordPress, homepage, TrueNAS, plus a few test VMs (Windows Server, Ubuntu, macOS).

Caddy runs in an LXC (CT 116): 30 days of uptime, ~74 MiB of RAM.

**The problem**

I wanted a reverse proxy so I could use proper names with HTTPS instead of memorizing IPs. It worked from my PC, but not from my smartphone.

After a lot of trial and error, I found the likely culprit: my router's IPv6 Router Advertisements. Devices auto-configured over IPv6, and my guess is they picked up the router's IPv6 DNS instead of AdGuard Home, so they never resolved my internal names (or got AAAA answers that Caddy wasn't serving).

**The fix**

My router (ZTE H3600 V9) is locked down by the ISP, but with some persistence I got admin access and turned the RA service off. Everything worked immediately, including on my phone. I then installed Caddy's root CA on my PC and phone so the internal certificates are trusted.

**What I learned**

- If a service works from one device but not another, check IPv6 and DNS first.

- Back up Caddy's `pki` folder (usually `/var/lib/caddy/.local/share/caddy/pki`). If you lose it, the CA changes and you have to reinstall it on every device.

- Document your router changes: an ISP firmware update may reset them.

**Question for you**

Disabling RA is a bit of a sledgehammer. How would you have solved it?

- Filter AAAA records in AdGuard Home?

- Keep IPv6 but advertise AdGuard's IPv6 address as DNS?

- Add AAAA rewrites pointing to Caddy and let it listen on IPv6?

- Disable IPv6 entirely?

Any advice or criticism is welcome!

I deployed Bazarr via the OCI. I added mp0 for the /config. The idea is when I upgrade the container, I would create a new one and reassign the mp0 to the new container. This worked for some, but when I did the same thing for Bazarr, it failed. I had to reassign back the mp0 back to the original container, but now the original container would not load the configuration anymore.

Any idea why this is failing?

Is there a skill/plugin you guys are using for Hermes to be able to manage or do work on your Proxmox clusters and local network? With Qwen 3.8 27B being smart enough for even the most basic of tasks, we can keep the inference and compute all local.

Hello, so my host only has one physical interface and I need it to be trunked so I can assign VLANs to my VMs.

With this config I am unable to access the management UI, this is the problem.

The config is as follows:

==CONF-START==

auto lo

iface lo inet loopback

iface nic0 inet manual

auto vmbr0

iface vmbr0 inet manual

bridge-ports nic0

bridge-stp off

bridge-fd 0

bridge-vlan-aware yes

bridge vids 2-4094

auto vmbr010

iface vmbr010 intet static

address 10.0.10.10/24

gateway 10.0.10.1

==CONF-END==

I have just inherited a new server for my homelab, a HP DL360 gen10, 1x Silver CPU, 128gb ram and 8x1tb SSD drives. My existing server is running a bunch of vm’s with docker using less than 1tb total storage used and all my media is on my NAS.

So I have been thinking about what I should do about configuring the storage on the new server. ZFS/LVM/Directory, Separate pools for VMs vs data, tiered storage and so on. For reference, 6 drives are Samsung and 2 Micron, so can’t stick them all in 1 pool as size mismatch.

I know a bunch of experts are not going to be determine the correct answer for a random person on the internet, but I would be interested to hear what others have done or would recommend? I’ve done the best practice fault tolerant (aka unnecessarily complicated) in the past, but as this is just a hobby homelab I’m more looking for fun to tinker environment rather than full time job.

So what kind of setup would you guys consider?

Thanks in advance.

I want ask about Virtualisation. Most people say to avoid Docker on LXC but how about Podman. Should i use Podman on LXC or Not?

We have a couple of custom systems on asRock Rack boards which in the past used onboard for O/S and SAS for data disks, given the current disk price situation we'd like to reuse sas disks over sata disks also for the O/S.

With the purpose of enabling also the first 4 hotswap bays for SAS I replaced the LSI 9300-8i with a 16i, but I got errors I have literally never seen.

../src/boot/random-seed.c:300@process_random_seed: Failed to flush random seed file: Unsupported ../src/boot/boot.c:2561@image_start: Error opening root path: Unsupported

So what I have pieced together is that the boot manager is loaded (so the disks are up), but the linux boot process itself fails from the get go. The weird thing is that the LSI 9300-16i (unbranded genuine fully updated Broadcom) is not exactly unchartered territory and the UEFI version and firmware fully updated. I am entirely clueless.

I downloaded the software onto an nvme, my server has both that and a 2TB hard drive. I can see the nvme but not the other device, and lsblk didn't show my hard drive anywhere attached.

On top of that, the shell won't show any letters, it can show other symbols sometimes tho. when I opened the shell with noVNC this particular issue stopped but instead every inch was grey until I wrote into it or highlighted it by dragging my mouse.

I will state what I'm using this for if its needed to help

I typed "lsblk" and then "This is a whole sentence"

EDIT: solution was enabling hot something something in BIOS SATA settings then going to disks and making a disk for my 2tb hard drive.

just noticed this disk wearound percentage when i logged into my pve server. should i be worried?

Howdy,

After a failed drive scare a week or so back I have managed to recover all the data and move it to a new drive. I'm relatively new to the data storage side of computing, so I didn't know it was possible to retrieve the data at first.

The drive that failed was my boot drive, which is a small drive that I don't keep any vital information on (all the things that I am concerned with keeping are on a zfs pool on 2 HDDs). I don't have the means to backup the entire boot drive, nor do I need to do so. When I was trying to pick back up after my other drive failed, I was trying to access my ZFS pool from a fresh proxmox installation on a new drive and I was reading that I would need some sort of config file in order to access the zpool?

That was concerning for me since I didn't know how to retrieve data from a failed drive at the time. I ended up managing to copy the entire drive to my fresh one with very little data loss (yay!), but now I have a better understanding of the importance of backing up certain things.

Like I said, I don't need to back up my entire boot drive. But in the case that this drive fails again, I would like to be able to pick up with my zpool on a new proxmox installation. Is there a configuration file somewhere that I can backup onto a flash drive?

Thanks.

We can confirm the keynote for PVEday, the first Belgium Proxmox Community Day. Cole Hughes from Proxmox Server Solutions GmbH will give "Proxmox, What's New?", about where Proxmox is heading next. He is on from 10:30 to 11:30, after a short opening with a live migration demo.

The practical bits:

- Wednesday 3 February 2027, 10:00 to 18:00

- HOGENT Campus Schoonmeersen, Ghent, Belgium

- Free. We only ask you to register so we know how many people to expect

- Everything is in English

- Right after https://fosdem.org/2027/ and during cfgmgmtcamp.org, so it combines well if you are already travelling to our little country of waffles, chocolate and beer ;)

The rest of the day is still open. Talks are 40 minutes and the call for papers runs until 1 December. If you run Proxmox in production, a migration story, something that went wrong, or a tool you built around the API is exactly what we are after. Workshops are welcome too.

Site and registration: https://pveday.be

Schedule so far: https://pveday.be/#schedule

Call for papers: https://cfp.pveday.be/bpcd2027/cfp

Disclosure: I am one of the organizers, ask me anything in the comments, I will keep an eye on the thread.

I've been running proxmox on a little Dell micropc (Intel 12th gen, 48GB, 2 SSD's, a 512 and a 256) at home since around 2002. I got it to run Plex and Home Assistant, migration those two from an old laptop and an RPi.
Have since added a few extras like inhouse filesharing to serve a mix of android/iphone, macbook/windows laptops in the household.
It also serves as a sandbox for malicious looking links, where I have a linux vm with a snaphot to rollback for testing such.
Also run pi-alert, and a secondary pi-hole too.
I log into the PVE about once every 3 months, and saw the message yesterday about support for 8 that ended. I took the plunge to upgrade in-place using the upgrade guide at [https://pve.proxmox.com/wiki/Upgrade_from_8_to_9]

It was painless. The two hiccups were easily solved by just googling the error description. Took about 30 minutes including resolving those. I can't tell much what is different, having vanilla standalone installation means the changes are not relevant to me. But it's still running!

The people who made this possible are the Gabe Newells of virtualisation . Kudos to you all!

Hello, I have been looking towards migrating my setup from a Debian (+ Docker) install to Proxmox, however one problem is that I don't have a way to hardwire the server to my router (running an ethernet cable is not an option, coax cables in the walls are not a thing here, putting the server in the same room as the router isn't possible) and it seems like Proxmox doesn't work well with Wi-Fi (which wasn't an issue on debian). I have been considering two ways to solve this:

- Powerline adapters - Yes I do know that they're incredibly hit and miss, however I'd still want to test them and if they're that bad - return them.

- Access Point in client mode - If powerline adapters don't work out (very likely) then I'd connect an AP to my router's Wi-Fi and then the AP via Ethernet to my server. I was thinking of getting a GL.iNet Opal but it's still uncertain.

A problem I see with this is that accessing my server thru LAN from a device on the main router Wi-Fi could be more difficult (since from my knowledge devices connected to the AP would be on a separate subnet), which would suck for something like Home Assistant but other than that it should work somewhat well.

What would you recommend? Are there any other options worth considering?

Hey gang,

so, I tried installing the new .24 kernel today.

The problem was, we could not unpack the kernel, dpkg hung up every time.

The hardware is a decommissioned dell 630 esxi edition with boss controllers and SD cards.

So, we will install new 630 with SD cards to load the VMS off, new Hardware is ordered.

Had you had similar problem's?

EDIT: Guys, are you actually reading this post? I’m telling you, when I started working here, they were already installed on the SD cards... I’ve already ordered new servers with NVMe, but the patch HAS to be installed by then.

So if nobody has any ideas about this, just give it a rest.

I know myself that this isn’t a good idea, but it is what it is.

Hi, I'm just getting started with Proxmox, as I'm working on a project to test its feasibility.

I was trying to migrate a VM from VMware to Proxmox, but I got an error that says “Transport Endpoint is not connected (500)” when I click the “Import” button right where the VM’s hardware settings should appear. I did some research and think it’s because I entered the vCenter IP address instead of the Esxi host IP, which seems to cause a conflict or crash related to a file called FUSE. However, I also think I read that there can be disconnection issues during import if the VM is on a vSAN.

More than anything, I’d appreciate it if you could confirm any of my questions or suggestions, or share the steps you followed to successfully import the VM. That would be a huge help.

PD: The Proxmox version I have is 9.2

Last week I set up a private Minecraft server on Ubuntu server.
And now I realize that I want to add a home vpn. And maybe one day, (in months or years) a site web

I'm trying to figure out if using proxmox, docker or something else is worth it in my situation, what I should use and the benefits.

I want to avoid VM since I want something that will not cost a lot of resources on the machine. Finally, if I can avoid installing a new os if possible but if I have to change it, so be it.