[SOLVED] failed to parse api response

crazywolf13

Member
Oct 15, 2023
66
8
13
Hi,

On PDM 0.9.2 I keep getting this error when visiting the dashboard:1763382303381.png

I can't see any real errors in the network tab nor the console.

But on this url (found in network tab):

https://10.10.20.3:8443/api2/extjs/pve/remotes/tiny_cluster/resources


I get this reply:
errors{}
message"api returned unexpected data - failed to parse api response"
status400
successfalse

On one specific view it shows a bit more info:
1763382395864.png

All Nodes are up-to-date on the latest changes on pve-no-subscription.
 
After updates to PVE, I get this same error from DM when trying to view my cluster. I have removed the cluster from DM and re-added. No luck.

Thanks,

Matt
 

Attachments

  • Screenshot 2025-11-17 092411.png
    Screenshot 2025-11-17 092411.png
    23.3 KB · Views: 5
  • Screenshot 2025-11-17 092426.png
    Screenshot 2025-11-17 092426.png
    56.2 KB · Views: 5
should be fixed in the next bump of PDM!
 
Upgraded to Datacenter Manager 0.9.3. I still had an API error message on the updates tab of a node. I upgraded this from Virtual Environment 9.0.15 to 9.0.17 and the API error on the update page was also resolved.
 
  • Like
Reactions: fabian
I've upgraded both of my PVE nodes to 9.0.18 and still get this API error on the mobile web GUI. "Desktop" mode seems to function fine.
 

Attachments

  • Image.png
    Image.png
    197.6 KB · Views: 8
I've upgraded both of my PVE nodes to 9.0.18 and still get this API error on the mobile web GUI. "Desktop" mode seems to function fine.
this should be fixed in pve-yew-mobile-gui >= 0.6.4!
 
Hi, im getting this error today as well, however seeing the comments about updating "pve-yew-mobile-gui >= 0.6.4!", i updated all nodes yet im still getting his error?
 
please try to refresh your browser cache or check using a fresh profile.
 
what does "dpkg -l | grep pve" say?
 
Hello everyone,

after upgrading my 3-node PVE cluster from 8.4 to 9.1 I can no longer connect the cluster to Proxmox Datacenter Manager (PDM). The remote is added successfully, fingerprint validation works, and the login/token creation works as well — but when PDM tries to load the cluster afterwards, I get this error:
Code:
api error (status = 400: api returned unexpected data - failed to parse api response)

What I have already verified
All nodes reachable from PDM
From the PDM host:
Code:
curl -k https://192.168.1.101:8006/api2/json/nodes   → 401 (expected without auth)
curl -k https://192.168.1.102:8006/api2/json/nodes   → 401
curl -k https://192.168.1.104:8006/api2/json/nodes   → 401

Token authentication created correctly
In PVE GUI:
Datacenter → Permissions → API Tokens → Add
User: root@pam
Token ID: pdm-admin
Privilege Separation: OFF
Expire: never
Token name becomes:
root@pam!pdm-admin
The secret is correctly saved.
Token works via cURL (JSON response OK)
On the PDM host:

Code:
curl -k \
  -H "Authorization: PVEAPIToken=root@pam!pdm-admin=SECRET" \
  https://192.168.1.101:8006/api2/json/nodes

This returns valid JSON.
So authentication and API access from the PDM host to the PVE nodes is working.

What happens in PDM
During the “Add Remote” wizard:
Probe Remote → OK
Token creation → OK
Fingerprints detected → OK
Summary → OK
But immediately after clicking Finish, PDM shows:

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

Environment
Cluster:
PVE01: 9.1.1 / kernel 6.17.2-1-pve
PVE02: 9.1.1
PVE04: 9.1.1
PDM:
Version: 0.1.12 (ALPHA)
OS: Linux PDM 6.8.12-15-pve
All nodes have valid SSL certificates and fingerprints match correctly.
What I suspect
It looks like PDM expects JSON but receives something else (likely an auth or redirect page).
This may be related to recent changes in PVE 9.1 API output or authentication.
There are similar reports here:
Question
Is there a known incompatibility between PDM 0.1.x and Proxmox VE 9.1?
Is this a bug in the current PDM alpha?
Or does PVE 9.1 require a different token/permission setup?

Any help or hints are greatly appreciated.
Thanks!
 
Hello everyone,

after upgrading my 3-node PVE cluster from 8.4 to 9.1 I can no longer connect the cluster to Proxmox Datacenter Manager (PDM). The remote is added successfully, fingerprint validation works, and the login/token creation works as well — but when PDM tries to load the cluster afterwards, I get this error:
Code:
api error (status = 400: api returned unexpected data - failed to parse api response)

What I have already verified
All nodes reachable from PDM
From the PDM host:
Code:
curl -k https://192.168.1.101:8006/api2/json/nodes   → 401 (expected without auth)
curl -k https://192.168.1.102:8006/api2/json/nodes   → 401
curl -k https://192.168.1.104:8006/api2/json/nodes   → 401

Token authentication created correctly
In PVE GUI:
Datacenter → Permissions → API Tokens → Add
User: root@pam
Token ID: pdm-admin
Privilege Separation: OFF
Expire: never
Token name becomes:
root@pam!pdm-admin
The secret is correctly saved.
Token works via cURL (JSON response OK)
On the PDM host:

Code:
curl -k \
  -H "Authorization: PVEAPIToken=root@pam!pdm-admin=SECRET" \
  https://192.168.1.101:8006/api2/json/nodes

This returns valid JSON.
So authentication and API access from the PDM host to the PVE nodes is working.

What happens in PDM
During the “Add Remote” wizard:
Probe Remote → OK
Token creation → OK
Fingerprints detected → OK
Summary → OK
But immediately after clicking Finish, PDM shows:

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

Environment
Cluster:
PVE01: 9.1.1 / kernel 6.17.2-1-pve
PVE02: 9.1.1
PVE04: 9.1.1
PDM:
Version: 0.1.12 (ALPHA)
OS: Linux PDM 6.8.12-15-pve
All nodes have valid SSL certificates and fingerprints match correctly.
What I suspect
It looks like PDM expects JSON but receives something else (likely an auth or redirect page).
This may be related to recent changes in PVE 9.1 API output or authentication.
There are similar reports here:
Question
Is there a known incompatibility between PDM 0.1.x and Proxmox VE 9.1?
Is this a bug in the current PDM alpha?
Or does PVE 9.1 require a different token/permission setup?

Any help or hints are greatly appreciated.
Thanks!
Thank you, after an update and reboot its all working again.