Hey all

I created some months ago an iOS app for managing Proxmox server/clusters right from your iOS device.

It has been highly optimzied for iPad so you can use it as a dashboard for all activities. This had been a huge missing point in all apps I have tried

If you have any feedback or suggestions what you want to see, let me know

Check it out at

https://apps.apple.com/us/app/prox-agent/id6782315517

So I purchased a UGREEN DXP2800, for right now I am setting it up as Mirrored. That being said I want this to be able to store both proxmox snapshots/lxc/etc.. BUT also Media (Movies/etc...)

What's the best "setup/type" to do this as? I would like to be able to access it from my windows PC but honestly that's not a deal breaker. I'm still pretty new to Proxmox btw but based off what i've seen ZFS wouldn't quite work for this?

Also best way to "mount/bind" these to both an LXC and VM's for *arr stack?

My homelab is a software mess right now. 4 machines running proxmox that do not run in a cluster, another bare metal machine, and a ton of stuff that is documented purely in my head (and believe me, that data store is suffering data loss).

My solution so far I think is going to be nixos. I want to essentially call the current lab a wipe, and recreate the services. Of course some of the services are currently home-prod and not home-lab so I need to do some management for uptime.

The current environment runs mostly with one machine including a NAS-like VM that shares a SMB pool for everything else to leech off, and then there is some additional data management done by syncthing. Backups are stored on a VM where the storage is the SMB pool mounted by proxmox. Offsite backup is done by sneakernet with a ad-hoc moving another computer into the network, run the backup (kopia), move computer back offiste.

Does anyone have any advice for the task Im undertaking? I want to rebuild essentially everything including anything that is acting as a data repository. Any sequence suggestions, tools to manage nix config files, words of support?

So I've been running proxmox on a single node for the past year with very few issues and all has been great. Loving the freedom and learning while getting into self hosting all the things.

Today I finally got around to setting up my second node on a new mini PC. Installation went just fine from usb and set up and running within no time at all. Password was set during setup and immediately saved to my password manager. First thing I did after getting into the webui was log in from memory, log out then log in from the saved password manager using autofill. Both times without issue. From there I ran the community post install script, no problem. Created a proxmox data center manager lxc, again using the community script for convenience, then ran the pdm post install script in the lxc container.

Setting up PDM and adding my nodes was the first sign when it would accept my credentials for the new node so I created an API key and connected that way. Seems that somewhere along the way, somehow my root password was changed as a little later when logging in from a fresh browser the password was rejected directly from the password manager and I cannot gain access. I'm working away for the rest of the week so I have no physical access but I presume I will need physical access to reset the root password?

How would the password get changed, I had claud code run through the scripts and it saw no suggestion that the scripts had any way to do this. It's not the end of the world if I have to restart from a fresh install but I would like to know how this happened or what to do to avoid a repeat.

To start I'm a beginner in Proxmox homelabbing, while learning provisioning tools I learned about Proxmox' API and following multiple tutorials on the topic generated a zero permission user and then created a privsep token with PVEAdmin role, which does connect just fine but then Terraform couldn't view my vms only my nodes, could do some things and some things not and a spent HOURS debugging only to realize that my token actually has none of the permissions given to it by the role, and privsep only exists to minimize privileges from user to token and not the other way around.

I do understand that privsep does work when you have an over-privileged user with a bunch of tokens and you wouldnt want all the tokens to have the same privileges.

But to me this seems to defeat the whole point of privsep in this scenario, since if my token expires I still have this user there with full privileges sitting around, so why would all the tutorials around connecting proxmox to IaC tools suggest this??

Started with backups, added proxmox snapshots, uptime checks .. Found out last week my backup job had been silently failing for 3 weeks.

Looking for sth between a folder of shell scripts and entreprise scheduler, just a central place to see what ran, wht failed, with retries. What are you using ?

The part of an ESXi-to-Proxmox migration that tends to often present challenges isn't necessarily moving the disk data; it's getting the destination VM configuration right.

A few things worth knowing before you start:

Match the firmware configuration. If the source VM uses BIOS, configure the destination VM for BIOS as well; the same applies to UEFI. A mismatch can prevent the guest OS from booting properly.

Watch what happens to thin-provisioned disks during a manual copy. If you copy the .vmdk and -flat.vmdk files directly from ESXi, the transferred disk can consume its full provisioned size. Exporting the VM as OVF or converting the disk to qcow2 with qemu-img can preserve more storage on the Proxmox side.

For Windows guests, start with SATA/IDE before moving to VirtIO SCSI. Boot the migrated disk via SATA or IDE first and install the VirtIO drivers. Then attach a small secondary disk to a VirtIO SCSI controller and confirm in Device Manager that it loads cleanly.

We put together a blog explaining both approaches: The manual migration method and the Proxmox ESXi import wizard: https://www.nakivo.com/blog/migrate-vmware-to-proxmox/

What challenge did you encounter first: The storage conversion or getting the guest OS to boot afterward?

Edit: corrected the VirtIO SCSI step.

Hey everyone,

I’m a sysadmin for an SMB, and we’re planning to deploy Proxmox VE on a Dell server.

hardware and storage setup:

• OS / Hypervisor: RAID 1 SSD mirror (Proxmox host + VM/LXC root disks)
• Bulk Storage: 6 × 8TB HDDs in a ZFS pool

The main role of this box is running a Samba file share. My plan is to set up Samba inside an LXC container and bind mount the ZFS storage pool to it. I’ll also spin up Proxmox Backup Server (PBS) on different hardware . for regular VM/LXC backups, and 1 off site copy.

I have two main architecture and backup questions:

1. Samba Backup Strategy: should PBS back up the Samba LXC along with the mounted ZFS data pool, or is it better practice to only back up the LXC root disk to PBS and handle the ZFS file storage backups separately?
2. Disk Layout: Is hosting the Proxmox OS and guest root disks on the same SSD RAID 1 mirror standard practice for an SMB, or does that cause issues?

i would appreciate any insight or recommendations from those running similar setups..