There can be a few issues after successfully logging in to the ProxySG through the default secure port of 8082.
Even though the blue banner that shows the serial number and the software version can be seen, the rest of the console does not load. When this happens, an error message similar to this one displays:

ClassNotFoundException bluecoat.sgos.ui.SG_UIApp.class

Another error can be found by doing enabling Java Debug on the client machine that is experiencing the issue:

java.lang.NoClassDefFoundError com.sun.deploy.net.protocol.https.Handler$Initializer

Java trusts a separate certificate store than the browser.  When custom Root Certificates are trusted by the browser, they may not be automatically trusted or run by Java.

The Java Applet can also experience problems when loading if it doesn't support TLS1.0, TLS1.1 or TLS1.2 depending on the supported version/s of the ProxySG's certificate.

 

For issues with an untrusted certificate:

  • Log in to the proxy over 8081 or SSH.
  • Go to Configuration>Services>Console, and edit the HTTPS console.
  • Change the certificate that is presented to one that is trusted by Java. Also, the certificate in question can be imported into the Java security settings in control panel. This will need to be done for every machine that is used to access this proxy.

For issues with TLS version incompatibility:

  • Go to "Configure Java" > Advanced tab.
  • Make sure TLS1.0, TLS1.1 and TLS1.2 are enabled
Imported Document ID: 000032830

Thanks for your feedback. Let us know if you have additional comments below. (requires login)

    © 1995-2019 Symantec Corporation