[Bug]: Markdown preview not working with self signed certificate (SecurityError)

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chrome Version 106.0.5249.119 (Offizieller Build) (64-Bit)
• Local OS: Windows 10 21H1
• Remote OS: Debian 11
• Remote Architecture: amd64
• code-server --version: 4.7.0

Steps to Reproduce

1. start code-server with cert: true in config.json https://coder.com/docs/code-server/latest/guide#using-a-self-signed-certificate
2. open code-server with https://IP:PORT
3. accept self signed certificate
4. open or create a *.md file
5. Hit the preview button on the top right

Expected

The preview of the Markdown document should be shown.

Actual

The preview windows remains empty.

Logs

code-server --verbose Nothing that is related to this error/bug.

Code-Server Webview

Error loading webview: Error: Could not register service workers: SecurityError: Failed to register a ServiceWorker for scope ('https://192.168.107.129:8080/stable-784b0177c56c607789f9638da7b6bf3230d47a8c/static/out/vs/workbench/contrib/webview/browser/pre/') with script ('https://192.168.107.129:8080/stable-784b0177c56c607789f9638da7b6bf3230d47a8c/static/out/vs/workbench/contrib/webview/browser/pre/service-worker.js?v=4&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&remoteAuthority=192.168.107.129:8080'): An SSL certificate error occurred when fetching the script..

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

This happens only on my local deployment with the self signed certificate. My external deployment with a lets encrypt certificate does work as expected.

[jneuhauser]

Thank you very much… I’ve defined http://192.168.107.129:8080 as secure origin in chrome://flags/#unsafely-treat-insecure-origin-as-secure and it works. 😃 Using the auto generated self signed cert (cert: true) and defining https://192.168.107.129:8080 (https Instead of http) does not work.

So to sum up what makes service workers work is:

• Using code-server with a trusted certificate
  • Use Let’s Enrcrypt in combination with:
    • A reverse rroxy https://github.com/coder/code-server/blob/main/docs/guide.md#using-lets-encrypt-with-nginx https://github.com/coder/code-server/blob/main/docs/guide.md#using-lets-encrypt-with-caddy https://github.com/coder/code-server/issues/4723#issuecomment-1119340126
    • Direct with code-server --cert /path/to/cert.crt --cert-key /path/to/key.pem
  • Use https://mkcert.dev/ for trusted self signed certs
• Using code-server over localhost / 127.0.0.1
  • Run code-server on the same host or as Docker container and connect over localhost / 127.0.0.1
  • Use SSH forwarding to make a remote code-server available over localhost / 127.0.0.1 https://github.com/coder/code-server/blob/main/docs/guide.md#port-forwarding-via-ssh
• Define your HTTP-URL (example: http://192.168.107.129:8080) as secure origin. HTTPS-URLs may not work!
  • Chrome Browser: chrome://flags/#unsafely-treat-insecure-origin-as-secure
  • Firefox Browser: ???
  • …

Can/Should we close this issue or should i leave it open till anyone updates the documentation?

[code-asher]

In the docs we recommend mkcert. Wonder if we can deprecate code-server’s built-in certificate generator for that or at least add a warning to the output.