Univiewer webconsole / webstart does not start due to an expired certificate

Octavie ChakouteOctavie Chakoute Posts: 2,289 admin
edited September 2016 in Dollar Universe - English

Dear webconsole/webstart user,

Be aware that you can get an error message when trying to launch the console via the uvc.jnlp

The message can look like this:

Your security settings have blocked an application signed with an expired or not-yet-valid certificate from running


The workaround consists in adding to the exceptions site the url of the tomcat server.

If you launch the univiewer webconsole from this link: http://server.domain.com:8080/univiewer_webconsole_6.6.21_all_os/,

The tomcat server url is: http://server.domain.com:8080           


In order to add the exception, you have to go to:

Control Panel – Java  - Security


Click on Edit Site List.

Then click on Add and paste the tomcat server url

After that,  click on Ok and  then on Continue. Then you can close the java control panel and redownload the Univiewer Console again.

You need to tick the option: “I accept the risk and want to run this application” and  then Run


Hope this helps!



  • Adrian Fresno menendezAdrian Fresno menendez Team Automic Posts: 92 Journeyman ✭✭✭
    The version 6.6.25 of the Univiewer Console is now available and fixes definitively this problem with the certificate. You can get it from the downloads section, on the folder \public\Workload Scheduler\kit\Univiewer\Univiewer Console\CA
  • Adrian Fresno menendezAdrian Fresno menendez Team Automic Posts: 92 Journeyman ✭✭✭
    Important update: due to the newer and more secure way of signing the jar files starting on uvc 6.6.25, the minimum necessary version of Java on the desktops where the Univiewer Console is launched is Java 7, if you have Java 6, an error will appear after downloading the Webconsole. 
    Therefore, you should also check that the Java version of your desktops is 7 or 8 prior to upgrading.
  • Claudia OstrowskiClaudia Ostrowski Team Automic Posts: 37 Journeyman ✭✭✭

    Update: This is fixed in the last update done by Oracle, to know Java 8 update 111.

    You can find more information here : http://www.oracle.com/technetwork/java/javase/8u111-relnotes-3124969.html

This discussion has been closed.