The default Proxmox installation includes enterprise repositories. These repositories are paid, and you need a subscription token to access them. Without a token, you'll see errors during updates. These errors are harmless but annoying! :) First image (1) To eliminate these update errors, you need to disable or remove those enterprise repositories. Run these commands:mv /etc/apt/sources.list.d/ceph.sources /root/ceph.sourcesmv /etc/apt/sources.list.d/pve-enterprise /root/sources.list.d/pve-enterprise These commands safely move the enterprise repo files out of the active sources directory. Second image (2) No more error message :)

My name is Ogundele Alimat. I'm excited to be in the community, I’m a professional resume writer, and I help job seekers create ATS-compliant resumes and revamp their existing CVs. If you need help improving your resume or positioning yourself better for job opportunities, feel free to reach out here or send your resume to: [email protected]

Hey everyone! 👋 I just open-sourced a new project: job-forge — an LLM-powered CV & job-matching assistant that runs entirely in your browser. ✅ Paste a job offer → get a tailored, ATS-optimized resume in seconds ✅ Matches job requirements against your skill profile automatically ✅ Supports Anthropic Claude, Gemini, Ollama (local), or any OpenAI-compatible proxy ✅ 100% private — all data stays in your browser, nothing stored on any server ✅ Built with TypeScript + React + Vite Whether you're actively job hunting or just want to stay sharp, this tool can save you hours of CV tweaking. Would love your feedback, stars, or contributions! 🔗 https://github.com/codemonkey-df/job-forge Let me know what you think! 🚀

Hello engineers, I recently configured my Proxmox instance with ZFS RAID1 (I need to test the recovery process :)). I then added three additional SSD disks and partitioned them with this command: mkfs.ext4 -L SSD-256GB /dev/sdX - -L: label flag - SSD-256GB: label (adjust for each disk, e.g., SSD-1TB, SSD-128GB) After that, I mounted them via /etc/fstab like this: UUID=4c1cebaf-8142-4b79-a0ea-45c26253ed75 /media/ssd-1-TB ext4 defaults,noatime,nofail 0 2UUID=b012b34c-bb86-408a-bebf-a91d1a1d3a49 /media/ssd-256-GB ext4 defaults,noatime,nofail 0 2UUID=55c39d33-8665-4ba6-9b45-1c513df36296 /media/ssd-128-GB ext4 defaults,noatime,nofail 0 2 Now I have three extra disks for playing around with :) Let me know how you use additional disks in Proxmox.

I recently installed Proxmox on my home lab server. I wanted to start deploying network apps and services on the Proxmox instance, but something didn't feel quite right. I knew everything wasn't fully ready. I wondered what I should do to make it solid. Then it hit me: I needed to ensure all my data and configs were safely backed up and recoverable at any moment. My first thought was RAID1. The challenge? I didn't know how to set it up properly in Proxmox. After some searching and learning, I discovered it's actually super simple :) I just reinstalled Proxmox with the right settings. I pulled two 1TB SSDs out of my laptop (I had four total) and installed them in the home lab server. During installation, on the target harddisk screen I just selected the ZFS RAID1 option, chose the correct disks, and that was it :) Now I've got RAID1 up and running. Of course, I should test the recovery process next, but I'm too excited and want to start playing around right away!