Community Return to multiportal.io
Skip to content
  1. Home
  2. MultiPortal Support

MultiPortal Support

18 Topics 48 Posts

Get help with MultiPortal deployment and operations

Subcategories

  • Fresh installs, version upgrades, and HA deployment

    1 8
    1 Topics
    8 Posts
    P
    Sorry, it took a bit longer to check. I redeployed a MP instance and this time bootstrap worked just fine. But i can assure last time i tried, it gt blocked by cloudflare.

  • VDCs, VMs, templates, placement, and lifecycle management

    7 21
    7 Topics
    21 Posts
    C
    Environment MultiPortal Version: 1.2.1 Proxmox VE Version: 9.2.6 Deployment Type: HA Cluster Description We have only 1 specific CPU Model enabled at datacenter level. While we add new nodes to our cluster, then the new host have enabled 71 CPU Models on the database. On the WebUI there are likely random things enabled / disabled while we flip through the sites. Steps to Reproduce (if applicable) Disable all CPU Models and enable some / one CPU Model(s). Add new nodes to the cluster. Some CPU Models you previously disabled becomes randomly enabled. Expected Behavior New nodes in the cluster get the CPU Models from the existing Nodes. Actual Behavior New nodes become 71 default enabled CPU Models

  • Storage policies and disk configurations

    3 8
    3 Topics
    8 Posts
    D
    Environment MultiPortal Version: 1.2.2 Proxmox VE Version: 9.2.20 Deployment Type: HA Cluster Description Reporting of backup storage usage seems broken - and it’s disabling backup jobs. Steps to Reproduce (if applicable) Run a report on the VDC, shows fairly consistent backup usage:[image: 1790835581701-c988ba38-e899-41d8-a26c-132e5f71707d-image.jpeg] Check VDC Usage - shows WAY more usage: [image: 1790835511988-252fdad7-a167-4903-954e-99978368a1d6-image.jpeg] Actual usage in PBS is even lower than report shows (a little over 1TB) - and only 1/10th of what VDC consumption shows. Expected Behavior Report and VDC dashboard show the same backup storage consumption. More clarity on how this is calculated - and expected variance with PBS physical disk usage. Actual Behavior VDC dashboard show 10+TB usage, report shows 3.xTB usage, PBS show 1.xTB usage Logs/Screenshots [Attach relevant logs or screenshots]

  • Internal & External networks, VLANs, SDN, and IP management

    1 1
    1 Topics
    1 Posts
    M
    Hi, I have noticed that in the latest version of MP you cant use the tenant search field in the add External Network wizard (Accessibility tab). (Unable write anything in the search field) The same goes for when you try to update an External Network. [image: 1787084411077-d199c2e5-2df4-410f-a606-e3fb0aa9144c-image.jpeg] Cheers!

  • RBAC, users, groups, and IdP integration

    3 6
    3 Topics
    6 Posts
    StellS
    Hey @espenw-nordlo Can you raise a ticket with support bundle attached please? For other readers of this thread: did you try recreating the role? Or reapplying the role?

  • REST API, scripting, Terraform, Ansible, and integrations

    3 4
    3 Topics
    4 Posts
    C
    Environment MultiPortal Version: 1.2.1 Proxmox VE Version: 9.2.6 Deployment Type: HA Cluster Description When we create a virtual datacenter via the API, the “reseller” and “tenant” variables in the Proxmox resource pool do not appear to be populated. However, when a datacenter is created via the GUI, the reseller and tenant names do appear there. Datacenter Name (GUI): Reseller_XYZ.Kunde_ABC.vdc.9672ec9c-4199-43b0-b258-f2ce4135673c [image: 1789050383346-c9b07b78-ffda-4468-94d9-79dc8577eca3-image.jpeg] Datacenter Name (API): reseller.tenant.vdc.bbfa10c2-7c52-4d6e-986f-d6c0c156fd80 [image: 1789050397348-670ac32b-19c1-4eed-8c5d-9bf26def9e41-image.jpeg] I also checked the swagger documentation but couldn’t find a way to change this behavior. Expected Behavior The ressource pool on Promox includes the reseller and tenant names also when created via api. Actual Behavior The ressource pool on Proxmox only includes the id of the virtual datacenter, and doesn’t include the showname of the reseller and tenant when created via api.