Search results

Hello, In the document here : https://www.proxmox.com/en/downloads/item/proxmox-mail-gateway-subscription-agreement It is indicated that the subscription unblocks the "Complete feature-set" What are the features that don't work without a subscription ? Thanks

Hello, I have two mail backend servers with Postfix behind the PMG gateways. I would like to be able to distribute mail on these servers with high availability. I initially used "smtp_fallback_relay" to the back-up server in the Postfix PMG configuration, but this causes problems with mail...

Perfect! Thank you. Just if you haven't seen it, but according to my tests, the problem only occurs on 64-bit VMs.

With i686 system on kvm32 and kvm64 it works ! So it seems to be a 64-bit guest problem..

Same as with core2duo or Conroe. I will try with a 32bit infrastructure.

Thank you very much for your support The problem is on Debian 9 Stretch

A test on an Ubuntu VM (Kernel 4.15.0-66-generic) normally works on pve-kernel-5.0.21-4-pve . VM Info: bootdisk: scsi0 cores: 2 ide2: none,media=cdrom memory: 2048 name: Lubuntu net0: virtio=02:48:4C:D3:7A:1A,bridge=vmbr0,firewall=1 numa: 0 ostype: l26 protection: 1 scsi0...

On the VM, the last message I managed to capture at the boot before the reboot: Probing EDD /edd=off to disable)... ok

Nothing.. After a cleaning of dsmeg, just this during the startup and reboot of the VM : [22838.095401] device tap1001i0 entered promiscuous mode [22838.156978] fwbr1001i0: port 1(fwln1001i0) entered blocking state [22838.156982] fwbr1001i0: port 1(fwln1001i0) entered disabled state...

If I reboot the node on the kernel : 5.0.21-3 it works very well.

With pleasure. I have carried out several tests: - Deleting all hardware (net, ide, disk) - Backup and restore VM - Migration to another node Information about a newly created test VM: bootdisk: scsi0 cores: 1 ide2: local:iso/gparted-live-1.0.0-5-amd64.iso,media=cdrom memory: 512 name: test...

Hi, Same problem here since the kernel update : pve-kernel-5.0.21-4-pve The reinstall doesn't do anything better. Chris

Known problem and will be fixed in the new version of the manager. https://forum.proxmox.com/threads/fw-ip-address-problem.57226/#post-265751

Perfect, thank you Aaron. It will be more convenient than intervening in the /pve/firewall/cluster file. :) CG

Hello, I just noticed that adding IPs to the firewall rules is no longer accepted. It is indicated that the format is not good. Is a bug open? Greetings Chris

Hello, Also the same problem. IPs are no longer accepted in IPSet and firewall rules. CG

Hi Dominic, I misspoke. That's what I'm thinking about. --> https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_redundancy Chris

Good evening, I have exactly the same problem, and I haven't found a solution. I think this problem comes from the hosts file. So, what is the point of several Corosync links? Chris

Hello, You can already adapt the PVE explanations for PMG as a first step. https://pve.proxmox.com/wiki/Fail2ban Greetings