Latest activity
-
Mmoored99 posted the thread Secure Boot – Microsoft UEFI CA 2023 Certificate - Promox host server in Proxmox VE: Installation and configuration.I am running Proxmox 9.1, I have tested for secure boot on the physical server and it appears to be disabled. mokutil --sb-state SecureBoot disabled My servers are Dell R650 and should support the 2023 certificate. All hosting servers are setup...
-
Ppulipulichen replied to the thread [SOLVED] What are the best practices for using Windows as a Q-Device arbiter in a two-node PVE cluster?.You’ve made a very valid point regarding security. The potential risk of the arbiter being a weak link that could lead to unauthorized control over the PVE cluster is a serious concern that shouldn't be overlooked. Using a PVE instance as a...
-
Ppulipulichen reacted to Johannes S's post in the thread [SOLVED] What are the best practices for using Windows as a Q-Device arbiter in a two-node PVE cluster? with
Like.
Another thing to consider: As soon as you add the qdevice the cluster members can login as root on the qdevice via ssh without additional authentification. So you really shouldn't use the qdevice VM for anything else. This is especially important... -
Ppulipulichen reacted to bbgeek17's post in the thread Backup with Veeam failing (Disk Size=null) with Like.
It is possible that OP did not permission the user/token properly. A quick way to check is to run: curl -k \ -H "Authorization: PVEAPIToken=<USER>@<REALM>!<TOKENID>=<SECRET>" \...
-
Ppulipulichen posted the thread Why does PVE 8.4.16 LXC Console show "Connected" but remain a black screen? in Proxmox VE: Installation and configuration.Hi everyone, I'm encountering a strange LXC issue on Proxmox VE 8.4.16. I have several containers running, and the WebUI Console used to work perfectly. However, one day, the console for CT 109 suddenly went pitch black. It shows "Connected" at...
-
-
Ppulipulichen replied to the thread New "storage" type server for nextcloud.If it were my setup, I’d keep things simple and split the roles clearly. I would install Proxmox on SSDs first. If the server has a proper hardware RAID controller with protected write cache, running RAID1 for the OS is perfectly fine. If not, I...
-
PThe pvesm command is in /usr/sbin, which is not on the default path for a cron job: * * * * * /usr/sbin/pvesm apiinfo
-
Ppulipulichen replied to the thread Missing feature: Show free internal diskspace of VM.Hi Dietmar, I wanted to contribute a couple of points regarding the visibility of internal disk usage. First, it's worth noting that Proxmox already implements this feature for LXC Containers (CT). As shown in the summary page for a container...
-
-
Ppulipulichen replied to the thread Proxmox host/node failure behavior questions.Hi Henry, I think the main point of confusion here is that `pvecm nodes` does not necessarily show every configured cluster node. It only shows the currently active membership, so an offline/dead node not appearing there does not mean it was...
-
-
Ppulipulichen posted the thread How to limit concurrent backup jobs across multiple nodes to prevent PBS overload? in Proxmox VE: Installation and configuration.Hello everyone, I'm running into a serious bottleneck with my backup strategy. I have a 10-node Proxmox cluster, and all VMs are backed up to a single Proxmox Backup Server. The issue is: I created a cluster-wide backup job selecting VMs by...
-
-
ZZivalita posted the thread Can't login to admin GUI proxmox in Mail Gateway: Installation and configuration.Hi, We had issue cannot login to the admin GUI login proxmox mail gateway, the error that showing only this : "Login failed. Please try again" I've restarted pmgproxy but not affected, and issue still occured, can anyone help me to solve this...
-
Hhpahnke replied to the thread pvescheduler memory leak on PVE 9.1.6.Update: Please ignore my idiocracy, didn't fully understand linux memory caching system.
-
Hhpahnke replied to the thread pvescheduler memory leak on PVE 9.1.6.Update: A colleague running PVE 9.0.3 reproduced the same issue. After backing up a single small LXC, pvescheduler went from 117MB to 440MB (peak 1.7GB) and did not release memory after completion. This confirms the issue spans multiple versions...
-
bbgeek17 replied to the thread <span>nodename</span> showing up in front of everything.https://www.reddit.com/r/Proxmox/s/KrmvrSdtmR Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox -
Sste-bm replied to the thread Regression in 6.17: ASMedia ASM1164 SATA controller forced to max_performance, preventing disk spin-down.Hi, I just came across the same issue with kernel 6.17 where disks consume more power in idle. With 6.14 I don't have this problem and disk can be set to med_power_with_dipm. 6.17 for f in...
-
Bbitr0t replied to the thread Severe system freeze with NFS on Proxmox 9 running kernel 6.14.8-2-pve when mounting NFS shares.Hello everyone, I am also seeing intermittent NFS deadlocks that force me to reboot the entire server. This is my first proxmox deployment but I'm not new to hypervisors. I've tried to add as much detail as possible about my setup below and in...
-
-
Hhpahnke posted the thread pvescheduler memory leak on PVE 9.1.6 in Proxmox VE: Installation and configuration.Hi all, I've noticed a significant memory leak in pvescheduler on my Proxmox VE 9.1.6 installation. Here are the details: Environment: proxmox-ve: 9.1.0 pve-manager: 9.1.6 (running version: 9.1.6/71482d1833ded40a) proxmox-kernel...
-
Ddrwtsn32 reacted to Unsubtle9244's post in the thread Can't backup 1 VM to Proxmox Backup Server with Like.
Hi, I also had a similar problem and did not find the solution at first. For testing I disabled fs-freeze flag (uncheck "Freeze/thaw guest filesystems on backup for consistency" in QEMU Guest agent section of VM options). Backup went well...
-
Ddrwtsn32 replied to the thread Can't backup 1 VM to Proxmox Backup Server.THANK YOU for saving me a few hours of troubleshooting!
-
Ggunterwa replied to the thread [SOLVED] PVE 9.0.3 suffered from DNS Drop after a upgrade....The line 118 is the root cause I think, I cannot remove the blocker so far... root@PVE01:/home/test# iptables -L PVEFW-FORWARD -n -v | grep "DROP.*udp.*53" root@PVE01:/home/test# iptables -L PVEFW-INPUT -n -v | grep "DROP.*udp.*53"...
