Skip to content

Commit 8bee26b

Browse files
authored
Merge pull request #19009 from github/repo-sync
repo sync
2 parents b189807 + 1156682 commit 8bee26b

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,3 +94,9 @@ If {% data variables.product.product_location %} indicates that your session has
9494
- Configure your load balancer to operate on Layer 4, and use the PROXY protocol instead of `X-Forwarded-For` for passthrough of client IP addresses. For more information, see "[Enabling PROXY protocol support on {% data variables.product.product_location %} ](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)."
9595

9696
For more information, refer to the documentation for your load balancer.
97+
98+
### Live updates to issues and check runs not working
99+
100+
When {% data variables.product.product_location %} is accessed via a load balancer or reverse proxy, expected live updates, such as new comments on issues and changes in notification badges or check run output, may not display until the page is refreshed. This is most common when the reverse proxy or load balancer is running in a layer 7 mode or does not support the required [websocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) protocol.
101+
102+
To enable live updates, you may need to reconfigure the load balancer or proxy. For more information, refer to the documentation for your load balancer.

0 commit comments

Comments
 (0)