You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment: WebSocket server (Mega running on DigitalOcean Kubernetes behind a DO LoadBalancer
Cloud provider or hardware configuration: 2 GB Memory / 50 GB Disk + 23 GB / NYC3 - Debian do-kube-1.16.6-do.2
OS (e.g. from /etc/os-release): Debian
Kernel (e.g. uname -a): Darwin Williams-MacBook-Pro.local 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64 (development)
What happened:
The WebSocket was closed with code 1006 after 100 seconds
What you expected to happen:
The WebSocket connection would stay open for longer than 100s
How to reproduce it:
Create a DigitalOcean cluster behind a DigitalOcean LoadBalancer (also behind Cloudflare proxy) and deploy a WebSocket server (specifically Mega) with the following Ingress config:
Anything else we need to know:
Initially connections were timing out after 60s. This wasn't fixed by adding nginx.ingress.kubernetes.io/proxy-read-timeout and nginx.ingress.kubernetes.io/proxy-send-timeout, but weirdly it was fixed via ingress.kubernetes.io/proxy-read-timeout, ingress.kubernetes.io/proxy-send-timeout and ingress.kubernetes.io/proxy-connect-timeout. After this, connections started being dropped due to WS code 1006 after 100 seconds.
I have port-forwarded the WebSocket server and connected to it locally without any connection drop issues, so I'm confident the issue resides in either the DigitalOcean LoadBalancer or in ingress-nginx.
/kind bug
The text was updated successfully, but these errors were encountered:
NGINX Ingress controller version: 0.32.0
Kubernetes version (use
kubectl version
): v1.16.6Environment: WebSocket server (Mega running on DigitalOcean Kubernetes behind a DO LoadBalancer
uname -a
):Darwin Williams-MacBook-Pro.local 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64
(development)kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-0.32.0/deploy/static/provider/do/deploy.yaml
What happened:
The WebSocket was closed with code 1006 after 100 seconds
What you expected to happen:
The WebSocket connection would stay open for longer than 100s
How to reproduce it:
Create a DigitalOcean cluster behind a DigitalOcean LoadBalancer (also behind Cloudflare proxy) and deploy a WebSocket server (specifically Mega) with the following Ingress config:
Anything else we need to know:
Initially connections were timing out after 60s. This wasn't fixed by adding
nginx.ingress.kubernetes.io/proxy-read-timeout
andnginx.ingress.kubernetes.io/proxy-send-timeout
, but weirdly it was fixed viaingress.kubernetes.io/proxy-read-timeout
,ingress.kubernetes.io/proxy-send-timeout
andingress.kubernetes.io/proxy-connect-timeout
. After this, connections started being dropped due to WS code 1006 after 100 seconds.I have port-forwarded the WebSocket server and connected to it locally without any connection drop issues, so I'm confident the issue resides in either the DigitalOcean LoadBalancer or in ingress-nginx.
/kind bug
The text was updated successfully, but these errors were encountered: