Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Jupyterlab's responses "400 Bad Request" in version 2.6.0 #11672

Closed as not planned
@madhosoi

Description

@madhosoi

After upgrade of Coder OSS to version 2.6.0, we are experiencing these errors accessing to any feature related to websockets (I suppose) of jupyterlab instantiated in a given template running on Kubernetes:

image

With previous version, it is running as expected.

I have this setup:

/opt/miniconda/bin/python3.11 /opt/miniconda/bin/jupyter-lab --no-browser --ServerApp.password= 
--ServerApp.token= --JupyterApp.config_file=~/.jupyter/jupyter_notebook_config.py 
--ServerApp.port=8888 --ServerApp.base_url=@<user>/<workspace>.main/apps/jupyter --ip='*'
# jupyter
resource "coder_app" "jupyter" {
  count        = local.jupyter-count
  agent_id     = coder_agent.main.id
  display_name = "Jupyter Lab"
  slug         = "jupyter"
  icon         = "/icon/jupyter.svg"
  url          = "http://localhost:8888/@${lower(data.coder_workspace.me.owner)}/${lower(data.coder_workspace.me.name)}.main/apps/jupyter/"
  subdomain    = false
  share        = "owner"
}

I cannot see any clue in the logs of coder, of the proper workspace's container neither in the jupyterlab logs (running it manually to get them).

Could you help me to understand the error?
If you need more info, just ask me.
Thanks

Miguel

Metadata

Metadata

Assignees

No one assigned

    Labels

    need-helpAssign this label prompts an engineer to check the issue. Only humans may set this.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions