⚠️ OPSWAT Central Management v7 and My OPSWAT On-Premises (My OPSWAT Central Management v8) will reach End of Sale on July 31, 2025, and End of Life on January 31, 2027. We encourage you to upgrade to My OPSWAT Central Management v10 before Janauary 31, 2027, to ensure continued support and access to the latest features.

The console failed to reload after disabling HTTPS in Secure Connection settings

TypeDetail
ProblemAfter disabling HTTPS mode in Secure Connection settings, the console failed to load with an error related to a secure connection.
CauseThe Server URL has not updated to http://.
TroubleshootingCan access the management console with http:// prefix
SolutionManually change the Server URL prefix to http://.

After disabling HTTPS mode in Secure Connection settings without manually updating Server URL to HTTP, the console failed to reload .

For instance, you may see the error "This site can't provide a secure connection" on Google Chrome.

One possible cause is that upon disabling HTTPS mode, the Server URL's protocol prefix was not updated to http:// manually. By default, the console will be reloaded with the configured Server URL. In other words, it will be reloaded with https and as a result, the OCM instance cannot provide a secure connection, the web browser will encounter an error.

You need to manually change the console URL to http on your web browser to able to access the console and follow the document here to update the Server URL to http.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard