Skip to main content

RiCoder Does Not Work After Installation or Migration Between Servers

Problem description

After RiCoder is installed or moved to another virtual machine or another server, the application does not start correctly. When trying to log in to the admin panel, an error appears:

Container <Container name> is not running.

although all containers are shown as running in the Docker interface or in the RiCoder installation wizard dialog.

Cause

In new versions of RiCoder (version 7 and later), the way containers are started has changed.

If you use the old command:

docker compose up

the containers start without the required files with environment variables, which causes the application to work incorrectly.

Important!
Do not use the docker compose up command when manually restarting RiCoder containers from the command line: the containers will start, but the settings specified in the RiCoder installation wizard (ports, RiCoder admin web panel address) will not be applied. Default settings will be used.

Solution

1. Correct start of containers (with a full stop)

Use the new command to start:

docker compose --env-file=.env --env-file=settings.env up -d

This command:

  • Starts the containers in the background;
  • Loads settings from two files: *.env and settings.env;
  • The second file (settings.env) overrides values from the first one if necessary.
2. Stopping containers

The command for stopping containers has not changed:

docker compose down
3. Restarting containers

If RiCoder does not start, you can restart the containers without a full stop:

docker compose restart

Important notes
1. When moving a virtual machine snapshot, be sure to use the new start command with the environment files specified.
2. Two env files are needed to separate RiCoder settings and software versions.
3. The container status can be checked via the Docker command line, in the Docker Desktop interface or in the RiCoder installation wizard.

If the problem persists

If the problem is not solved after using the correct commands:

1. Check that the *.env and settings.env files are present in the CHOP_DEPLOY folder.

2. Check the container logs for additional errors.


Last updated: 09/09/2026