Skip to content

[Bug]: update issue version 453 to 454 #7599

@JorenRothman

Description

@JorenRothman

Error Message and Logs

I'm having trouble updating version 453 to 454 on both two my instances of Coolify.
I've tried running the update via the web UI and also via the command line as described in the troubleshooting docs.

It seems to be getting stuck on the /data/coolify/source/upgrade.sh script and an issue with the coolify db.

CLI output:

Welcome to Coolify Installer!
This script will install everything for you. Sit back and relax.
Source code: https://github.com/coollabsio/coolify/blob/v4.x/scripts/install.sh
Using registry URL from .env: ghcr.io
Found existing Docker network pool: 10.0.0.0/8/24
---------------------------------------------
| Operating System  | ubuntu 24.04
| Docker            | 27.0
| Coolify           | 4.0.0-beta.454
| Helper            | 1.0.12
| Realtime          | 1.0.10
| Docker Pool       | 10.0.0.0/8 (size 24)
| Registry URL      | ghcr.io
---------------------------------------------

1. Installing required packages (curl, wget, git, jq, openssl).
2. Check OpenSSH server configuration.
 - OpenSSH server is installed.
 - SSH PermitRootLogin is enabled.
3. Check Docker Installation.
 - Docker is installed.
4. Check Docker Configuration.
 - Network pool configuration: 10.0.0.0/8/24
 - To override existing configuration: DOCKER_POOL_FORCE_OVERRIDE=true
 - Log configuration is up to date
 - Configuration is up to date
5. Download required files from CDN.
6. Setting up environment variable file
 - Creating backup of existing .env file to .env-20251212-094402
 - Merging .env.production values into .env
 - .env file merged successfully
7. Checking and updating environment variables if necessary...
8. Checking for SSH key for localhost access.
9. Installing Coolify (4.0.0-beta.454)
 - It could take a while based on your server's performance, network speed, stars, etc.
 - Please wait.
 - Until then, here's a joke for you:

Hey Girl,
Roses are #ff0000,
Violets are #0000ff,
I use hex codes,
But I'd use RGB for you.

Log File:

\"source\" (expected \"coolify\"). Use `external: true` to use an existing volume"
time="2025-12-12T09:44:09Z" level=warning msg="volume \"coolify-redis\" already exists but was created for project \"source\" (expected \"coolify\"). Use `external: true` to use an existing volume"
 Container coolify-db  Creating
 Container coolify-redis  Creating
 Container coolify-realtime  Creating
 Container coolify-db  Error response from daemon: Conflict. The container name "/coolify-db" is already in use by container "430c18af286136e4d799c3faca3948d5d259cd6e9261a4f910d3b0a07776bcff". You have to remove (or rename) that container to be able to reuse that name.
Error response from daemon: Conflict. The container name "/coolify-db" is already in use by container "430c18af286136e4d799c3faca3948d5d259cd6e9261a4f910d3b0a07776bcff". You have to remove (or rename) that container to be able to reuse that name.
exit status 1

Steps to Reproduce

  1. Have a version 453 installed
  2. Update to version 454
  3. Nothing happens

Example Repository URL

No response

Coolify Version

v4.0.0-beta.453

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    🔍 TriageIssues that need assessment and prioritization.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions