You may come across this error if you've disabled TLS 1.0 on your system as the agent will no longer be able to post payloads back to Server Density.
You can work around this issue on fully updated servers by adding specific registry values. These can be added manually via regedit, or by using the commands provided.
First, make sure that your Windows server is up to date, including all updates for .net3.5.
Required Registry Values
In order to use the OS defaults SSL and TLS instead of the hardcoded .NET Framework defaults you need to create a new
SystemDefaultTlsVersions DWORD with the value of 1 at
64Bit Servers will also require the same DWORD with the value of 1 at
Open regedit.exe as an Administrator.
Once open navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727 and then right-click and select 'New' > 'DWORD (32bit) Value'.
Rename the new value to
Modify the new value and set the 'Value Data' to 1.
For 64 Bit servers repeat this process for
creating another new value with the same
SystemDefaultTlsVersions name and Value Data of 1.
You can also set these registry values quickly and easily via the command line. Open cmd as an administrator and execute the following:
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727 /v SystemDefaultTlsVersions /t REG_DWORD /d 1
For 64bit servers, add the additional required value:
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727 /v SystemDefaultTlsVersions /t REG_DWORD /d 1
In order for these new values to take effect, you will need to reboot the server. Once rebooted you should see metrics for the server in your Server Density account.
The above information was taken from the following Microsoft document which you can refer to for further details: