search

microsoft / vscode-jupyter-hub

Jupyter Hub Support in VS Code
https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter-hub
MIT License
9 stars 7 forks source link

Can't connect to jupyterhub with self signed certificate #58

Open nikita-dev-null opened 5 months ago

nikita-dev-null commented 5 months ago

Environment data

Expected behaviour

connect to jupyterhub

Actual behaviour

Can't connect to jupyterhub

Steps to reproduce:

  1. update from 2023.10.1003492320 to 2024.4.1001491100
  2. try connect to jupyterhub with self signed certificate

Logs

[warn] Could not fetch kernels from the remote server, falling back to cache: Error: request to https://jupyterhub.xxx/hub/api/authorizations/token failed, reason: unable to verify the first certificate

I added the certificate to the OS CA, but it didn't help downgrade to 2023.10.1003492320 resolve this problem

steve-offutt commented 2 months ago

We are experiencing similar behavior from a Windows client.

10:10:59.448 [error] Error sending request to https://hostname.example.com/hub/api FetchError: request to https://hostname.example.com/hub/api failed, reason: unable to verify the first certificate
    > at ClientRequest.<anonymous> (c:\Users\user_name\.vscode\extensions\ms-toolsai.jupyter-hub-2023.10.1003012305\dist\extension.node.js:63581:18)
    > type = system
    > errno = UNABLE_TO_VERIFY_LEAF_SIGNATURE
    > code = UNABLE_TO_VERIFY_LEAF_SIGNATURE

Interestingly connecting to JupyterHub from a MacOS client works fine.

On the Windows client I have the following settings set based on other related suggestions found in this repos issue tracker:

"jupyter.allowUnauthorizedRemoteConnection": true,
"http.systemCertificates": true,
"http.experimental.systemCertificatesV2": true,
"http.proxyStrictSSL": true,
"http.proxySupport": "override",

We experience the same behavior from both the Pre-Release and Release versions of the extension.

Release Version: v2023.10.1003012305
PreRelease Version: v2024.5.1002140811

Our company certificates are installed on both the client machines (MacOS and Windows). Any help on this issue would be greatly appreciated!