Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Bug]: cannot connect remotely to jupyterhub #6193

Closed
3 of 4 tasks
BouarfaMahi opened this issue May 7, 2023 · 5 comments
Closed
3 of 4 tasks

[Bug]: cannot connect remotely to jupyterhub #6193

BouarfaMahi opened this issue May 7, 2023 · 5 comments
Labels
bug Something isn't working triage This issue needs to be triaged by a maintainer

Comments

@BouarfaMahi
Copy link

BouarfaMahi commented May 7, 2023

Is there an existing issue for this?

  • I have searched the existing issues

OS/Web Information

  • Web Browser: Brave
  • Local OS: Ubuntu Server 22.04 with code server in a docker container.
  • Remote OS: Ubuntu Server 22.04 with JupyterHub
  • Remote Architecture: x86_64
  • code-server --version:code-server: v4.12.0

Steps to Reproduce

  1. install jupyter extension
  2. open a jupyter notebook
  3. insert the remote server url
  4. https:///user//?token=

Expected

an established connection to the remote jupyterhub environment and viewing the notebook.

Actual

no connection in this configuration, cannot view the notebook.
the connection is established when using VSCode desktop on windows.

Logs

No response

Screenshot/Video

No response

Does this issue happen in VS Code or GitHub Codespaces?

  • I cannot reproduce this in VS Code.
  • I cannot reproduce this in GitHub Codespaces.

Are you accessing code-server over HTTPS?

  • I am using HTTPS.

Notes

No response

@BouarfaMahi BouarfaMahi added bug Something isn't working triage This issue needs to be triaged by a maintainer labels May 7, 2023
@BouarfaMahi BouarfaMahi changed the title [Bug]: [Bug]: cannot connect remotely to jupyterhub May 7, 2023
@code-asher
Copy link
Member

code-asher commented May 8, 2023 via email

@BouarfaMahi
Copy link
Author

let me check in a deep level.

@thevedicdeveloper
Copy link

thevedicdeveloper commented May 18, 2023

Opened bug for it --> #6220

Is there an existing issue for this?

  • I have searched the existing issues

OS/Web Information

  • Web Browser: firefox, edge, google chrome
  • Local OS: macos
  • Remote OS: ubuntu-server
  • Remote Architecture: arm64
  • code-server --version:latest

Steps to Reproduce

  1. Open Visual Studio Code on one machine.
  2. Create or open a file in the editor.
  3. Save the file.
  4. Access the same file from a different machine using a network or cloud storage.
  5. Attempt to view the file content.

Expected

I should be able to view the content of the .ipynb file from a different machine, when I accessed the vscode container using the IP address of the machine which is running the vs code container.

Actual

I am able to see the vscode when accessed over the network, but is not able to view the content of the file.

Although I can see the cells in the outline section of the vscode (bottom left)

  • When accessing the vscode from the machine which is running the vscode container --> able to see the content of the file.
    Screenshot 2023-05-18 at 12 21 11 PM

  • when accessing the vscode from a different machine using ip address of the machine which is running the vscode container. ---> the file content is not visible on the editor, but we can see the content in the left side of the outline pannel
    Screenshot 2023-05-18 at 12 21 59 PM

Logs

No response

Screenshot/Video

No response

Does this issue happen in VS Code or GitHub Codespaces?

  • I cannot reproduce this in VS Code.
  • I cannot reproduce this in GitHub Codespaces.

Are you accessing code-server over HTTPS?

  • I am using HTTPS.

Notes

I have not tried in VS CODE and GitHub Codespaces.

Please let me know if I need to provide any other information

@benz0li
Copy link
Contributor

benz0li commented May 19, 2023

You are not using HTTPS. This is required for Jupyter notebooks.
ℹ️ Fully qualified domain name (FQDN) required, too. TLS for an IP is not sufficient.

HTTP only works for 127.0.0.1 / localhost.

Cross reference: #5475 (comment)

@BouarfaMahi
Copy link
Author

@benz0li Many thanks it works.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working triage This issue needs to be triaged by a maintainer
Projects
None yet
Development

No branches or pull requests

4 participants