This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Web Filtering is not working correctly

Hi everyone,

From Monday the 19th of December, I've got an issue with my web filtering.

It's configured to filter some categories, like porn, violence .... BUT the pages are not blocked.

I have a cluster of SG430 (active/passive) with 9.713-19 update.

Here is my configuration :

ALL_PRIVE = ALL PRIVATE NETWORKS,

POLITIQUE PAR DEFAUT = DEFAULT POLICY,.

Also the websites listed here are not blocked.

When I test an address of a pron website with source IP from one of my PRIVATE NETWORK, it says that the website is allowed and the

This type of website should not be allowed.

I see in the live log, that the traffic is saw by the proxy.

I have already try to disable and enable the Web protection with the switch in the web interface, and also do the proxy restart command in SSH.

I have checked 10 times the Skiplist, maybe there is a mistake in it, but for me, there is not.

It"s like the UTM doen't can't categorized the URLs.



This thread was automatically locked due to age.
Parents
  • Salut Jean-Charles and welcome to the UTM Community!

    There's a workaround using DNS Request Routes:

         

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  •  I have the same bug on one UTM 450 Cluster. (9.713-19)

    the workaround helps:

    cc set http modulepath  '<DEFAULT>' 

    /var/mdw/scripts/httpproxy restart

     

    lucky for me i have only 3 sophos UTM cluster left to migrate to fortigate.

     

    Nice to see you still active here ;-)

    greets

    zaphod
    ___________________________________________

    Home: Zotac CI321 (8GB RAM / 120GB SSD)  with latest Sophos UTM
    Work: 2 SG430 Cluster / many other models like SG105/SG115/SG135/SG135w/...

Reply
  •  I have the same bug on one UTM 450 Cluster. (9.713-19)

    the workaround helps:

    cc set http modulepath  '<DEFAULT>' 

    /var/mdw/scripts/httpproxy restart

     

    lucky for me i have only 3 sophos UTM cluster left to migrate to fortigate.

     

    Nice to see you still active here ;-)

    greets

    zaphod
    ___________________________________________

    Home: Zotac CI321 (8GB RAM / 120GB SSD)  with latest Sophos UTM
    Work: 2 SG430 Cluster / many other models like SG105/SG115/SG135/SG135w/...

Children