Search results

Firewall rules at cluster level are inherited by the nodes, but not by VMs - for VMs rules have to set individually. Also necessary to have "firewall" option for each interface (which is set by default).

tap devices are assigned to the bridge as configured in the VM settings in the moment when the respective VM starts. You can manipulate the assignments by running the linux bridge commands but it is not the approach of Proxmox, the supported way is to use the respective `qm set` command, for...

If not checked already whether it works without active firewall do it since also other wrong network configuration can be the cause. Then have a look at generated iptables in the host by running iptables-save in order to see if the rules had been generated as expected.

AFAIU you want to have the virtual disks hosted by 3 different physical disks. In this case you have to configure 3 different storages - expandig a LVM group across 3 disks is not a solution for this. For considering the situation comprehensively more information is necessary, running a...

It's caused by missing access rights in the mounted filesystem, the following resolves the problem (at your own risk, running from an SD and/or changing /var/log is not recommended indeed): chmod 777 /var/log/pveproxy chmod 777 /var/log/pveproxy/*

In V7.3 attaching an USB device is improved and it's not necessary any more to specify USB version explicitly. On the other hand due to compatibility the USB3 check box still exits. You are right, a check box which cannot be used is useless - thank you for the hint, we will think how to improve...

The difference is caused by ifupdown vs. ifupdown2: Debian 11 default is ifupdown which needs "bridge_hw" as keyword where Proxmox uses per default ifupdown2 which needs "hwaddress" as keyword. You can change this also in Proxmox by apt install ifupdown which removes implicitly ifupdown2...

Run simply apt install ifupdown2 at your "old" (probably PVE6) version.

Just about USB in general (the particularly mentioned devices I don't know): Vendor/Device ID may change when activating certain functions, therefore the safer and more stable way is to specify an USB device by Port. Note that also in this case you may have different port addresses at the same...

Probably your video does not support the geaphic mode of installation media. How to workaround: - Put the planned system disk into a different machine, install Proxmox there and put the disk back (network configuration has probably to be adapted afterwards) - since throughout the versions some...

Go in WEB GUI to Datacenter -> <node> -> <vm-id> -> Hardware -> Add -> USB Device and select in the popping up form the requested device (by Vendor/Device ID or Port; recommended to use Port since Vender/Device may not be unique).

As soon as a NIC is defined as bridge port (in the current case enp2s0@vmbr0) it must not have configured an IP any more. Moreover, since you have just one network ip_forward is not necessary, VMs are contacted directly by layer 2 (i.e. via MAC address) from the router. Port forwarding to VMs...

Sollte ohne weitere Maßnahmen seitens Proxmox Host funktionieren, daher vermute ich, dass irgend eine Windows Eistellung nicht passt. Würde folgendes machen: - NIC Zustand in Windows prüfen, möglicherweise nicht aktiv (bzw. ob Link erkannt); wenn nicht dann passt mit dem Netzwerktreiber in...

Data which are occurring during the installation process are proposals based on DHCP responses. You can adapt them according to your needs. Not quite clear what you address here that is not working correctly (giving an example may help) - anyway, after installation you can adapt the setting...

Server ID is generated randomly as also ssh keys are in order to have a distinct identification whenever a system is installed.

GRUB maybe not correctly installed (respectively does not find file /boot/grub/grub.cfg). Try the following: - Boot with a Linux live Media (perferrably Debian or Ubuntu) - investigate the Proxmox boot disk - check if /boot/grub/grub.cfg is ok (probably yes; if no you should better reinstall...

Since the Device # is created "randomly" you have to adapt the .conf file before each container start by grep-ing the current device ID from `lsusb` output.

No - reissue the key(s) following https://shop.proxmox.com/index.php?rp=/knowledgebase/6/Server-change---How-can-I-move-my-current-subscription-key-to-the-new-server.html

Works for more containers simultaneously too.

https://forum.proxmox.com/threads/proxmox-metric-server-influxdb-grafana.116276/