Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 2097 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

All HTTP Requests are being Blocked - No Changes were applied to Web Filtering

DavidHudson

Web Filtering is blocking all HTTP requests - no changes were made.

The Web Filtering log shows all HTTP requests started to be blocked at  2019-02-20 18:46 (EST) .

________________________________________________________________

<Previously Posted - Firmware Upgrade on 2019-02-21 07:55 (EST) does not appear to be the issue>

Originally the Web Filtering / HTTP block appeared to coincide with the morning firmware upgrade

Applied the firmware update to 9.600-5 - no other changes made.

Immediately access to websites began to timeout with browsers displaying the Sophos time-out error message.  It appears that HTTP does not work however HTTPS does work.
Why would the firmware update cause this problem?

__________________________________________________________________

Example of error message:

An error occurred while handling your request
While trying to retrieve the URL:    http://thestar.com/
The content could not be delivered due to the following condition:  Connection to server timed out

Web Filtering Log:

2019:02:22-07:35:36 xxxutm httpproxy[5734]: id="0002" severity="info" sys="SecureWeb" sub="http" name="web request blocked" action="block" method="GET" srcip="999.999.999.222" dstip="192.206.150.106" user="" group="" ad_domain="" statuscode="504" cached="0" profile="REF_DefaultHTTPProfile (Default Web Filter Profile)" filteraction="REF_HttCffxxxBaseFilte (xxx Base Filter)" size="2500" request="0xdb1cf100" url="http://thestar.com/" referer="" error="Connection to server timed out" authtime="0" dnstime="10859" aptptime="180" cattime="67206" avscantime="0" fullreqtime="60237598" device="0" auth="0" ua="Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0" exceptions="" category="134" reputation="neutral" categoryname="General News" country="Canada"


Web Filtering Settings:


Web Filtering - On
Allowed Networks - set for existing networks (no changes)
Operation Mode - Transparent
Default Authentication - None
Device-specific authentication - disabled
HTTPS Scan Settings - URL filtering only

 

Thanks,
David



This thread was automatically locked due to age.
  • 0

    This email was lead me to review the previous days web filtering log:

     

    From: Firewall Notification System [mailto:do-not-reply@fw-notify.net]
    Sent: Wednesday, February 20, 2019 7:10 PM
    To: David Hudson
    Subject: [utm.xxxxxxxxxx.ca][WARN-129] Spam Filter cannot query database servers

     

    The spam filter daemon is unable to reach the database servers via HTTP. Please make sure that the device is able to send HTTP (TCP port 80) requests to the Internet. You may have to allow such traffic on upstream devices.

    --

    System Uptime      : 61 days 21 hours 15 minutes

    System Load        : 0.50

    System Version     : Sophos UTM 9.510-5

  • 0

    Problem solved!  The UTM was okay, always curious when no changes are made yet problems start appearing.

    The problem was our ISP's router, it had a redirect that was causing the problem.

    Thanks,
    David

Unfiltered HTML