Updated xcp-ng-pv-tools on my one XCP 8.2 server. (We have mostly (citrix)7.1 and (xcp)7.6 because of hardware RAID limitations)
Found the ISO located at /opt/xensource/packages/iso. (verison 8.2.0-9)
Moved this to my local workstation, and then to my ISO-repo file server.
Went to my XCP 7.6 server, and then to the Rocky Linux 8.4 VM i just set up.
Removed the EPEL xe-guest-utilities-latest package. (7.21.0-1)
Mounted the XCP ISO from the ISO-repo and installed the guest tools from that. (7.20.0-9)

Agent detected! and the service seems to run without error.

Updated to Master build, a66ae, xo-server 5.92.0, xo-web 5.96.0.
Consoles seem to work fine again.
thanks all!

@florent
I ran the install upgrade script from @ronivay with the fix_console_proxy_xcp_7x branch. Seems to be working.

Can't create Private Network, on XO 5.83

I got to the Pool page, and select Network tab, and then, Select Manage. Add a network, and then hit the Private button. It makes me select a PIF, but anyone I select, and hit go, gives me an error.

I've seen instructions, and they seem pretty easy, so not sure what im doing wrong here.

Doing so in XCP-Center worked fine.

sdnController.createPrivateNetwork
{
  "poolIds": [
    "8e059584-1d7b-b674-1fe4-ef5cd08d2550"
  ],
  "pifIds": [
    "566e0925-72d9-f3c3-6c06-b05ab7035018"
  ],
  "name": "dfg",
  "description": "dfg",
  "encapsulation": "gre",
  "encrypted": false
}
{
  "message": "no connection found for object 8e059584-1d7b-b674-1fe4-ef5cd08d2550",
  "name": "Error",
  "stack": "Error: no connection found for object 8e059584-1d7b-b674-1fe4-ef5cd08d2550
    at default.getXenServerIdByObject (file:///opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server/src/xo-mixins/xen-servers.mjs:197:13)
    at default.getXapi (file:///opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server/src/xo-mixins/xen-servers.mjs:478:29)
    at default.getXapiObject (file:///opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server/src/xo-mixins/xen-servers.mjs:484:17)
    at Xo.getXapiObject (/opt/xo/xo-builds/xen-orchestra-202111011545/node_modules/lodash/_createBind.js:23:15)
    at map (/opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server-sdn-controller/src/index.js:716:46)
    at Array.map (<anonymous>)
    at SDNController._createPrivateNetwork (/opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server-sdn-controller/src/index.js:716:27)
    at Object.call (/opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server-sdn-controller/src/index.js:363:12)
    at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202111011545/packages/xo-server/src/xo-mixins/api.mjs:304:33)"
} 

pulled and rebuilt and plugins have returned!

I thought I did that.

Oh I see whats happening. My cold moves are freaking out.
The first time, I restarted the toolstack for the server I was working on the # of tasks dropped by 50% or so. as soon as I tried my cold move of a VM again, im up to 50-60 tasks again. Going from Xen 7.1 to XCP 7.6. and a Xeon 2630 V3 to a 2620 V0. Which I know is a bad idea, hence the cold move.

@olivierlambert
control+shift+R on that page and they all come back.
I even tried to kill them from the cli on any given xen server, and they don't seem to go away.
xe task-cancel force=true uuid=

Haven't used my XO in a few weeks, but went in today, and see something like 50-60 tasks all like the below. Is this normal? Haven't noticed before. How can I get rid of?

Looks like it took me to build 37cdbc19e
xo-server 5.101.0
xo-web 5.102.0

and making new VM works.
and to think I just happened to need to make a new one after updating the other day, wasn't really looking for a bug.

went back to my previous build (using the XenOrchestraInstallerUpdater)
xo-server 5.96.0/ xo-web 5.97.2 build c4839 and new VM worked fine.

XCP-ng Center had no problem making new VM, by the way.

Can't create new VM today, after updating to 5.101.0 / 5.102.0 build 281a1
Any thoughts on this? Am I missing something?

thanks.

vm.create
{
  "clone": true,
  "existingDisks": {},
  "installation": {
    "method": "cdrom",
    "repository": "a05463cd-8a9f-40e5-9087-8f1ddda0c750"
  },
  "name_label": "Windows Server 2019 (64-bit)",
  "template": "9788e5a6-c4ec-a4ba-2083-c448722a5974-d986ea98-09fa-4e9a-9ee6-e6c78119496f",
  "VDIs": [
    {
      "bootable": false,
      "device": "0",
      "size": 268435456000,
      "type": "system",
      "SR": "000988d9-5c09-4c63-86a1-8cb904d0642f",
      "name_description": "Created by XO",
      "name_label": "Windows Server 2019 (64-bit)_oleri"
    }
  ],
  "VIFs": [
    {
      "network": "46843b23-dd90-2b78-0f9a-dfaac7847e9c",
      "allowedIpv4Addresses": [],
      "allowedIpv6Addresses": []
    }
  ],
  "coresPerSocket": 2,
  "CPUs": "4",
  "cpusMax": 4,
  "cpuWeight": null,
  "cpuCap": null,
  "name_description": "",
  "memory": 17179869184,
  "bootAfterCreate": true,
  "copyHostBiosStrings": false,
  "secureBoot": false,
  "share": false,
  "coreOs": false,
  "tags": [],
  "hvmBootFirmware": "uefi"
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "instancePath": "/VDIs/0",
        "schemaPath": "#/properties/VDIs/items/additionalProperties",
        "keyword": "additionalProperties",
        "params": {
          "additionalProperty": "bootable"
        },
        "message": "must NOT have additional properties"
      },
      {
        "instancePath": "/VDIs/0",
        "schemaPath": "#/properties/VDIs/items/additionalProperties",
        "keyword": "additionalProperties",
        "params": {
          "additionalProperty": "device"
        },
        "message": "must NOT have additional properties"
      },
      {
        "instancePath": "/VDIs/0",
        "schemaPath": "#/properties/VDIs/items/additionalProperties",
        "keyword": "additionalProperties",
        "params": {
          "additionalProperty": "name_description"
        },
        "message": "must NOT have additional properties"
      },
      {
        "instancePath": "/VDIs/0",
        "schemaPath": "#/properties/VDIs/items/additionalProperties",
        "keyword": "additionalProperties",
        "params": {
          "additionalProperty": "name_label"
        },
        "message": "must NOT have additional properties"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at Module.invalidParameters (/opt/xo/xo-builds/xen-orchestra-202209011436/packages/xo-common/api-errors.js:26:11)
    at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202209011436/packages/xo-server/src/xo-mixins/api.mjs:65:20)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202209011436/packages/xo-server/src/xo-mixins/api.mjs:390:19)"
}

Updated to Master build, a66ae, xo-server 5.92.0, xo-web 5.96.0.
Consoles seem to work fine again.
thanks all!

@florent
I ran the install upgrade script from @ronivay with the fix_console_proxy_xcp_7x branch. Seems to be working.

I don't know if this helps:
most of my VMs are Windows. There are a few Linux, Centos 7+, Rocky, and Ubuntu 18.
the production XO I use, is behind an Apache reverse proxy, using https. The temporary one, is just XO, using http on 8080. Looks like all of these are PVHVM, (so, HVM?) it claims. Both of these XO's are VMs on the same host, and the other hosts are on the same subnet, but some are on a different VLAN. There are also a number that are in a co-location facility, connected via a point to point fiber link, on a different VLAN, but all behind our edge router.
Console working: XCP 8.1, XS 7.1
Console not working: XCP 7.6 - I can't say for sure that these have any updates applied, though.