XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • P

      backup mail report says INTERRUPTED but it's not ?

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      2
      5
      0 Votes
      2 Posts
      20 Views
      P
      some timeout or race condition between the end of the job and the mail generation ? perhaps putting 10sec delay to send mail ?
    • M

      Site outage. pfSense VM offline after pool master reboot

      Watching Ignoring Scheduled Pinned Locked Moved Management
      8
      2
      0 Votes
      8 Posts
      276 Views
      itservicesI
      Hi @McHenry . You should obfuscate the IP address in your first screenshot. Also check your profile and private chat Hope everyone had a joyful Christmas and I wish everyone the best for 2026. Regards, Marc
    • A

      Migrate windows VM from Xenserver 8.4 to XCP-ng 8.3.0 (GPLv2)

      Watching Ignoring Scheduled Pinned Locked Moved Migrate to XCP-ng
      5
      1
      0 Votes
      5 Posts
      65 Views
      A
      Thanks @olivierlambert , really appreciate quick help. VM migrated successfully.
    • olivierlambertO

      🛰️ XO 6: dedicated thread for all your feedback!

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      77
      5 Votes
      77 Posts
      4k Views
      MathieuM
      Has anyone tried to access XO 6 via a reverse proxy? I'm using nginx proxy manager in a docker container to access my XO instance. Everything is working fine with XO5 (both XOCE and XOA). But when trying to access XO6 through the reverse proxy, it shows only a few info, with a circle loading on the top and nothing on the left bar: [image: 1766747700954-7c0cc74d-19cc-4a9e-858a-f53913c654c6-image-resized.png] If I access XOCE and XOA v6 by their IP address, it's working as expected. Websocket support and cache is activated on the reverse proxy, nothing else fancy on that side. Thanks.