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

SFOS 17.1.3 MR-3 HTTPS sessions are freezing.

Maxim Grechikhin

Hi all!

Recently we got "XG 135 w" with subj firmware. After I configured all necessary policies and rules I performed a test launch by switching a couple of live users from old Cisco firewall to this new one.

Our users work with cloud CRM via HTTPS protocol and all switched users noticed that after a time webpage of CRM freezes and it is impossible to refresh it. Users had to relogin into CRM.

From my side I noticed the same with online radio app (PCradio) which works fine through Cisco firewall but hiccups and freezes while using Sophos.

Any ideas how to overcome this disappointment?

I didn't check the workflow with previous (recommended) firmware because it does not allow to restore the configuration made under newer one and there are a lot of settings to reproduce them again manually.



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

    Is HTTPS scanning enabled? Try disabling it in the appropriate firewall rule.

    Currently it seems that 17.1 releases have a lot of problems. We have 17.1.1 with some trouble and MR2 and MR3 also have major issues.

  • 0 in reply to Jelle

    Hi Jelle,

    Thank you for the reply. Unfortunately or not, I do not have any firewall rules with enabled HTTPS scanning, just in order to avoid unecessary problems with certs. But it was the first place that I had looked at. As far as I convincied that it is a firmware issue I would appreciate to confirm that MR2 doesn't have the same issue. Because MR2 is the only one alternative option which is available to boot.

Reply
  • 0 in reply to Jelle

    Hi Jelle,

    Thank you for the reply. Unfortunately or not, I do not have any firewall rules with enabled HTTPS scanning, just in order to avoid unecessary problems with certs. But it was the first place that I had looked at. As far as I convincied that it is a firmware issue I would appreciate to confirm that MR2 doesn't have the same issue. Because MR2 is the only one alternative option which is available to boot.

Children
No Data