Search results

I really like the feature to disable mac address learning at all (bridge-disable-mac-learning 1) which was integrated in PVE 7.2. Currently, the forwarding database is only populated on a start / reboot / reset of vms. Are there any plans to enhance this database population for events like...

After some testing, figured out by myself. :) The default Proxmox ebtables look like the following: ebtables --list Bridge table: filter Bridge chain: INPUT, entries: 0, policy: ACCEPT Bridge chain: FORWARD, entries: 1, policy: ACCEPT -j PVEFW-FORWARD Proxmox does not insert rules directly...

Setup: - PVE Cluster 8.1.0 / Linux 6.5.13-3-pve - Typical Proxmox installation with bridged WAN (Linux Bridge) Test VMs: #1: Debian 12 - Kernel: 6.1.0-18-amd64 - IP & Mac Filter enabled (NDP enabled) - Firewall: Block all Incoming (except ICMP Test server ip) / Allow all outgoing - Network...

Hey there, on a large PVE cluster all vms are flooded with many ARP Requests. (PVE 8.1.10 / Linux 6.5.13-3-pve) tcpdump -ennqti any arp ens18 B ifindex 2 88:30:37 Request who-has <redacted> tell <router-ip>, length 46 ens18 B ifindex 2 88:30:37 Request who-has <redacted> tell <router-ip>...

@m2m be careful exposing the full proxmox webinterface with your reverse proxy configuration. As already mentioned before, you can create a VNC tunnel by API using the /vncproxy endpoint. With the return value of the API request you get: - VNC Ticket - VNC Port With this information you can...

After migrating servers from PVE A to PVE B maybe the original storage from the PBS QEMU Server Config is not existing on the new server. While trying to restore this backup perfectly works from Proxmox GUI PBS Storage view. Example: API POST Request to /api2/json/nodes/nodeXX/qemu Parameters...

Hi, hast du gesehen, dass Argumente in PVE 8 als Array übergeben werden müssen? Poste gerne mal dein Command, welches den Fehler erzeugt.

Thank you very, very much! That was exactly the problem. I already suggested earlier in this national topic to rename "command" to "commands" for the PVE 8 implementation to still support the command string implementation.

Proxmox info: - Version: 8.0.4 (pve-manager/8.0.4/d258a813cfa6b390) VM info: - Windows Server 2022 (Latest) - QEMU GA enabled - Machine: Default (i440fx) 8.0 - VirtIO Drivers: 0.1.240 (Latest) Problem: After running sysprep for further cloning of Windows servers, the QEMU guest agent is unable...

In the current PMG 8.0.7 version postfix internal mails (bounce & notify) will not be DKIM signed - even if the source domain is part of the signing domains. If the bounce sender domain have a strict DKIM / DMARC alignment, some providers are rejecting these important mails. e.G. Incoming mail...

Nach dem Upgrade von Proxmox 7.4 auf 8.0.4 funktionieren alle QEMU Guest Agent Exec API Calls nicht mehr, die im Command Argumente verwenden. Beispiel Request: POST https://X.X.X.X:8006/api2/json/nodes/node25/qemu/15223/agent/exec { "command": "ls -lah" } (Die Übergabe als Array "command"...

Hallo zusammen, ist es möglich, die PMG so zu konfigurieren, dass mehrere Domains innerhalb einer E-Mail signiert werden? Beispiel: Envelope E-Mail-Adresse: bounce@mailings.domain.com Header FROM: news@domain.com Die DKIM Signierung unterstützt aktuell nur eine Domain, unabhängig, ob die...

Eine Alternative bietet hier unter anderem auch Websockify mit einem selbst gehosteten noVNC. Um 8006 nicht extern zu exposen nutzen wir eine VM "console.domain.com", wo wir den Websockify Dienst via 443 (WSS) hosten. Dieser Console Server wiederum hat Zugriff auf Datacenter Level (TCP...

Hallo zusammen, beim Setup eines neuen Proxmox Nodes (7.3) ist folgendes Verhalten aufgefallen. Der Proxmox Installer verwendet beim ZFS Pool erstellen idealerweise bereits die NVMe NGUID anstelle der Labels. Anschließend werden nach der Installation zusätzliche Spare Devices ebenfalls via...

Awesome! Thank you very much

Same problem here with GUI. Loading backups by REST-API works as expected. (Fetching 5.000 Backups in less then 5 minutes) Loading 14 backups in Proxmox GUI results in HTTP 500 after 8 seconds PVE: 7.2.7 PBS: 2.2-5

Hi zusammen, einmal kurz eine Verständnisfrage. Vorab als Basisinfo: 1 GiB = 1024 Bytes * 1024 * 1024 * 1024 (Binärpräfix [IEC]) 1 GB = 1000 Bytes * 1000 * 1000 * 1000 (SI-Präfix) Proxmox 7.1: Storage: ZFS Linux Debian 11: Hardware SCSI Adapter: 200G Laut Proxmox sind hier 200 GiB gemeint...

Thanks, that was the correct hint! The POST requests contained an empty json body which results in this error. A "parameter validation exception" would make much more sense :) Thank you very much, works now fine after removing the JSON body.

Hey thanks for your fast reply, In tests with the API Tokens it seems the token can't be applied because there is no pre auth like auth by cookie? In tests with the Cookie auth its included

Sometimes I'm getting an error by the Proxmox REST-API for any QEMU related task. pveversion pve-manager/7.1-6/4e61e21c (running kernel: 5.11.22-5-pve) root@node49:~# pvesh create /nodes/node49/qemu/XXXXX/agent/ping ┌────────┬───────┐ │ key │ value │ ╞════════╪═══════╡ │ result │ {} │...