Guest User!

You are not Sophos Staff.

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

XGS116: Website does not load correctly

Hello

We have 2 Sophos XGS 116 and one website is not displayed correctly.
The main.css file does not download or can't be encoded.

I have created a ticket and already had a troubleshooting session with someone from Sophos. So far, we can't workaround the issue.
Does anyone have a clue on what is wrong on the XGS or is someone able to reproduce on their product?

We've tested the access also with other models, and there it works:

  • Location 1: XGS116 (SFOS 19.0.0 GA-Build317) -> not working
  • Location 2: XGS116 (SFOS 19.0.1 MR-1-Build365) -> not working
  • Location 3: SFV1C4 (SFOS 19.0.0 GA-Build317) -> working
  • Location 4: SG210 (SFOS 19.0.0 GA-Build317) -> working

Kind regards



This thread was automatically locked due to age.
Parents Reply Children
  • Hello Emmanuel

    You are right, I could have provided more details.

    • Checked the firewall rule.
    • Checked the policy test and PCAP and traffic was allowed through Rule 57
    • Checked with and without web proxy and decrypt Https traffic.
    • Checked the interface configuration.
    • Checked the Conntrack and verified that the traffic is passing through the correct rules.
    • Checked the TCPDUMP and verified that the MTU and interface was correct.
    • Checked the Wireshark PCAP.
    • Checked the drop packet capture and there was no drop.
    • Checked with the URL exception and allowed the URL in the web policy as well as tried with the FQRN host in the firewall rule.
    • Checked the log viewer and it was allowing the traffic as per the web policy.
    • Checked the Awarrenhttps logs.
    • Cleared the conntrack for the source user.

    I can try what you have written above. But from my understanding, if I create a rule where no filter is applied, I wouldn't need to create any exceptions as nothing should be blocked / filtered.

  • Hello there,

    I believe the Proxy or DPI might be affecting this, so I would recommend you to also disable the DPI engine, as a test.

    Protect >> Rules and Policies >> SSL/TLS inspection rules >> SSL/TLS inspection settings >> Advanced Settings >> Disable

    When you don't select any option in the Firewall Rule the DPI runs by default, so this is the one that might be actually causing the issue.


     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support VideosProduct Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.