Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Firewall IPsec Site2Site settings page slowdown

Hi all,

when we try to add or change a configuration on the IPsec settings page on our XG/XGS Firewalls we always have to wait for about 2 minutes for the site to load and for it to be usable. The web browser shows the message "This page is slowing down Firefox. To speed up your browser, stop this page.". If you change a setting for example the local/remote subnet, you have to wait again for 2 minutes to continue/save.

This issue has been present for years now and through all the version from V18, V18.5, V19,  V19.5 to V20. This issue is also present on all the models we have in production. (XG330, XG450, XGS2100, XGS3300) My guess this has nothing to do with the firewall itself but more of the webpage trying to load something. Most likely something javascript related.

It doesn't matter which browser we use (Firefox, Edge, Chrome, etc.) or if we use the local firewall administrator or if we go through Sophos Central. We have tried different endpoints and we even tried from home with personal devices which don't have an endpoint protection installed.

Does anyone else have this issue? If so, is there a fix for it?

Greetings

Jens



Added TAGs
[edited by: Raphael Alganes at 5:45 AM (GMT -7) on 27 Aug 2024]
Parents
  • I was unable to reproduce or witness the issue on the user-provided setup.
    However, we encountered a similar problem, debugged it further, and implemented the following changes, which seem to resolve the issue:

    High-level changes made include:

    • Utilizing track by $index to track items by their index in Angular.
    • Avoiding complex ng-if conditions by performing filtering in advance with the newly created filteredHostList function in AngularJS.

     , could you please confirm whether the issue is not occurring on both of the provided devices?

Reply
  • I was unable to reproduce or witness the issue on the user-provided setup.
    However, we encountered a similar problem, debugged it further, and implemented the following changes, which seem to resolve the issue:

    High-level changes made include:

    • Utilizing track by $index to track items by their index in Angular.
    • Avoiding complex ng-if conditions by performing filtering in advance with the newly created filteredHostList function in AngularJS.

     , could you please confirm whether the issue is not occurring on both of the provided devices?

Children