PDM: Adding fresh installed PVE causes api error

[beckerr]

I'm using PDM 0.9.2 and trying to add a fresh install pve 9.0.17 host (not clustered, not licensed yet).
Its name is `pwe-lwt-1`, if that's relevant,

Right after add the new remote I get:

api error (status = 400: api returned unexpected data - failed to parse api response)

I checked if the apt-token was successfully add on `pwe-lwr-1`. Yes, it was:

root | @pam | pdm-admin | never | auto-generated by PDM host 'pdm' on Tue, 18 Nov 2025 13:51:38 +0100

The problem appears to occur when retrieving cluster resources.
However, “Remote Tasks” can be accessed, as can be seen in this screenshot:


Firefox displays this in the console when the error occurs:

And `pveproxy/access.log` on `pve-lwt-1` logs this:

::ffff:xxx.xxx.xxx.xxx - root@pam!pdm-admin [18/11/2025:14:01:12 +0100] "GET /api2/extjs/cluster/resources HTTP/1.1" 200 1901

When I query the API via curl, I get this:

# curl -k -H 'Authorization: PVEAPIToken=root@pam!test=XXXXXXXXXXXXXXXX' https://localhost:8006/api2/extjs/cluster/resources
{"data":[{"level":"","type":"node","node":"pve-lwt-1","cgroup-mode":2,"id":"node/pve-lwt-1","status":"online"}],"success":1}

Does anyone have any ideas?

 

[sterzy]

Hm I'd need to look into this further, but my current guess would be that PVE added a parameter in certain API endpoints that PDM doesn't respect yet. Can you check the logs of your PVE and PDM hosts to get some more insight into what might be happening here and which requests exactly are failing? Thanks!

 

[beckerr]

Thank you for your prompt reply.
Do you have any suggestions as to which logs I could check, apart from these two?

pdm:/var/log/proxmox-datacenter-manager/access.log

::ffff:aaa.aaa.aaa.aaa - root@pam [18/11/2025:14:01:12 +0100] "GET /api2/extjs/pve/remotes/z-pve-lwt/resources" 200 0 Mozilla/5.
0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0

pve-lwt-1:/var/log/pveproxy/access.log

::ffff:xxx.xxx.xxx.xxx - root@pam!pdm-admin [18/11/2025:14:01:12 +0100] "GET /api2/extjs/cluster/resources HTTP/1.1" 200 1901

 

[DerekG]

This seems to be a general error.
I had PDM working with my cluster until the last update, then I got the same api error.

Strange enough, the issues does not effect the 2x PBS which the PDM is also monitoring.

 

[sterzy]

Do you have any suggestions as to which logs I could check, apart from these two?

These two logs are fine, it would have been interesting to see whether there are any authentication related issues here, but it doesn't look like it. I think at this point logs will not be super helpful as we don't log contents of the requests (for good reason) and tend to return 200 error cases in places where we shouldn't.

However, pveversion --verbose could be helpful when recreating this.

 

[aeisan]

This seems to be a general error.
I had PDM working with my cluster until the last update, then I got the same api error.

Strange enough, the issues does not effect the 2x PBS which the PDM is also monitoring.

I am also getting this API error. I first noticed it in PDM. I finally (just yesterday) joined my two PVE nodes into a cluster and thought maybe that (and some certificate changes) had something to do with the API issues. Seems more general as you have noted.

This morning I was checking in on things remotely from my phone and noticed the same/similar API issues with the mobile web GUI for PVE. Changing to "desktop" mode seems fine (albeit cumbersome to use on mobile).

 

[ns33]

Adding to this; I started having this issue after updating everything using POM. POM was updated Nov 18 and then promptly deployed.

PBS and PDM comms are fine. Looks like it's just between PVE and PDM. Tried readding the PVE instance but the API still occurs

 

[TheGoat]

I'm using PDM 0.9.2 and trying to add a fresh install pve 9.0.17 host (not clustered, not licensed yet).
Its name is `pwe-lwt-1`, if that's relevant,

Right after add the new remote I get:

api error (status = 400: api returned unexpected data - failed to parse api response)

I checked if the apt-token was successfully add on `pwe-lwr-1`. Yes, it was:

root | @pam | pdm-admin | never | auto-generated by PDM host 'pdm' on Tue, 18 Nov 2025 13:51:38 +0100

The problem appears to occur when retrieving cluster resources.
However, “Remote Tasks” can be accessed, as can be seen in this screenshot:
View attachment 92955

Firefox displays this in the console when the error occurs:
View attachment 92958
And `pveproxy/access.log` on `pve-lwt-1` logs this:

::ffff:xxx.xxx.xxx.xxx - root@pam!pdm-admin [18/11/2025:14:01:12 +0100] "GET /api2/extjs/cluster/resources HTTP/1.1" 200 1901

When I query the API via curl, I get this:

# curl -k -H 'Authorization: PVEAPIToken=root@pam!test=XXXXXXXXXXXXXXXX' https://localhost:8006/api2/extjs/cluster/resources
{"data":[{"level":"","type":"node","node":"pve-lwt-1","cgroup-mode":2,"id":"node/pve-lwt-1","status":"online"}],"success":1}

Does anyone have any ideas?

Upgrade PDM to 0.9.3 fixes the issue.