Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 28 subscribers
  • Views 21800 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

Decrypt & Scan HTTPS Blocks some webs

AquilesMarrero

Good Morning,

I only have the default rule and when i turn on Decrypt & Scan HTTPS XG blocks some webs like Whatsapp and Facebook.

I have installed the certificate on the laptop. I made a test directly connected to the wan and it works.

Some other pages like https://dolartoday.com/ shows fast some times and other doesnt show anything at all.

I'm using SFOS 15.01.0 MR-3

Regards,

AM



This thread was automatically locked due to age.
Parents
  • 0

    Facebook doesn't load properly if I enable Decrypt and Scan HTTPS. I've already installed the CA certificate in my computer.

  • 0 in reply to Omeng

    Hi,

    Clear web history from te web browser and restart Web Proxy on XG. Go to System > Diagnostics > Services > Web Proxy- restart.

    After following these steps, if you still get inadequate access for facebook, I suspect something is blocked through Web Filter.

    Thanks

  • 0 in reply to sachingurung

    I did what you instructed but the problem persists. I tried to remove also the policies for App and Web filtering, it did not solve the problem.

    The problem only exists when I use Chrome. Our users prefer Chrome as their browser and I need to resolve this. One thing that I've noticed is that the problem started when FB updated their cookie policy last May 26, 2016.

Reply
  • 0 in reply to sachingurung

    I did what you instructed but the problem persists. I tried to remove also the policies for App and Web filtering, it did not solve the problem.

    The problem only exists when I use Chrome. Our users prefer Chrome as their browser and I need to resolve this. One thing that I've noticed is that the problem started when FB updated their cookie policy last May 26, 2016.

Children