Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 7 subscribers
  • Views 1850 views
  • Users 0 members are here
Options
Suggested
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

Since Update 9.715-4 Web Filtering not Working?

Chris -

I know, this one sounds strange: After Upgrade to 9.715-4 and Web Filtering turned on, Internet Connection stopped working. Turning Web Filtering off: Everything works fine. As far as i remember i did no other configuration-changes after upgrade, so i can see no other reason...

Everything (with web filter on) worked fine before update. But I don't want to rule out that I haven't changed something...and forgotten it :). 

Any hints, where to start?

Thanks!



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Raphael Alganes

    Guess there is no Ticket-Option for me, i´m Sophos UTM Home Free User.

    Again: When turning Web Filtering off, everythings works normal. As soon as i activate Web Filtering in transparent Mode (no authentification), every Website ends with a time out error. Log for Web Filter is completely empty, which is very strange. What do i miss? Anything to do about that 8080-Port?

  • 0 in reply to Chris -

    Hello Chris,

    Thanks for this additional information. Could you confirm your UTM's pattern version? under Management>Up2date>Pattern

    Also, could you show the error you are encountering with port 8080?

    What happens when you use policy test? and could you test disabling all Web Filter profiles and use only the Base Policy? 

    Kindly let us know how it goes. Many thanks for your time and patience and thank you for choosing Sophos

    Cheers,

    Raphael Alganes
    Community Support Engineer | Sophos Technical Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.

  • 0 in reply to Raphael Alganes

    Pattern Version: 228881

    No Error with 8080. Just a suspicion that the port might be blocked somehow. But the logs don't give anything in this regard.

    Policy test: " An error occurred while processing the policy test request."

    Base Policy only: WORKS! But i need to tick "Do not proxy HTTPS traffic in transparent mode". If not ticked, same error. Even with Base Policy only Policy test still throws the above error.

    Additional Info 1/3: Web Filter Log stays empty all the time (except a short notice when i turn off the filter: "2023:07:28-19:41:22 firew_ttt URID[31081]: T=31081 ------ 1 - [exit] SIGTERM: exiting"); for testing purpose i´ve added a Domain under " Block These Websites" in Base Policy, Domain is NOT blocked, no log entry --> Guess Web Filtering isn´t working at all.

    Additional Info 2/3: Selfmonitoring-Log:

    2023:07:28-21:32:12 firew_ttt selfmonng[3948]: W triggerAction: 'cmd'
2023:07:28-21:32:12 firew_ttt selfmonng[3948]: W actionCmd(+):  '/var/mdw/scripts/httpproxy restart'
2023:07:28-21:32:14 firew_ttt selfmonng[3948]: W child returned status: exit='0' signal='0'
2023:07:28-21:32:19 firew_ttt selfmonng[3948]: I check Failed increment httpproxy_running counter 1 - 3
2023:07:28-21:32:24 firew_ttt selfmonng[3948]: I check Failed increment httpproxy_running counter 2 - 3
2023:07:28-21:32:29 firew_ttt selfmonng[3948]: W check Failed increment httpproxy_running counter 3 - 3
2023:07:28-21:32:29 firew_ttt selfmonng[3948]: W NOTIFYEVENT Name=httpproxy_running Level=INFO Id=141 suppressed
2023:07:28-21:32:29 firew_ttt selfmonng[3948]: W triggerAction: 'cmd'
2023:07:28-21:32:29 firew_ttt selfmonng[3948]: W actionCmd(-):  '/var/mdw/scripts/httpproxy restart'
2023:07:28-21:32:34 firew_ttt selfmonng[3948]: I check Failed increment httpproxy_running counter 1 - 3
2023:07:28-21:32:39 firew_ttt selfmonng[3948]: I check Failed increment httpproxy_running counter 2 - 3
2023:07:28-21:32:44 firew_ttt selfmonng[3948]: W check Failed increment httpproxy_running counter 3 - 3
2023:07:28-21:32:44 firew_ttt selfmonng[3948]: W NOTIFYEVENT Name=httpproxy_running Level=INFO Id=141 suppressed
2023:07:28-21:32:44 firew_ttt selfmonng[3948]: W triggerAction: 'cmd'
2023:07:28-21:32:44 firew_ttt selfmonng[3948]: W actionCmd(+):  '/var/mdw/scripts/httpproxy restart'
2023:07:28-21:32:47 firew_ttt selfmonng[3948]: W child returned status: exit='0' signal='0'
2023:07:28-21:32:52 firew_ttt selfmonng[3948]: I check Failed increment httpproxy_running counter 1 - 3

    Additional Info 3/3:

    SSH on Sophos UTM --> /var/mdw/scripts and run ./httpproxy restart:

    Restarting httpproxy
:: Stopping httpproxy                                                                                                                    done
:: Starting httpproxystartproc:  cannot execute /var/chroot-http/usr/bin/httpproxy: Exec format error
                                                                                                                                         failed



    Update 2
    [edited by: Chris - at 8:27 PM (GMT -7) on 28 Jul 2023]
Unfiltered HTML