ERR_SSL_PROTOCOL_ERROR on Google Chrome

Author
sforbus@atljewishacademy.org
New Member
  • Total Posts : 1
  • Scores: 0
  • Reward points: 0
  • Joined: 2019/08/08 10:48:00
  • Status: offline
2019/08/13 08:40:20 (permalink)
0

ERR_SSL_PROTOCOL_ERROR on Google Chrome

We are having a bizarre problem since updating to 6.2.1 (we updated due to a memory leak issue in 6.2.0).
 
Certain sites are giving us a ERR_SSL_PROTOCOL_ERROR only in Google Chrome. I have tried all the usual troubleshooting for this error, but the only thing that fixes it is restarting the fortigate. Two sites (facebook.com and login.renweb.com) both use TLS 1.3, but we can get to facebook without a problem and we cannot get to the other site. After rebooting the device, it works for several days and then starts behaving poorly again.
 
Other browsers work fine, including Internet Explorer, Edge (not Chromium based) and Firefox.
 
I have attempted to disable SSL certificate inspection, but that does not seem to affect the problem one way or another. I also tried putting the fortigate back on its factory certificate.
 
My next step will be to revert to 6.0 branch, where I did not experience this issue, but I figured I would post first to see if anyone had similar experiences.
 
#1

0 Replies Related Threads

    Jump to:
    © 2019 APG vNext Commercial Version 5.5