[Bug]: 500 Error when accessing dashboard for all resources of a project and environment after restore on new server

[ldesomer]

Error Message and Logs

After restoring Coolify on a new server, the dashboard for all resources of a project and its environment initially worked. However, after updating Coolify, accessing the dashboard now results in a 500 Internal Server Error.

500 Wait, this is not cool... There has been an error with the following error message:

SQLSTATE[42703]: Undefined column: 7 ERROR: column "is_buildtime" does not exist LINE 1: select "value", "is_multiline", "is_literal", "is_buildtime"... ^ HINT: Perhaps you meant to reference the column "environment_variables.is_build_time". (Connection: pgsql, SQL: select "value", "is_multiline", "is_literal", "is_buildtime", "is_runtime" from "environment_variables" where "environment_variables"."resourceable_type" = App\Models\Application and "environment_variables"."resourceable_id" = 3 and "environment_variables"."resourceable_id" is not null and "is_preview" = 0 order by CASE WHEN is_required = true THEN 1 WHEN LOWER(key) LIKE 'service_%' THEN 2 ELSE 3 END, LOWER(key) ASC) (View: /var/www/html/resources/views/livewire/project/application/configuration.blade.php)

Steps to Reproduce

1. Restore Coolify on a new server.
2. Go to the dashboard for a project.
3. Attempt to view all resources and environment configuration.
4. Observe the error.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.452

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 25.04

Additional Information

No response

[coderabbitai[bot]]

Duplicate Detection

ℹ️ This issue may be similar to coollabsio/coolify#5765.

Related Issues

• coollabsio/coolify#6439: [Bug]: PostgreSQL Resource Creation Returns 500 Error - Unable to Access Database Configuration Page
• coollabsio/coolify#5765: [Bug]: General configuration 500 error

Suggested Issue Assignees

• epaprat
• NeKzor

Actions

• [ ] 📝 Generate an implementation plan for this issue

---

_{ℹ️ Note: Issue enrichment is currently in early access.}

Disable automatic issue enrichment

_{To disable automatic issue enrichment, add the following to your .coderabbit.yaml:}

issue_enrichment:
  auto_enrich:
    enabled: false

[ShadowArcanist]

Can you run docker exec coolify php artisan migrate --force on your server terminal and see if it solves the issue?

[ldesomer]

@ShadowArcanist it didn't solve the issue.

root@vps-c736fb3b:~# docker exec coolify php artisan migrate --force INFO Nothing to migrate.

[ldesomer]

Fixed it by migrating to an oldest version (v4.0.0-beta.400). When upgrading to v4.0.0-beta.452 the issue keeps coming back.