Recent content by linushstge

  1. L

    Get VNC port from VM?

    @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...
  2. L

    Restore from PBS by API to specific storage

    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...
  3. L

    QEMU Gast Agent [exec] - Broken Pipe (Proxmox 8.0.4) Array Breaking Change

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

    [SOLVED] Windows Server 2022 - QEMU Guest Agent Exec (Failed to execute child process (No such file or directory)

    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.
  5. L

    [SOLVED] Windows Server 2022 - QEMU Guest Agent Exec (Failed to execute child process (No such file or directory)

    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...
  6. L

    DKIM signing for bounces

    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...
  7. L

    QEMU Gast Agent [exec] - Broken Pipe (Proxmox 8.0.4) Array Breaking Change

    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"...
  8. L

    DKIM doppelte Signierung

    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...
  9. L

    VNC über API: 401 No Ticket

    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...
  10. L

    ZFS Spare Device - Label anstelle der NGUID

    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...
  11. L

    Error listing snapshots - 500 read timeout

    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
  12. L

    Storage Frage

    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...
  13. L

    PVE REST-API - Sometimes error: Not a HASH reference at /usr/share/perl5/PVE/APIServer/AnyEvent.pm

    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.
  14. L

    PVE REST-API - Sometimes error: Not a HASH reference at /usr/share/perl5/PVE/APIServer/AnyEvent.pm

    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

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!