This is a lab box, on a bench with a flat 192.168.1.x network and g0 is connected. Not connected to the Internet. Can ping g0 from local subnet. When we try to browse to it, we get "The connection for this site is not secure". This actually worked six months or so ago. Not sure what changed, but it sure sounds like a date somewhere, but cannot find anything.
I followed Scott's advice on this link to no avail:
Recently we noticed some changes on the browser behavior where it will use HTTPS even though you try to use HTTP. And this can explain your problem.
If you try to connected to the WLC using HTTPS, it is expected this error message because the browser will not trust the self-signed certificate presented by WLC during the SSL handshake.
Depending on the browser you use, you can disable this behavior and force the browser to actually use HTTP.
- Update the software as per TAC recommended link below. - Check the WLC config using Config Analyzer (link below) - Get a packet capture on client and on WLC to understand why it's not working.
@tdennehy It seems like the issue is related to an SSL certificate expiration or mismatch on your Cisco 9800 wireless controller. Since the error mentions "ERR_SSL_PROTOCOL_ERROR" and the connection being "not secure," it’s likely that the controller's certificate is either expired or no longer trusted by your browser.
Here are a few steps to troubleshoot and resolve this:
Check the System Date and Time: Ensure the date and time on the controller are correct. An incorrect system date can cause SSL certificate issues.
Inspect the Certificate: Try accessing the controller using HTTPS and click on the certificate details in your browser. Check if the certificate is expired or invalid.
Regenerate or Re-upload Certificates: If the certificate is expired, you can either regenerate a new self-signed certificate or upload a valid one (e.g., from a trusted CA).
Fallback to HTTP: If HTTPS access is not critical for your lab setup, you can enable HTTP temporarily for access.
Browser Security Settings: Modern browsers are stricter with outdated or self-signed certificates. Try accessing the controller using an older browser or adjust security settings temporarily.
