Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: scheduled-tasks 500 Error #4894

Closed
Cizzl opened this issue Jan 21, 2025 · 3 comments · Fixed by #4887
Closed

[Bug]: scheduled-tasks 500 Error #4894

Cizzl opened this issue Jan 21, 2025 · 3 comments · Fixed by #4887

Comments

@Cizzl
Copy link

Cizzl commented Jan 21, 2025

Error Message and Logs

Image

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

updateCompose(): Argument #1 ($resource) must be of type App\Models\ServiceApplication|App\Models\ServiceDatabase, array given, called in /var/www/html/bootstrap/helpers/shared.php on line 2875 (View: /var/www/html/resources/views/livewire/project/application/configuration.blade.php)

I only have 2 projects with a docker compose, on both of them it occured. Not on Nixpack / Dockerfile.

Steps to Reproduce

  1. Open a Project which has a docker-compose as build pack
  2. Navigate to scheduled-tasks
  3. Error pops up

Example Repository URL

No response

Coolify Version

v4.0.0-beta.384

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 22.04.4 LTS

Additional Information

No response

@Cizzl Cizzl added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 21, 2025
@wesselhuising
Copy link

wesselhuising commented Jan 21, 2025

Same here, unable to deploy services using docker compose files since the new update (384).

updateCompose(): Argument #1 ($resource) must be of type App\Models\ServiceApplication|App\Models\ServiceDatabase, array given, called in /var/www/html/bootstrap/helpers/shared.php on line 2875

@EthanCarollo
Copy link

EthanCarollo commented Jan 21, 2025

I encountered the same issue; it affected some of my services, but not all of them.

Image

Tried to rollback to 3.380 but i got another new error

Image

So to temporarily solve this problem I duplicated my service on the same server and it seems to be working...

@peaklabs-dev peaklabs-dev removed the 🔍 Triage Issues that need assessment and prioritization. label Jan 21, 2025
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Jan 21, 2025
@andrasbacsai
Copy link
Member

I am going to fix it today (and probably release it as well).

@andrasbacsai andrasbacsai self-assigned this Jan 21, 2025
@github-actions github-actions bot removed the 🐛 Bug Reported issues that need to be reproduced by the team. label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants