-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid URL #36
Comments
Thanks for filling this issue and sorry you are running into this Please can you provide a screenshot of the problem |
I don't have the admin rights for this JupyterHub. On older versions i could connect, only on the newer version it was not possible. |
Please can you share a screenshot of the problem |
Thanks for the screenshots. The second error is basically a message suggesting you use the new extension
How to get to the output?
|
11:44:51.853 [error] Error sending request to https://jhub-highmem-start.apps.ocp4pbk.versatel.local/user/hub/api FetchError: request to https://jhub-highmem-start.apps.ocp4pbk.testment.local/user/hub/api failed, reason: unable to get issuer certificate |
@snami100 Thanks for the logs and the screenshots. I've got a PR that would prompt the user to allow using such un'trusted certificates (but this is not recommended). |
Please can you
If it works great, you can keep using this. |
I am still seeing the "unable to get issuer certificate" error in |
I am facing similar issue. My company uses a custom CA to issue certificates, that's the cause of the error. Version
|
@DonJayamanne I found out my problem was in the reverse proxy (httpd) config. It needed the |
@DonJayamanne I have a similar problem, I have the jupyter.allowUnauthorizedRemoteConnection: true (and the pre-release version of JupyterHub and Jupyter) and I accept the popups saying it is a self signed certificate, but a Invalid Url always appear. `10:56:03.239 [error] Error sending request to https://HOSTNAME:9443/hub/api FetchError: request to https://HOSTNAME:9443/hub/api failed, reason: self signed certificate 10:56:04.801 [error] Failed to determine base url for https://HOSTNAME:9443/user/USER/?token=TOKEN Error: Unable to determine base url of Jupyter Hub Server |
@Straboxer are you using vscode.dev or the like (i.e. are you using VS Code from within the browser)? |
Hey @DonJayamanne I am using VS Code native app for Mac M1. |
Hi @DonJayamanne , thanks for the great extension
Environment data
|
Please open the dev tools using the command
|
Hello @DonJayamanne , |
|
we are using
I tried and it didn't help 😞 |
Hello @DonJayamanne, I'm facing what seems like the same issue. I'm using Docker/Jupyterhub, attempting to connect to the server via my IP address with a SSL. Opening the running server in my browser via the address (https://10.XXX.X.XX:8000) redirects me to login as it should, but connecting through VS Code gives an invalid jupyterhub url. The log message is the same as well - [error] Failed to determine base url for https://10.XXX.X.XX:8000 Error: Unable to determine base url of Jupyter Hub Server. It does, however, work when loading through https://localhost:8000 instead of through the IP address. I just need others to be able to connect, hence why I need it to work via my IP address instead. I've attempted all the troubleshooting you described above, with the same outputs as @cchen777. Any help is appreciated! VS Code 1.87.2 |
Same issue : "Invalid JupyterHub URL specified" VSCode : 1.87.2 JupyterHub :
URL in kernel selection : For the record I have a working configuration for an air-gapped network (with private CA and different versions of almost everything). |
@lateo-net @cchen777 @snami100
|
@DonJayamanne Also tried to uninstall JupyterHub extension then install the insiders vsix and restart VSCode, no luck, same result. From console dev tools while "create new notebook" :
No Console event while validating the URL of the JupyterHub server. |
Here is the jupyterhub output for me:
|
I was able to fix my issue using the following steps: add env var NODE_TLS_REJECT_UNAUTHORIZED=0 Then faced an authentication issue (in spite of using the dummy authenticator). Fixed by having the user log in through the browser. After that, their username/pw combo was accepted by VS code. |
add env var NODE_TLS_REJECT_UNAUTHORIZED=0 Where to set this?command line? |
Unable to determine base url of Jupyter Hub Server
|
In your .bashrc The solution of @kaigg96 worked for me |
Still getting |
thank you bro. This solution worked for me |
I'm connecting from a Windows machine. Where am I supposed to find it? Is it ok to create it in a notebook session via |
i think you just set the variable through cmd like set NODE_TLS_REJECT_UNAUTHORIZED=0 |
Any progress on this issue? I can easily connect via pycharm jupyter connection but cant do the same with vscode. I get only |
Please can you
ms-toolsai-jupyter-hub-insiders.vsix.zip Screenshot for enabling logging To get to the logs, please open the bottom output panel (use the command |
Ive done every step from your instruction. Here is the output: I have tried several urls:
Using the same url i can connect to the jupyterhub in Pycharm via 'Add jupyter connection' feature |
Let me know if that works, and I'll try to update the code to try and strip that out. Also, can you share the rest of the logs, not just the error. |
Hello! @DonJayamanne Thank you for your fast feedback. When i type https://jupyter.{domain.tld}/hub/api i get What else can i provide in order to give you full details on this issue |
For context: my URL is not starting with https://jupyter.{domain.tld}/... but rather https://ml-jupyterhub.{domain.tld}/ |
Thank U so much! |
I have the same problem, but the solution above doesn't work for me。My jupyterhub version is 1.0.0, and I don't have the right to upgrade it |
Environment data
Expected behaviour
Should connect to JupyterHub
Actual behaviour
Doesnt connect, says invalid URL, when using 'Existing JupyterHub Server...'
My URL looks like this:
https://aubf-hig-start.apps.ocp4pbk.kernel.local/user/{username}?token={token}
When im using 'Existing Jupyter Server...' it says, use 'Existings JupyterHub Server...'...
The text was updated successfully, but these errors were encountered: