Nodes don't show on the Proxmox Overview Tab after upgrade to 4.32.0

[JerseyTechGuy]

Describe the bug
After applying the upgrade to 4.32.0 the Nodes no longer show on the Overviews Tab. The column headers are there but no nodes

To Reproduce
Steps to reproduce the behavior:

1. Upgrade to version 4.32.0 from version 4.2x.x
2. Refresh pulse app in the brower
3. Nodes header is there on the overviews page but no nodes show.

Expected behavior
In the prior versions the nodes showed without issue

Environment:

• Pulse Version: 4.32.0
• Installation Type: Docker on a Raspberry Pi 5 with Raspberry Pi OS

[rcourtman]

Thanks for the report. The 4.32.0 regression that stopped adding the default PVE port when using https://host without an explicit port is fixed in 4.32.1. Nodes should populate again after upgrading. Please retry on 4.32.1 and let me know if nodes still don’t appear.

[JerseyTechGuy]

I upgraded to 4.32.1 and it has the same issue. Screen shot attached. There should be 2 nodes there from 2 different servers.

[ZaDarkSide]

Last known version to work correctly is 4.31.0 everything after this version presents this bug/regression, also temperatures stopped working even if the sensor proxy is working correctly. Downgrading to 4.31.0 fixes the issue, you don't need to reinstall sensor proxy, if it was working before.

You can downgrade Pulse to 4.31.0 using this command:

curl -fsSL https://raw.githubusercontent.com/rcourtman/Pulse/main/install.sh | bash -s -- --version v4.31.0

[rcourtman]

Thanks for the detail. 4.32.1 restored default-port handling for new inputs, but configs saved on 4.32.0 may still have hosts without the default Proxmox port, which would make Pulse call port 443 and leave the Nodes table empty. I need to confirm 100% this is what you’re seeing: could you open Settings → Nodes and check whether your PVE/PMG hosts (and any cluster endpoints) are missing :8006 (PBS: :8007)? If they are, add the default port, save, and restart Pulse to see if the nodes reappear. I have a patch ready to auto-migrate saved hosts to include the default ports for the next point release.

[JerseyTechGuy]

I checked the settings and both have :8006. I have attached a screen shot showing the ports.

[rcourtman]

Thanks for confirming the ports. 4.32.3 includes the host normalization + default-port migration that covers configs saved on 4.32.0/4.32.1. Please try 4.32.3 and restart; if the Nodes tab is still empty, could you grab journalctl -u pulse --no-pager | grep -i proxmox around the time you refresh Overview? That will show whether Pulse is polling the hosts and what endpoint it’s hitting.

[ZaDarkSide]

4.32.3 has same bug/regression
running journalctl -u pulse --no-pager | grep -i proxmox doesn't returns anything relevant

[dsouzamiranda]

Upgraded to 4.32.3 and everything works just changing port 8086 to 443 at the end of the address.
I'm using reverse proxy pointing the this address.

[rcourtman]

4.32.3 normalizes saved PVE/PBS/PMG hosts and restores default ports for configs saved on 4.32.0/4.32.1. If the Overview still shows no nodes after upgrading and restarting Pulse, Pulse isn’t reaching the PVE API. The log grep you tried would skip relevant lines because they don’t contain "proxmox"; please share the Pulse log around startup/polling with something like:

ajournalctl -u pulse --no-pager | grep -i "get nodes" -C2

plus any nearby "Failed to create PVE client" lines. That will show which host URL Pulse is using and what the API returned.

[Vaskyy]

I'm using pulse in docker container. I cannot attach or connect to console, but i can acess logs from portainer.
Just updated to 4.32.3.

Using Portainer to get logs:

2025-11-21T23:20:58+01:00 INF Nodes configuration loaded | component=pulse-config file=/data/nodes.enc pve=2 pbs=0 pmg=0 encrypted=true
2025-11-21T23:20:58+01:00 INF Loaded nodes configuration | component=pulse-config pve=2 pbs=0 pmg=0
2025-11-21T23:20:59+01:00 INF Initializing PVE clients | component=pulse-config count=2
2025-11-21T23:20:59+01:00 INF Configuring PVE instance | component=pulse-config name=Vaskyy-Nuc host=https://192.168.178.10:8006 user= hasToken=true
2025-11-21T23:20:59+01:00 INF PVE client created successfully | component=pulse-config instance=Vaskyy-Nuc
2025-11-21T23:20:59+01:00 INF Configuring PVE instance | component=pulse-config name=Vaskyy-Five host=https://192.168.178.33:8006 user= hasToken=true
2025-11-21T23:20:59+01:00 INF PVE client created successfully | component=pulse-config instance=Vaskyy-Five

Settings - Proxmox VE nodes screenshot:

Proxmox Overview Nodes screenshot:

Five is a Raspberry Pi 5 running Lierfang Pxvirt 8.4.10 (Linux 6.12.47+rpt-rpi-v8)
Nuc is a Asus Nuc running PVE 9.0.11 (Linux 6.14.11-4-pve)

[JerseyTechGuy]

Sorry for the late response. Just got home from the office. After the update to 4.32.3 the issue is still there. No nodes showing on the Proxmox tab under overview.

I also rebooted the Raspberry Pi 5 that I run pulse on.

Trying to run journalctl -u pulse --no-pager | grep -i proxmox before refresh, after refresh during refresh always shows nothing. Running without the grep command I do get a ton of pulse logs for the servers (VMs) but it's not finding anything with proxmox in it.