Applications Systems
Adding a Proxmox server gets stuck on stage 2 in SolarWinds Platform 2025.4
Proxmox server can't complete the Stage 2 when adding a Virtual Object for Monitoring.
First published date
Last published date
Overview
When clicking on Add a Virtual Object for Monitoring for Proxmox and the credentials have been added, it gets stuck on Stage 2.
In the VIM Logs at C:\ProgramData\SolarWinds\Logs\VIM, it shows the following error:
ERROR Client.ProxmoxVEAuthenticator - Failed to get session ticket.System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.0.0.100:8006
Product section
Cause
The Proxmox server is not a Cluster, it is a single node like ESXi VMware.
SolarWinds Platform 2025.4 supports only Proxmox Cluster.
Resolution
Enable the Cluster mode in your Proxmox server. You can do this even if you have only one Proxmox server.
- In the Proxmox dashboard, go to Datacenter.
- Click on Cluster > Create Cluster.
- Select the IP of the Proxmox Server and click Ok.
- After creating the Cluster, try to add the Proxmox in the SolarWinds Platform Web Console.