From c902a7d1737d5214eaa86b6ae234fe91f6c907f8 Mon Sep 17 00:00:00 2001 From: Pavithra Eswaramoorthy Date: Sat, 19 Aug 2023 00:12:11 +0530 Subject: [PATCH 1/2] =?UTF-8?q?=F0=9F=93=9D=20Note=20a=20Dask=20Gateway=20?= =?UTF-8?q?related=20error?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/docs/troubleshooting.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/docs/troubleshooting.mdx b/docs/docs/troubleshooting.mdx index a26e9ed3e..ad0e8f751 100644 --- a/docs/docs/troubleshooting.mdx +++ b/docs/docs/troubleshooting.mdx @@ -102,6 +102,17 @@ At this point, feel free to cancel the deployment and rerun the same deployment If you are interested in learning more about DNS, [this "How DNS works comic" by dnsimple](https://howdns.works/) is a great resource to get started. +### New Dask Gateway clusters lead to `500 Internal Server Error` + +This may occur when `dask-gateway-controller` has some internal authentication issues. To resolve this, you can restart `nebari-daskgateway-controller` and `nebari-daskgateway-controller` pods: + +- Open `k9s` (Learn more about `k9s` in [Debug Nebari deployment](./how-tos/debug-nebari#debugging-the-kubernetes-cluster-using-k9s)) +- Press the / key and search for "daskgateway" +- Use the arrow keys to highlight each pod +- Delete highlighted pods with ctrl + d, and the pods should restart automatically + +It's also worth verifying that all API resources are up to date for your Nebari deployment. + ## How do I...? ### Get the Kubernetes context From e0b79331691abee2e41200e7028a6b4aa7a17577 Mon Sep 17 00:00:00 2001 From: Pavithra Eswaramoorthy Date: Fri, 15 Sep 2023 02:25:57 +0530 Subject: [PATCH 2/2] Update docs/docs/troubleshooting.mdx --- docs/docs/troubleshooting.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/docs/troubleshooting.mdx b/docs/docs/troubleshooting.mdx index ad0e8f751..da2e2a6b4 100644 --- a/docs/docs/troubleshooting.mdx +++ b/docs/docs/troubleshooting.mdx @@ -111,7 +111,6 @@ This may occur when `dask-gateway-controller` has some internal authentication i - Use the arrow keys to highlight each pod - Delete highlighted pods with ctrl + d, and the pods should restart automatically -It's also worth verifying that all API resources are up to date for your Nebari deployment. ## How do I...?