Proxmox integration shows NAN for stats and doesn't list CTs/VMs

[Aikufurr]

Environment

Docker

Version

No response

Describe the problem

Followed the setup guide and added the System Health Monitoring widget.
But, uptime shows NAN, stats show NAN, and doesn't list my CTs/VMs.~
Checked homarr logs and doesn't report any issues.

Logs

yarn run v1.22.19

$ ts-node ./migrate.ts

Done in 2.25s.

Starting production server...

Listening on port 7575 url: http://557bf27fa281:7575

ℹ Local icons repository directory exists and contains 0 icons

ℹ Saving updated configuration of 'default' config.

Context

Please tick the boxes

• I confirm that I attached the proper logs
• I've read the docs
• I've checked for duplicate issues
• I've tried to debug myself

[github-actions]

Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly.

[timfischbach]

Looks like missing permissions for me. Did you follow the Homarr guide for Proxmox integration? Did you give the token and user group PVEAuditor rights inside Proxmox? Also the api-token, user and group shall not have the same names, since this bugs out the Proxmox API :)

[Aikufurr]

Yeah I followed that guide, used the same names it showed and set permissions to PVEAuditor.

[duka10]

Look on proxmox do you have status for all your containers and vm or you have question mark (unknown status)?
You vm/conctainers can be live but service with statuses stopped, you can check services on proxmox with systemctl status pve*, maybe pvestatd.service is just stoped.

[sosudaniel]

Hello everyone, I have the same problem, on my machine looks like pvestatd.service is running

● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-09-20 22:13:44 EEST; 8min ago
Process: 1169 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
Main PID: 1185 (pvestatd)
Tasks: 1 (limit: 18370)
Memory: 109.0M
CPU: 3.000s
CGroup: /system.slice/pvestatd.service
└─1185 pvestatd

Sep 20 22:13:43 proxmox systemd[1]: Starting pvestatd.service - PVE Status Daemon...
Sep 20 22:13:44 proxmox pvestatd[1185]: starting server
Sep 20 22:13:44 proxmox systemd[1]: Started pvestatd.service - PVE Status Daemon.

[duka10]

Try to restart pvestatd.service. If you get error, reboot proxmox server.

[sosudaniel]

@duka10 neither restarting the service or the proxmox host does not work

[sosudaniel]

additional info, unchecking the Ignore Certificate Errors setting will make the widget to not show anything

[duka10]

If you check ignore cert. the widget will not show anything because you are probably accessing proxmox over http, and not over https.

First, does this widget work for you from the start and you now got this error or you got this error when you setup for the first time?

[sosudaniel]

the widget does not work from the start

[sosudaniel]

update: if setting the administrator role, then everything works as expected

[manuel-rw]

Can we consider this as resolved then?

[sosudaniel]

for me it does the job like this, so yes we can close this. still would be nice to know why setting the PVE Auditor role as specified in the config manual does not do it.

also the issue was open by @Aikufurr not by me. I just stumbled upon it and tried to help the investigation as I was also affected by this.

[Razor094]

I have the same problem. If I only add a Proxmox card, it looks like the first picture and if I need OpenMediavault, it is completely broken.

I have read the documentation, searched twice for the API key and cannot resolve the problem.
I hope someone can help me. Thanks in advance

[manuel-rw]

I have the same problem. If I only add a Proxmox card, it looks like the first picture and if I need OpenMediavault, it is completely broken.

I have read the documentation, searched twice for the API key and cannot resolve the problem. I hope someone can help me. Thanks in advance

Please post your logs

[Razor094]

Here they are:

Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 2.42s.
Starting production server...
Listening on port 7575 url: http://48757887a8e6:7575
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 2.44s.
Starting production server...
Listening on port 7575 url: http://48757887a8e6:7575

[manuel-rw]

Have you followed the documentation at https://homarr.dev/docs/integrations/hardware step by step?

[jimsander]

update: if setting the administrator role, then everything works as expected

I had the same issue. Overlooked the Privilege Separation: unchecked step.
Go back and edit the API token and voila.