[Bug]: Problem opening .ipynb files (Jupyter Notebook)

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Microsoft Edge / Chrome / Firefox / Vivaldi / Safari
• Local OS: Windows 10.0.19044.1826 / macOS Big Sur 11.6.8
• Remote OS: Raspberry Pi OS Lite (64-bit) 2022-04-04 (Kernel: 5.15 | Debian: 11 ‘bullseye’)
• Remote Architecture: arm64
• code-server --version: 4.5.2

Steps to Reproduce

1. open code-server
2. try to open .ipynb file
3. trying to create an .ipynb file

Expected

The file should open and be viewable

Actual

Code-server keeps trying to open the file, or creating the file, never finishes loading on screen.

Logs

No response

Screenshot/Video

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

[c-dasq]

Hi all, I was able to simulate almost all possible cases in an orderly manner, and I was unable to replicate the problem:

• Web Browser: Firefox / Chrome / Chromium-based spinoffs
• Remote OS: Raspberry Pi OS Lite / Ubuntu Server / Containers
• Local OS: Windows 10 / Windows 11 / MacOs / iPadOs/ Ubuntu / Raspberry Pi Desktop / Android

It didn’t really work well in only two cases:

• Firefox on Android 9 (sorry, I don’t have a newer version)
• LXC Ubuntu Server container (I’m sure it’s a ProxMox problem)

I suspect that when I generated the report for this bug, I had left the bind-addr setting at 0.0.0.0:8080, I didn’t realize that port forwarding via SSH wasn’t working (I use tmux); or I don’t know if I made some other mistake.

I want to thank you all for the support, and if no one has any more comments, I will close this case.

Thank you very much,

[code-asher]

There is supposed to be a popup warning on startup when using insecure contexts saying that certain functionality will not work because the browser does not allow them but we should instead make that popup appear at the point of trying to perform an action so it is more obvious why a certain feature is not working. So instead we would make it show every time a web view fails to open, when paste fails, and other things that will fail due to insecure contexts. In the specific case of web views it might be best to show that message right in the web view instead of a popup.

Also we should change the error message in the console to specifically say whether an insecure context is the problem instead of just “can’t compute”.