how to run code server in https

[sanjayme97]

if we run "docker run -d -p 8080:8080 sanjayme/vscode-dotnet-core --auth none --cert" still we are facing not secure connection how to solve this. even we tried something similar to "docker -v /path/to/certs.crt:/home/coder/cert.crt -v /path/to/cert-key.key:/home/coder/cert.key -p 8080:8080 run codercom/code-server:v2 --cert /home/coder/cert.crt --cert-key /home/coder/cert.key" @code-asher kindly help here.
http url is working but if we browse https dns mapped url its throwing error. check the attachment for error

[mahmoudajawad]

I would suggest you run code-server as it's on separate container, then run a nginx reverse-proxy container pointing at code-server port. That allows to manage your reverse-proxy without the need to reset/restart/rebuild your code-server container. This can be easily achieved with docker-compose with both code-server and nginx as services in one compose config.

[code-asher]

I ran your image but it worked for me. What version of Chrome are you running? I'm on 80. I wonder if there was a recent change that makes self-signed certificates not work for websockets.

What I did was run docker run -d -p 8080:8080 sanjayme/vscode-dotnet-core --auth none --cert then browsed to https://localhost:8080.

[sanjayme97]

@code-asher I am on version 81 . is there any other way than self-signed certificates to run it in https in server with ssl certi?

[sanjayme97]

@code-asher if I run "docker run -d -p 8080:8080 sanjayme/vscode-dotnet-core --auth none --cert" i also can browse https://8080 but not secure

and below error is when we browse dns url(attached port to domain name) with ssl attached

[code-asher]

Ah that's interesting. Are you using some kind of reverse proxy? The websocket connection is returning a 200 which is unusual.

[necmettin]

I have a similar setup, tried nginx reverse proxy but couldn't get code-server to accept the domain name no matter what I did. (I use cloudflare and keep the origin server non-https). So I switched to a self-signed certificate on non-80 port.

Long story short, Chrome 81 does not let you pass self-signed certificates. Firefox does. code-server wasn't running on Chrome but when I switched to Firefox, no problems.

[cmoog]

Thanks for the investigation @necmettin! We're aware that documentation surrounding https is lacking. #1628 aims to fix this.

Closing this due to inactivity.