Search results

This was it for my case where I had to nuke and purge the ceph cluster and cleanup the disks.

Necro-posting really isn't my thing, but just to confirm for other users that may face this warning during PVE installation. Can confirm that pressing the screenshot button resulted in the popup with the warning. Installing PVE via ThinkPad and accidentally pressed the key. I'm glad it's not an...

Similar situation here; 2-node cluster; VMs are just randomly getting stuck; I have updated, but haven't rebooted.

Thanks! Switching to "LCAP" option worked like a charm.

Hi, I'm having some issues with interface bonding. I have four interfaces on my server (running Proxmox VE 6.3-3). The network config summary is as follows; - vm1 -> vmbr0 - vm2 -> vmbr0 - vm3 -> vmbr0 - vm4 -> vmbr0 - vm5 -> vmbr0 - vmbr0 -> bond0 - bond0 -> enp4s0f0 enp4s0f1 enp* are physical...

Makes sense - I appreciate the time you dedicated to helping me out. With the help of the command mentioned above I was able to get the name of the package that includes mentioned file, cloned the public repo and verified that the function was indeed not from the source. Thank you again and have...

Yes, ofc course. My bad.

Awh, a simple sed command. Nope, I just tested it by adding a comment and reinstalling - the file was not replaced with the new one. Are you sure that the pve-manager package includes those web assets? And no, I do not automatically patch it. I see that as too unstable since the script doesn't...

The "this node does not have the subscription active"-thing? No, I "disabled" it. Nope. AHA, now I'm sort of connecting the dots. Does the function/class/whatever used for spawning that popup have an option for a callback function which is called when the "OK" button is clicked? If so, that's...

Using Firefox, the popup window does not appear, no errors/warnings in the debug console, same thing with all extensions disabled. I've also tried Edge - same thing.

Yes it is; { "success": 1, "data": { "url": "https://www.proxmox.com/proxmox-ve/pricing", "message": "There is no subscription key", "status": "NotFound", "serverid": "REMOVED" } } And yeah, I haven't mentioned yet, I don't have the subscription...

Okay, fair. I provided wrong information, the button that doesn't do anything isn't the upgrade button, but the refresh button. I opened a new thread here, so we don't trash this announcement thread.

Anrighty, so I currently have the following pve packages installed on one of my nodes in the cluster. I also have a few other "non-default" packages installed, such as net-tools, nmap, screen, bmon and htop. Both nodes in the cluster are affected by this, so it's (most likely) not caused by...

Yeah well, I upgraded already and I didn't notice any issues. As said above, the ISO storage is now shown and works without any issues. I really like the fact that you implemented this "storage-type-splitting-in-ui" feature. Alsothoer thing I'm experiencing, the "update" button in node updates...

Sorry for the late reply, haven't checked the forums in a while... The ISO storage is now visible, I haven't changed anything, was probably the cache as you mentioned above.

I noticed a slight issue with this "split storage by type" feature that you added. I can't access the ISOs anymore..

I understand that necro-posting is very discouraged, but I think that resource-limits would really benefit PVE users. Are there any plans for adding this feature any time soon? Or it just isn't in PVE's "feature-scope" ? I'd like to apologize. After reading the 6.2 release thread I saw that...

If you managed to solve your issue, you should really describe it really fast - so when some other PVE user comes here searching for a solution they will be able to just read it ;)

@moxmox - read the followup if you haven't fixed it yet @spirit - thank you for the contribution :) // marking as solved

Update; executing iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1 on the host machine (root @ PVE host) "fixes" the issue. Source: https://forum.proxmox.com/threads/firewall-stops-vm-ct-communication-also-have-to-reboot-to-fix.59811/#post-275871 I do not fully understand the issue and I...