Skip to main content
gsarica
gsarica
New Member
November 16, 2016
Question

Chrome - ERR_EMPTY_RESPONSE

  • November 16, 2016
  • 1 reply
  • 15795 views

Just wondering if anyone has seen this error message in Chrome before, ERR_EMPTY_RESPONSE. We've been testing deep packet inspection and I thought it may be due to that, but a user who isn't in the test group reported he's seeing the same issue in Chrome also. Basically a page will load with this error and a refresh will allow access to the site. This happens pretty randomly, on different sites with no rhyme or reason. We just updated to 5.4.2, though I was seeing this on 5.4.1. Is there anything I can check? 

 

Thanks!

    1 reply

    Alby23
    Alby23
    New Member
    November 22, 2016

    Just to make a test, try to create a SSL/SSH Inspection Profile with "Inspect All Ports" in the Deep Inspection Section.

    alSwib
    alSwib
    New Member
    November 28, 2016

    I also have the same issue on 5.4.1, except a little worse; any site, not on the SSL inspection bypass list, will give this error and there is no workaround except for turning SSL inspection off for that policy. I have created a ticket with Fortinet and will update as we work through it.

    gsarica
    gsaricaAuthor
    New Member
    November 28, 2016

    Also have an update. We have a test policy in place with only a few users in it for deep inspection testing as I said above. I turned off that policy so that everyone is going through the standard certificate inspection now and no one has complained about this error since.

     

    I've never seen an instance when one policy would bleed into another but it seems that was the case here somehow. With the policy turned on, even people not in the test group saw the Chrome error, with the policy off everyone seems to be ok.

    Terms & ConditionsAccessibility statement