Search results

That is strange as it is said to be fixed. Can you post more details, what exactly you did so that the staff can reproduce the issue? Maybe you can post your results in the linked Bugzilla report I created, then there is a chance that it can be reinvestigated! As I am still interested in...

Yes, the bug was filled at the Proxmox Bugtracker here: https://bugzilla.proxmox.com/show_bug.cgi?id=2243 It is already patched since pve-kernel-5.0.21-2-pve Unfortunately, as it took some time until it was patched and I had to find a workaround, I was not able to test the patch yet. More...

I can confirm this, was also using Open vSwitch by the way and setting this kernel option, update initramfs, reboot, the server is running for four days already without any hang up! Works like charm, but why :rolleyes::)

Thank you for your quick reply, the Problem with the template is that I have different mounts of different underlying storages in addition to the configuration, the rootfs disk for example lies on a ceph SSD storage, additional mount points on a local LVM disk. This has practical performance...

Dear Community, When I provision a LXC container in Proxmox, it is quite difficult to reset it to an initial state. I want to override the rootfs with a clean image from the template and reinitialize the basic setup Proxmox does (like install SSH keys, configure network). The reason for this...

I have the same problem. One VM keeps freezing the entire system. It seems I can log in via noVNC, but when I shutdown, it stops before killing the process. Stopping the process on Proxmox does not work either. This is only on my home server: My CPU is an Intel i7-7700T on a GIGABYTE...

The problem you describe is a bug / missing feature in the kernel. It has been discussed here: https://github.com/lxc/lxd/issues/5193 There was a patch provided towards the kernel 5.3, as you can see here: https://github.com/lxc/lxd/issues/5193#issuecomment-502857830 I hope Proxmox is able to...

I am using a LetsEncrypt Certificate in my LDAP and because I validate user accounts against that LDAP, I only permit TLS or SSL binding, so connecting without encryption is not an option here, except local via ldapi:/// but these are two different machines. What also is strange is that it is...

I filled bug https://bugzilla.proxmox.com/show_bug.cgi?id=1799 Thank you!

Sorry to grab this old thread but the limit in the GUI is still there, can it please be removed? Thank you!

Dear Proxmox Support, when connecting to an LDAPS (no STARTTLS but direct TLS connection), I get the following error: update LDAP profile failed: Unexpected EOF at /usr/share/perl5/PMG/LDAPCache.pm line 368. (500) When I don't enter the port 636, it says (obviously): update LDAP profile...