Can't access management console WebUI (GUI) after upgrade to From 1.x to 2.x
search cancel

Can't access management console WebUI (GUI) after upgrade to From 1.x to 2.x


Article ID: 173196


Updated On:


Management Center


After upgrading from 1.x to 2.x Management Center, can't access WebUI Management Console (GUI) over port 8082 of the Management Center. 


Please find this note made in the Management Center release notes: 

"Upon upgrading from 1.x you may not be able to connect to the MC user interface using HTTPS. If this occurs, you will need to regenerate the default and bluecoat-appliance certificates"‚Äč


Important Considerations for Upgrading to Management Center




To resolve this issue follow the steps below:

 1. Find out which certificates are missing by issuing the following commands:

(enter enable mode password)
# ssl view certificate default
# ssl view certificate bluecoat-appliance

If the CLI reports that the certificate is not present, you'll need to create them. 

2. Create the default and bluecoat-appliance certs (depending on which ones were not present based on the previous commands in step 1). 

# ssl create certificate default

At this point, it will ask you for a subject. You can find information on this command in the Management Center CLI Guide under the section, "ssl create"

It will work if you add the hostname in the following format:

The same can be done for the bluecoat-appliance cert:

# ssl create certificate bluecoat-appliance


After the certificates are created you should be able to access the GUI on port 8082 now. 

If you need to import a custom server (appliance) certificates from your PKI please follow the steps in the following article:

ssl inline



You can enable the HTTP console over port 8080 from the CLI to workaround the issue. To do this, open the CLI and enter the command into the config terminal shell:

(enter enable mode password)
# config t
(config)# security http enable

After that, you can access the MC via  http://<mc_ip>:8080