Gesis hub blocks Dask dashboard?

With https://gesis.mybinder.org/v2/gh/dask/dask-examples/master?urlpath=lab, the dask labview plugin does not work and the direct link to the dask dashboard returns a Gesis login screen.

Does this happen for other BinderHubs that serve mybinder.org as well?

This only happens with the Gesis hub. But I think I’ve found what’s wrong here.

While the other hubs serve under https://binder.example.com/user/${JUPYTERHUB_USER}/lab, Gesis goes for https://notebooks.gesis.org/binder/jupyter/user/${JUPYTERHUB_USER}/lab. And the Dask examples binder repo is configured assuming jupyter_server_proxy is at /user/${JUPYTERHUB_USER}/proxy/.

4 Likes

ah - maybe @arnim or @bitnik would want to know about this.

So I guess the issue is that there’s a hard-coded assumption in the dask example repo, moreso than an error in how GESIS is configured, yeah? That said, we should probably encourage some standardization of the URL structure for the federation BinderHubs

2 Likes

Thank you - have seen the report by @willirath :wink:

1 Like

That said, we should probably encourage some standardization of the URL structure for the federation BinderHubs

Not sure about this. Turns out that there’s an env variable for this: $JUPYTERHUB_BASE_URL

2 Likes