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
I installed the vanilla DaskHub Helm chart, and routed traffic via an NGINX reverse proxy with a dedicated location for the JupyterHub service, e.g. https://<our_dev_domain>/jupyterhub/.
This meant overriding that part of the values.yaml as follows:
Describe the issue:
I installed the vanilla DaskHub Helm chart, and routed traffic via an NGINX reverse proxy with a dedicated location for the JupyterHub service, e.g.
https://<our_dev_domain>/jupyterhub/
.This meant overriding that part of the
values.yaml
as follows:The JupyterHub service then all works as expected at that location. However, when calling the Dask Gateway service (which is configured as a service of JupyterHub via the custom configuration here: https://github.com/dask/helm-chart/blob/main/daskhub/values.yaml#L27), the service is not found.
Inspecting the JupyterHub proxy's logs we see (including previous line as reference):
I tried modifying the
extraConfig
passed to JupyterHub to manually specify the subdirectory in the URL to no avail.It could be that this is a broader issue which should be raised in the JupyterHub project - let me know if I should do this.
Environment:
The text was updated successfully, but these errors were encountered: