This KB describes an issue where UTM Web-Filtering profiles configured in the CLI are not displayed in J-Web, even though the configuration is present and successfully committed on the device.

• UTM Web-Filtering profiles configured in the CLI are not visible in J-Web.
• The configuration is present and valid in the CLI but is missing from the J-Web interface.
• Restarting web-management services or accessing J-Web from different browsers does not resolve the issue.
• Profiles created through J-Web initially appear correctly in both J-Web and the CLI.
• After a commit, the profiles disappear from J-Web while remaining present in the device configuration.

The issue occurs when juniper-enhanced cache and juniper-enhanced server are configured under UTM Web Filtering. A format mismatch during cache synchronization can trigger a runtime exception, preventing J-Web from correctly displaying the configured profiles.

Example:

juniper-local {

   profile <profile-name> {

       default log-and-permit;

       category {

           <category-name> {

               action log-and-permit;

           }

       }

       timeout 3;

   }

}

juniper-enhanced {

   cache;

   server;

}

Workaround: Remove the juniper-enhanced cache configuration and restart the UTM daemon:

#delete security utm feature-profile web-filtering juniper-enhanced cache