James Collinson

Update: I have subsequently tried changing the proxy location to be `/` (i.e. no URL suffix), and updated the dask-gateway deployment and Ingress path accordingly. Even in this case, I...

Thanks for the reply @rigzba21 - I think it sounds like the issue I'm seeing is related to this, but I'm now seeing the "Failed to watch ..." errors you...

Thanks both for your help! I've done as @martindurant suggested and re-created the Traefik CRDs, and this resolves the `Failed to watch` errors I was seeing in Traefik, but I...

It may be worth mentioning issue: https://github.com/dask/dask-gateway/issues/246 since there is some discussion of timeout errors with the `get_client` method there. Having tried the suggestion in that issue: ``` cluster =...

Thanks @rigzba21 - much appreciated. We have a separate proxy machine natively running NGINX that listens for `https` traffic, and then routes using `http` to the head node of the...

Hi @martindurant - not explicitly; so this sounds like something I should explore further. I'm guessing if this isn't specifically done by NGINX I'll need to set this up for...

Thanks both for the help - this does sound plausible if it's only the `gateway://` traffic that's getting stuck. I'll look into it as soon as possible, but this was...

It took me a while to get back to this. As @martindurant and @rigzba21 suggested, the problem I was seeing was a result of the `gateway://` TCP traffic getting stuck...

Good idea @consideRatio, I've modified the title though let me know if you can think of a way to make it even clearer. From my side I'm happy for the...

Just adding one additional comment to this, since this issue can also emerge due to blocked TCP traffic intra-cluster, depending on the CNI used. In our case, on an old...