Search results

I sucessfully set up acme certificate on our proxmox node but certificate renew fails. Output of pvenode acme cert renew: Loading ACME account details Placing ACME order Order URL: https://acme-v02.api.letsencrypt.org/acme/order/1446374306/265127774607 Getting authorization details from...

I was ale to "hack" it to work. It seems that ( at lest in our case) mount works but what fails is detection if storage is online. I was able to bypass this by editing file /usr/share/perl5/PVE/Storage/NFSPlugin.pm and replacing: my $cmd = ['/sbin/showmount', '--no-headers', '--exports'...

Was you able to find way to access NFS shares hidden behind NAT? We have NFS accessible drive used to off-site backups, but it is in building where local netowrk is behind NAT and we cannot change that. We hacked it by solution psoted above but it is really ugly hack to use.

I was ale to "hack" it to work. It seems that ( at lest in our case) mount works but what fails is detection if storage is online. I was able to bypass this by editing file /usr/share/perl5/PVE/Storage/NFSPlugin.pm and replacing: my $cmd = ['/sbin/showmount', '--no-headers', '--exports'...

I was ale to "hack" it to work. It seems that ( at lest in our case) mount works but what fails is detection if storage is online. I was able to bypass this by editing file /usr/share/perl5/PVE/Storage/NFSPlugin.pm and replacing: my $cmd = ['/sbin/showmount', '--no-headers', '--exports'...

Same issue here. Anybody found a solution how to get NFS with NAT working?

Same problem here on latest PVE 6.3-3

Found out how to do it. Either to /etc/pve/VMID.conf or /etc/lxc/defult.conf add: lxc.apparmor.raw: #include <pathto/customrules> (# is intentional!) Then create custom AppArmor rules in /etc/apparmor.d/pathto/customrules

How is apparmor profile "generated" created? How can we add additional rules to this profile? Or is there another way how to create profile with everything default generated profeile has but with added rules? We need to deny some operations inside LXC containers.

Update. After some experiments I found out some additional info: - there is one log message which may realte pvedaemon[19116]: VM 5001 qmp command failed - interrupted by signal - backup starts to create content on target NFS backup storage (.tmp and .vma.dat files) But these files are no...

We just recently ugraded from 4.2 to 4.4. After upgrade one backup task for quite big VM timeout. Before upgrade everyting works fine. Backup took about 2-3 hours but it was ok. But now backup starts, looks fine for a moment (usually for 5-15% of backup) and then just freeze. No more progress...

I just updated to Proxmox 4.2 and after reboot network is unreachable. I can fix that manually by login via KVM console and executing: brctl addbr vmbr0 eth3 ifup vmbr0 ifup vmbr0:1 ifup vmbr0:2 ifup vmbr0:3 ifup vmbr0:4 My /etc/network/interfaces: auto lo iface lo inet loopback auto eth3...