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

Questionable use policy - unable to Proceed

recently updated our appliance to version 4.2.1  and now users are experience a problem with being able to proceed when sites are given warning.

example.   going to "questionable" sites gives the warning page, with the return or "Proceed" buttons..  but they are unable to proceed.

I've seen a couple messages here about this issue in the past, but those were supposedly fixed by subsequent updates..  anyone else seeing this issue?



This thread was automatically locked due to age.
Parents
  • I had this issue and worked it with Support.

    In our case, we narrowed it down to actually being an issue with having Sophos Endpoint clients using Web Control policies that we have pulling policy from the Web appliance. Disabling the Sophos Web Intelligence Service on the endpoint allowed the Proceed button to function as expected. Not sure if it's going out to the masses at the same time, but they are supposed to be upgrading our appliances with version 4.2.1.1 on Monday. They do have a patch available now, but it sounds like Support will have to apply it, and then remove it prior to upgrading to 4.2.1.1 via normal upgrade means.

    Fortunately, we don't use the Warn option or anything else to invoke needing to click on Proceed except for a couple of categories that are acceptable to us to change to Allow for a few days.

    Hope that helps :)

    Ryan

Reply
  • I had this issue and worked it with Support.

    In our case, we narrowed it down to actually being an issue with having Sophos Endpoint clients using Web Control policies that we have pulling policy from the Web appliance. Disabling the Sophos Web Intelligence Service on the endpoint allowed the Proceed button to function as expected. Not sure if it's going out to the masses at the same time, but they are supposed to be upgrading our appliances with version 4.2.1.1 on Monday. They do have a patch available now, but it sounds like Support will have to apply it, and then remove it prior to upgrading to 4.2.1.1 via normal upgrade means.

    Fortunately, we don't use the Warn option or anything else to invoke needing to click on Proceed except for a couple of categories that are acceptable to us to change to Allow for a few days.

    Hope that helps :)

    Ryan

Children
No Data