The user was trying to add scouts using the API but encountered an error message. Dennis suggested adding the TLS setting `$AllProtocols = [System.Net.SecurityProtocolType]'Ssl3,Tls,Tls11,Tls12'[System.Net.ServicePointManager]::SecurityProtocol = $AllProtocols` which resolved the issue.
Read the entire article here...
SSL/TLS
Why is ControlUp ignoring an impending Netscaler SSL certificate expiration linked to an lbvserver?
A user asked why their expiry alert was not alerting for a NetScaler SSL cert. The solution was that the expiry monitor was not enabled. A recommendation was made to look at ControlUp Trigger Packs, which can be found at https://support.controlup.com/docs/trigger-packs?highlight=trigger.
Read the entire article here...
Read the entire article here...
Can ControlUp Insights display ICA proxy connections for my NetScaler Gateway?
The ControlUp console displays ICA proxy connections for NetScaler Gateways, but ControlUp Insights does not. Filtering session activity reports by initial client IP or using export-cuquery may provide the desired results. Details can be found on the ControlUp Support page: https://support.controlup.com/docs/monitor-cluster-powershell-fields-by-table#hdxsessions.
Read the entire article here...
Read the entire article here...
HTTP Scout Fails With Status Code 200 OK
HTTP Scout check failed with a status code of 200 OK and a pattern of "{“status”:“ok”}". The scout had been functioning correctly for several weeks and tests on other custom, public, and servers are working, but the scout does not. When testing in a browser, the user gets the result of "{“status”:“ok”}" which clears when removed and then recreated. A fix is in process and Ehud has offered to provide logs if needed.
Read the entire article here...
Read the entire article here...
Troubleshooting an On-Premises 8.7 Issue with SOP Not Functioning
A customer upgraded their On-Premises environment from 8.5 to 8.7 and introduced SOP 8.7, however it was not functioning. Possible fixes such as restarting ControlUp Monitor and SOP, changing the SSL cert, toggling "Ignore SSL Cert Errors", checking port 443, checking UserManagement logs, checking docker logs, creating a monitor log (Log4Net) and generating the key file again were suggested. They would also benefit from visiting https://support.controlup.com/v1/docs/cop-87-security-enhancement-for-monitor-sop-communication for further instructions.
Read the entire article here...
Read the entire article here...
Replacing a Weak SSL Certificate in ControlUp
A customer reported a weak SSL certificate from ControlUp (SHA1, wrong hostname, self-signed) and asked if any issues may surface when switching to a trusted, SHA256 certificate with the correct hostname. It was suggested that the certificate switch should work without any issues, but the current COP version, certificate name, and file were requested for confirmation. It was later established that the certificate deployed with Console, Monitor, and Agent was the culprit, and that the old certificate just needs to be replaced.
Read the entire article here...
Read the entire article here...