Bokeh applications hang when using a TLS-secured scheduler

Hi, we’ve been investigating using TLS encryption for securing schedulers running on our cluster. We’ve managed to get almost everything working (which is great!) apart from bokeh applications. When the scheduler starts up, part of what it tells me is this:

distributed.scheduler - INFO -   Scheduler at:   tls://10.0.0.83:33881
distributed.scheduler - INFO -       bokeh at:          10.0.0.83:8787

I can connect to the bokeh applications homepage at that address but if I try to navigate to one of the application pages (/status, say), it doesn’t connect and the browser tells me it’s “Waiting for 10.0.0.83...” Any ideas what’s causing this or how we could work around it?

Note: we’re using distributed v1.19.3, which I’m aware is not the latest release (and I haven’t tested the latest release for this behaviour).

[mrocklin]

I wonder if there are others at the Met Office that might be able to help? cc @niallrobinson @jacobtomlinson

[DPeterK]

Actually, further investigation of this has shown this to just be due to us using an older version of bokeh - it all works fine with the latest version of bokeh 👍 As such I don’t think there’s anything to do here so I’m going to go ahead and close this issue. Thanks @mrocklin for engaging with us on this.