Articles in this section

HTTP/2 web sockets connections cause Chrome to crash

Diana Pai
  • Updated
Follow

Known issue upgrading to 4.6.4 or 5.0.2

During a recent investigation, we found that something in a user's network did not cooperate with browsers going directly to Domino 5.0 k8s via DNS RR with HTTP/2 enabled, leading to Chrome exhausting its socket pool. Disabling HTTP/2 fixed the issue (using HTTP 1.1 instead). 

  • Symptom:
    Domino UI slowness, UI hangs, Chromium-based browsers crash

  • Resolution:
    Edit the nginx-ingress-controller configmap to set use-http2 to false

Related articles

Comments

0 comments

Please sign in to leave a comment.