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

Error in Web Protection Log

I have the latest home edition (9.402-7) but this issue has been happening for a while now. I receive the following error on certain devices going to particular URLs. For example, my daughters iPhone using the Snapchat app receives this error:

2016:05:14-18:47:45 salkeldfam httpproxy[5753]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="read_request_headers" file="request.c" line="1576" message="Read error on the http handler 86 (Input/output error)"

It will not show the URL that is being used, just this error.

Is there a way to locate the rule that is causing this and correct it?

Thanks

This thread was automatically locked due to age.

Parents

0 neil_g over 8 years ago

Ive been having this on our corporate UTM since 9.402-7. Have raised a ticket with support.
Cancel
Vote Up 0 Vote Down

Cancel
0 AaronSalkeld1 over 8 years ago in reply to neil_g

Thanks for this. Will be very interested in seeing what they come back with. My guess is there is a rule somewhere that has an error.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 AaronSalkeld1 over 8 years ago in reply to neil_g

Thanks for this. Will be very interested in seeing what they come back with. My guess is there is a rule somewhere that has an error.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 neil_g over 8 years ago in reply to AaronSalkeld1

Apparently the issue was to do with the categorisation look up, there was an issue with their SXL look up servers.

This has now been resolved, the errors have gone for us.
Cancel
Vote Up 0 Vote Down

Cancel
0 AaronSalkeld1 over 8 years ago in reply to neil_g

I am glad you have your fixed. [:)]

I have checked my log and the errors are still there.

How did they correct the SXL issue? Was it a back end fix or something on your appliance?

Wonder how I can re set my categorizes.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 8 years ago in reply to AaronSalkeld1

I don't know if this will work, but it's worth a try. Try disabling/enabling SXL. From the commandline as root:

cc set http use_sxl_urid 0
cc set http use_sxl_urid 1

Any luck with that?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
0 AaronSalkeld1 over 8 years ago in reply to BAlfson

Thanks for your time in reply to this Bob.

I have run both commands and still the same issue.

Even if I run the first one and watch the log, the errors are still there. Once I run the second command, the errors are still there.

So no change after running these commands.

Thanks

Aaron
Cancel
Vote Up 0 Vote Down

Cancel