Operating System Debian

Cloud9 IDE Is Discontinued: Install code-server on Debian 13 Instead

The self-hosted Cloud9 SDK was archived in 2021. This guide sets up code-server, a maintained browser-based IDE, on Debian 13 with safe remote access.

Cloud9 was a browser-based IDE that you could host yourself by cloning the c9/core repository and starting a Node.js server. That is no longer an option, so this guide explains what happened to Cloud9 and then sets up a maintained replacement, code-server, on Debian 13 (trixie). The same steps work on Debian 12. At the end you will have an editor with a file tree and terminal that runs on your server and that you reach from a browser, either through an SSH tunnel or over HTTPS on your own domain.

What happened to Cloud9

  • The open-source Cloud9 SDK repository, c9/core, was archived by its owner on 6 April 2021. It is read-only and receives no fixes; its installer targets Node.js versions that are long out of support.
  • Cloud9 continued as a hosted service, AWS Cloud9. AWS documentation now states that AWS Cloud9 is no longer available to new customers; existing customers can keep using it.
  • Debian 7 (wheezy), the release many Cloud9 tutorials were written for, has been out of support for years.

code-server runs Visual Studio Code on a remote machine and serves it to a browser. It covers the same need as a self-hosted Cloud9: your code, tools and terminal stay on the server, and any device with a browser becomes a workstation. It is developed in the open by Coder and released under the MIT licence.

Requirements

  • A Debian 13 or Debian 12 server. The editor itself is light, but language servers and builds are not; 2 GB of RAM is a comfortable starting point.
  • A regular user with sudo rights. This guide uses deploy. Do not run the IDE as root: its built-in terminal gives whoever logs in a shell as the user the service runs as.
  • For HTTPS access: a domain such as code.example.com with a DNS record pointing to the server.

Install code-server

Log in as deploy and make sure curl is present:

sudo apt update
sudo apt install curl

The project's install script detects Debian and installs the latest .deb package. Run it with --dry-run first to see exactly what it will do, then run it for real:

curl -fsSL https://code-server.dev/install.sh | sh -s -- --dry-run
curl -fsSL https://code-server.dev/install.sh | sh

The package includes a systemd template unit, so each system user can have a separate instance. Enable and start one for your account:

sudo systemctl enable --now code-server@$USER

Check that it is running:

systemctl status code-server@$USER

Review the configuration

On first start code-server writes ~/.config/code-server/config.yaml:

bind-addr: 127.0.0.1:8080
auth: password
password: (a random string)
cert: false

Two things matter here. The server listens on the loopback address only, so it is not reachable from the internet yet, and it asks for the password stored in this file. Leave bind-addr as it is. Do not change it to 0.0.0.0 and open port 8080 in the firewall, as older Cloud9 tutorials did with their port: that would send the password and everything you type over plain HTTP.

To set your own password, edit the password line and restart the service:

nano ~/.config/code-server/config.yaml
sudo systemctl restart code-server@$USER

Option 1: connect through an SSH tunnel

For a single developer this is the simplest and safest way to reach the IDE, because nothing new is exposed. On your own computer, forward local port 8080 to the server:

ssh -N -L 8080:127.0.0.1:8080 deploy@203.0.113.10

Leave that command running and open http://127.0.0.1:8080 in your browser. Enter the password from config.yaml.

Option 2: HTTPS on your own domain with Caddy

To work from a tablet or any machine without an SSH client, put a reverse proxy with a real certificate in front of code-server. Caddy obtains and renews a Let's Encrypt certificate by itself and is packaged in Debian:

sudo apt install caddy

Replace the contents of /etc/caddy/Caddyfile with:

code.example.com {
  reverse_proxy 127.0.0.1:8080
}

Reload Caddy:

sudo systemctl reload caddy

Ports 80 and 443 must be reachable from the internet for the certificate to be issued, so allow them in your firewall (with ufw: sudo ufw allow 80,443/tcp) and in any firewall your hosting control panel provides. Then open https://code.example.com. Because the login page is now public, use a long, unique password.

Open a project

Use File → Open Folder in the editor, or put the folder in the address: https://code.example.com/?folder=/home/deploy/project. code-server reopens the last folder on the next visit. The integrated terminal (Terminal → New Terminal) runs as deploy on the server, so git, compilers and package managers behave exactly as they do over SSH.

Keep it updated

code-server is not in Debian's repositories, so apt upgrade does not update it. Re-run the install script to move to the newest release, then restart the service:

curl -fsSL https://code-server.dev/install.sh | sh
sudo systemctl restart code-server@$USER

The project's installation and setup guide pages describe further options, including Nginx as the proxy.

Frequently asked questions

Can I still run the old Cloud9 SDK?

The code can still be cloned, but it has been unmaintained since the repository was archived in April 2021 and it depends on outdated Node.js releases. An editor with a terminal is a remote shell on your server; do not expose an unmaintained one.

Do Visual Studio Code extensions work in code-server?

Most do. code-server installs extensions from the Open VSX registry rather than Microsoft's marketplace, so a small number of Microsoft-published extensions are missing or replaced by open equivalents.

Can I avoid storing the password in plain text?

Yes. Replace the password line in config.yaml with a hashed-password line containing an Argon2 hash; that field takes precedence. The project FAQ shows how to generate the hash.

Can several people share one installation?

Give each person a system account and start one instance per account with code-server@username, each on its own port in that user's config.yaml. A single instance has one login and one set of file permissions, so sharing it means sharing everything.

Share story:

Continue reading other guides on How VPS.