Why Rchilli API is not running at start-up or after reboot ?

If the RChilli API is not running at start-up or after a system reboot, there are a few possible causes and corresponding resolutions based on standard setup practices and documentation:

1. Docker Container Not Set to Auto-Restart

If you're running RChilli API via Docker (which is common), it may not be configured to automatically start on reboot.

Solution:
Use Docker’s restart policy to ensure the container starts automatically:

• The --restart=always flag ensures that the container starts whenever the Docker daemon starts (including after a reboot).

• You can update an existing container with this command:

📘 Reference: Installing RChilli API using Docker.

2. Missing or Misconfigured System Services

If RChilli was manually installed on a Linux server (outside of Docker), it might lack a systemd service to start the application automatically.

Solution:
Create a systemd service file (e.g., /etc/systemd/system/rchilli-api.service):

Enable and start the service:

3. Configuration or Environment File Not Loaded Properly

Check if your startup script depends on environment variables or config files that are not available or sourced correctly at boot time.

Solution:
Ensure all required environment variables are loaded in the service definition or shell script, such as:

You can place these in a .env file or inline in the service script.

4. No Network or Dependency Delay at Boot

If your server’s networking or required services (e.g., database, API gateway) are not fully available at boot time, the API may fail to initialize.

Solution:
Add a delay or retry logic in the startup script or set service dependencies in systemd.

Example:

Also consider a script that retries the start process if the first attempt fails.

5. Check for Error Logs

Finally, examine logs to identify what’s going wrong during startup:

These logs may reveal configuration issues, missing environment variables, or port conflicts.

Need More Help?

If you're unsure about the setup or need a specific startup script/config validation, email support@rchilli.com with:

• Environment details (Docker or manual install)

• Operating system

• Log snippets or error messages