code-server failing to start. Code exited Error 127

Hi All,

I’ve been following this instruction from Digital Ocean how to set up a code-server in a droplet.

Everytime I start the service, it would be failing to start.

The version I downloaded is 3.1.0 from the latest build of code-server.

Any advice is appreciated.


I was stuck with this same error yesterday. It seems that Netlify did not like seeing both package-lock.json and yarn.lock files. I’ve been using npm as my package manager, so I deleted yarn.lock and my builds started to work again.

I would also suggest deleting node_modules, package-lock.json, and doing a fresh npm install, just to be thorough.

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi @xaykogeki,

This is because you use a 3.x.x version of Code-Server

Take a look at the release note of the 3.0 version here : « Code-server files are no longer packed into a single binary » (binary you try to copy from the code-server DL folder to /usr/local/bin when you follow the tutorial)

You have to move the whole folder or use a 2.x.x. version of Code-Server (2.1698 is the last one which is working with the tutorial)

I reported it so the tutorial could be updated

✌️ Nemrix

Hi @xaykogeki,

Unfortunately, there could be a variety of errors which we won’t be able to forsee. Having said that, can you confirm the errors that get logged on your droplet?

There are a few ways you can do that. The first and easiest would be to check the journalctl. When you try and start/restart your code-server and it fails, the error will be immediately logged in the journalctl. You can see it by doing

journalctl -xe 

Once you have the error, provide it here so that we can have some idea where to start troubleshooting.

Regards, KDSys