Repository navigation
1.408 doesn't work with --cert args #378
Description
code-serverversion:1.408-vsc1.32.0- OS Version: Ubuntu Server 18.04 LTS (VM on Hyper-V)
Description
Trying to run code-server with --cert and --cert-key arguments causes application to exit issuing error EEXIST: file already exists, mkdir '<cert-path>'.
Steps to Reproduce
- Acquire certificates for HTTPS operation
- Try to run code-server with certificates, e.g.
./code-server --cert fullchain.pem --cert-key privkey.pem
Error shown
Below is a complete example of the error I am getting when running code-server following above steps:
lucas@u1804-coder:~/code-server1.408-vsc1.32.0-linux-x64$ ./code-server --cert fullchain.pem --cert-key privkey.pem
ERROR { Error: EEXIST: file already exists, mkdir '/home/lucas/code-server1.408-vsc1.32.0-linux-x64/fullchain.pem'
[stack]: 'Error: EEXIST: file already exists, mkdir \'/home/lucas/code-server1.408-vsc1.32.0-linux-x64/fullchain.pem\'',
[message]: 'EEXIST: file already exists, mkdir \'/home/lucas/code-server1.408-vsc1.32.0-linux-x64/fullchain.pem\'',
errno: -17,
code: 'EEXIST',
syscall: 'mkdir',
path: '/home/lucas/code-server1.408-vsc1.32.0-linux-x64/fullchain.pem' }
free(): invalid pointer
Aborted (core dumped)
Previous versions
This error does not happen on previous code-server version 1.32.0-310.
Activity
kylecarbs commentedon Mar 29, 2019
Will fix. Thanks for the report!
mcp352 commentedon Mar 29, 2019
Exact same issue. Is there an easy workaround? Thanks for posting Mentz.
mentz commentedon Mar 29, 2019
The "workaround" I'm using is reverting to version
1.32.0-310.kmahyyg commentedon Mar 31, 2019
same issue as #351
mentz commentedon Mar 31, 2019
Sorry, I didn't think it was a duplicate. Seeing that it's a different error I thought it would be better to open a new issue for this one.
kirintwn commentedon Apr 1, 2019
Got exact same error too, another workaround for now might be using reverse proxy like nginx to perform ssl transmission.
code-asher commentedon Apr 1, 2019
Did some testing and it looks like what fixed #351 also fixed this one (that fix hasn't been released yet though). The different arguments caused a different error message, but the root cause was the same.
XiaolongMeng commentedon Apr 4, 2019
same error, waiting to be fixed
kylecarbs commentedon Apr 4, 2019
Fixed with the latest release!