CFS blocks valid sites due to incorrect 64: Not Rated tag

The issue involves SonicWall's Content Filtering Service (CFS) incorrectly categorizing valid websites as 64: Not Rated, causing them to be blocked. This misclassification led to accessibility problems for users relying on CFS for web filtering. SonicWall Engineering has resolved the issue where valid websites were being blocked due to an incorrect "64: Not Rated" category rating in the Content Filtering Service (CFS). While the fix has been implemented, it may take some time to fully propagate

NOTE: SonicWall Engineering team investigated the issue and addressed. However, as with any such resolution, changes may take some time to take full effect and propagate to all.  

Please revert to the previously applied workaround ( of allowing the " Not Rated " category or whitelisting the websites ) and following these steps to verify functionality:

1. After reverting the workaround, test the Content Filtering Service (CFS) by loading a website and confirming whether it is correctly allowed or blocked based on its category. 
   
   
2. If the site does not load as expected, navigate to Policies > Content Filter > CFS Status and check if the Server is Ready. Click the Refresh button and test again.
   
   

3. If the issue persists,it has been observed that the Content Filtering Service (CFS) primarily relies on cache. Clearing the cache should resolve the issue

   .

   To clear the cache, follow these steps:

   1. Navigate to the diagnostic page of your SonicWall firewall. You can find instructions here: How to Access Internal Settings.
   2. Press Ctrl + F and search for the keyword "CFS".
   3. Click on the relevant options as displayed.
      
      
      
      
   4. Scroll to the top, save your changes, and exit.
      
      

   After completing these steps, test the scenario again. The issue should now be resolved.

NOTE: If you continue to experience any issues or need further assistance, please don't hesitate to reach out to our support team and submit a ticket.

Please refer to bug ticket GEN7-52774 for any additional reference.