Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Unable to register agent-initiated agents

Hello

I am having an issue with agent-initiated agents being unable to register to the Orion server.

Server-initiated nodes works fine.

Browsing to this https://OrionServer:17778/solarwinds/agentmanagement/api/TestConnection

Returns a ERR_CERT_COMMON_NAME_INVALID which doesn't really make sense to me. It is correct the CN=SolarWinds-Orion and there are no SAN's. As far as I know this certificate is just shipped with the Orion software.

I hope some one can assist with this issue. A case for SolarWinds has also been opened.

Find more posts tagged with

Accepted answers

admin_nsn

Hi Jeremy,

SolarWinds support helped us identify and resolve the issue.

Root cause: The following registry key was misconfigured:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\DisableRenegoOnServer

When set to 1, this disables the client's ability to renegotiate SSL/TLS sessions, which was causing the agent issue. Setting it to 0 restores renegotiation and resolves the problem.

Security note: Enabling SSL/TLS renegotiation does fix the agent issue, but it slightly weakens the security posture of the Orion Server. Please ensure this trade-off is reviewed and accepted by your security team before applying in production.

All comments

jeremymayfield

This is a well-documented SSL/TLS certificate validation issue specific to the SolarWinds Agent communication channel. Here is a structured analysis.

The ERR_CERT_COMMON_NAME_INVALID error on port 17778 is directly preventing agent-initiated registration. The root cause is that modern browsers and the SolarWinds Agent communication stack have deprecated CN-only certificate validation in favor of Subject Alternative Names (SAN). The shipped Orion self-signed certificate lacks SANs, which is the core of the problem.