Help

Fixes for problems you might run into with CSCM. Most commands below run in the installation directory, ~/cscm by default.

Minecraft server is missing features after an update

After CSCM updates, servers you created before the update still run in their old Docker container. New features that need a fresh container, like new settings or console improvements, don't show up for those servers until the container is rebuilt.

Fix: rebuild the server's Docker container.

1. Open the server in the CSCM dashboard and go to the Settings tab.
2. Next to Recreate Container, click Recreate.
3. Choose whether to create a backup first. It's optional, but a good habit.
4. Confirm. The server restarts in a new container with the same settings.

Updating CSCM

CSCM checks GitHub for a new version about once an hour. When one is out, a banner appears at the top of the dashboard. Click Update and CSCM downloads the new version and rebuilds itself. The dashboard is offline for a few minutes and reloads on its own. Your Minecraft servers keep running during the update.

After updating, recreate the containers of servers that should get new server features.

The update failed

The update window shows what went wrong. The most common cause is git pull failed: files in the installation directory were changed by hand, so the new version can't be applied on top. See what changed:

cd ~/cscm
git status

Your settings live in .env, which is never overwritten, so you usually don't need other local changes. To throw them away and update manually:

git stash
git pull
docker compose up --build -d

Update manually

If the banner says CSCM can't update itself, for example because it wasn't installed with the installer, update from a terminal:

cd ~/cscm
git pull
docker compose up --build -d

No update banner even though there is a new version

The check runs at most once an hour and needs internet access to GitHub. Wait a bit and reload the dashboard. If your network blocks GitHub, update manually.

The dashboard doesn't load

Check that Docker is running and that the CSCM containers are up:

cd ~/cscm
docker compose ps
docker compose logs --tail=100 api web

If a container isn't running, start everything again with docker compose up -d. The dashboard runs on the port you chose during installation, http://localhost:3000 by default.

Still stuck?

Open an issue on GitHub with what you did and the output of docker compose logs --tail=100 api. Remove passwords and keys before posting. To remove CSCM completely, see the uninstall guide.