You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, I wanted to thank you for putting that much effort into cooify. It's a masterpiece and I'm recommending it over and over to my friends and collegues! <3
#3668
As you can see here I had two problems which are fixed at this moment. Unfortunately after updating to 350 I'm now getting the error
DatabaseBackupJob failed with: No query results for model [App\Models\Team] 1
Could you please have a look at the problem? Thanks!
Steps to Reproduce
Go to settings
click on Backup now
Example Repository URL
No response
Coolify Version
v4.0.0-beta.350
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian GNU/Linux 12 (bookworm)
Additional Information
happens when I check S3 (Hetzner) as well as when I uncheck it, but it seems that the error is caused a few seconds later when unchecking s3
The text was updated successfully, but these errors were encountered:
lorenzpfei
added
🐛 Bug
Reported issues that need to be reproduced by the team.
🔍 Triage
Issues that need assessment and prioritization.
labels
Oct 3, 2024
Error Message and Logs
Firstly, I wanted to thank you for putting that much effort into cooify. It's a masterpiece and I'm recommending it over and over to my friends and collegues! <3
#3668
As you can see here I had two problems which are fixed at this moment. Unfortunately after updating to 350 I'm now getting the error
Could you please have a look at the problem? Thanks!
Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta.350
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian GNU/Linux 12 (bookworm)
Additional Information
happens when I check S3 (Hetzner) as well as when I uncheck it, but it seems that the error is caused a few seconds later when unchecking s3
The text was updated successfully, but these errors were encountered: