# OOD and Dask Labextension
**URL:** https://discourse.openondemand.org/t/ood-and-dask-labextension/1317
**Category:** Get Help
**Created:** [February 11, 2021, 5:01am UTC](https://discourse.openondemand.org/t/ood-and-dask-labextension/1317 "2021-02-11T05:01:35Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@David.Monro](https://discourse.openondemand.org/u/David.Monro)
#### Post date: [February 11, 2021, 5:01am UTC](https://discourse.openondemand.org/t/ood-and-dask-labextension/1317/1 "2021-02-11T05:01:35Z")
I’m trying to use the combination of OOD, jupyterlab, and dask-jobqueue, which I’m sure must be a fairly common scenario here 🙂
It is pretty much working - except for the Dask Labextension. The extension itself works fine; if I start the jupterlab instance manually on the login node (with appropriate ssh port forwards) everything is just dandy.
However, through OOD it doesn’t work.
If I put the following into the Labextension search bar:
https://[OOD-web-server]/node/[nodename]/[port]/proxy/8787/status
then it seems to at least actually find the cluster (all the buttons light up orange instead of grey) but launching any of the tabs from the extension just gives me blank pages.
I notice that in my browser network traffic it is doing some sort of web services request?
wss://[OOD-web-server]/node/[nodename]/[port]/proxy/8787/individual-progress/ws
and getting back a 403 forbidden, which I assume is part of the issue here.
Anybody got this to work?
Cheers
David
---
### Author:  [@David.Monro](https://discourse.openondemand.org/u/David.Monro)
#### Post date: [February 12, 2021, 1:30am UTC](https://discourse.openondemand.org/t/ood-and-dask-labextension/1317/2 "2021-02-12T01:30:21Z")
Found a little more info - it seems that the request is making it all the way through to the jupyterlab instance, since I’m seeing this in the jupyterlab output:
403 GET /node/rei-n1/4367/proxy/8787/individual-progress/ws (10.0.16.254) 1.72ms referer=None
so I’m not sure if this is an OOD problem or a jupyterlab issue at this point.
---
### Author:  [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [February 12, 2021, 3:13pm UTC](https://discourse.openondemand.org/t/ood-and-dask-labextension/1317/3 "2021-02-12T15:13:53Z")
I think you’re on the right track, though I don’t know much about this extension.
Here’s an issue from them itself, looks like there’s a setting `'allow_websocket_origin': ['*']` you may need (to set to either \* or the ondemand host).
>
>
> This is a replica of #129 (sorry couldn't see an option to re-open), apologies I didn't reply at that point.
> We have...
I also found this which may or may not help.
>
>
> Is there a way to get dask-labextension to autodetect a jupyter-server-proxy URL like proxy/8787 instead of the cluster's dashboard URL?
> I'm running...
---
### Author:  [@David.Monro](https://discourse.openondemand.org/u/David.Monro)
#### Post date: [February 15, 2021, 6:53am UTC](https://discourse.openondemand.org/t/ood-and-dask-labextension/1317/4 "2021-02-15T06:53:17Z")
After a couple of days adding random print statements all over jupyter code, I’m fairly sure this is actually a jupyter issue; I think it isn’t checking the allow\_websocket\_origin setting in the jupyter\_server\_proxy code, so I’ve raised an issue (I’ve actually raised it against the extension at the moment since I don’t know enough about jupyter to know which level the check should be implemented in).
Thanks for your help!
---
### Author:  [@system](https://discourse.openondemand.org/u/system)
#### Post date: [March 14, 2022, 6:01pm UTC](https://discourse.openondemand.org/t/ood-and-dask-labextension/1317/5 "2022-03-14T18:01:00Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.