Recent content by mvrhov

@Moayad did I answer you question?

I don't know exactly what are you asking, but Firewall rulers that we were expected to be applied are set on "<Server name>/Firewall", The "Datacenter/Firewall" has only ping and proxmox access rules. All rules are done via security groups. Which are all set under "Datacenter/Firewall/Security...

Hey everybody, We have just figured out that if we add port forwarding rules in /etc/network/interfaces, that the Proxmox firewall rules don't apply to that. Is this on purpose or is this a bug? excerpt from the interfaces file. post-up /bin/echo 1 > /proc/sys/net/ipv4/ip_forward post-up...

But this is not automatic (which should be) so you can easily forget.

Hey, I've just spent 4 days figuring out why there is no transfer of data on hetzener vswitch between multiple proxmox machines... The problem was mtu.. which has to be set on the actual interface and not the bridge. Now the problem remaining is that the Proxmox doesn't set the mtu of the LXC...

6.1 Still clock jumps for me :/ After the reboot command clock is in the future. root@h01:~# date Mon 09 Dec 2019 10:30:33 PM UTC root@h01:~# date Mon 09 Dec 2019 02:22:32 PM UTC

I don't know why, but after the upgrade from beta to stable I have weird time jumps on my server and also the CPU usage and server load graphs don't show anything. their start and end time are both showing 1970-01-01 01:00:00. also If I by any chance manage to login into the UI, then after the...

I'm trying to build a network between different machines connected to Hetzner vswitch but I'd like to have two things. I know how to do this with two network interfaces inside a LXC, but I'd really like to only have one. * network traffic of all LXCs on server X must be NATted out via the...

This did help however I'm finding this to be a regression since this worked just fine with proxmox 4.4 and LXC 2.0 Also this is annoying especially if you connect directly to the proxmox and then each of the hosts individually to do some maintenance.

Hi, I've updated (well created a new one and restored container from backup) one machine to 5.2 from 4.4 and it seems that with new lxc the mc is not working properly. Steps to reproduce: Install ubuntu 16.04 as a container apt-get mc now connect to the host proxmox machine with putty and use...

https://www.sencha.com/forum/showthread.php?336762-Examples-don-t-work-in-Firefox-52-touchscreen&p=1174857&viewfull=1#post1174857 So proxmox can fix this on their side.

This one is happening to us also and only on some machines. I've updated the quemu agent and there is no change. The mos annying thig with that is. that this is going on for an hour.. Can proxmox catch this and cancel the backup of that particular VM and then retires at the end, or it tries it...

This is the same problem I reported after the 4.2 was announced (in anouncment thread). However I'm using Windows. P.S. The only message in console is "unreachable code after return statement[Learn More]ext-all.js:22:344134"