[Bug]: Cannot assign null to property after upgrade to v4.0.0-beta.370

[driaug]

Error Message and Logs

My self-hosted Coolify instance has a Redis instance deployed on it.
Everything was running smoothly until I upgraded to v4.0.0-beta.370, after which trying to open it results in the following 500 error.

Cannot assign null to property App\Livewire\Project\Database\Redis\General::$redis_username of type string (View: /var/www/html/resources/views/livewire/project/database/configuration.blade.php)

I have tried a variety of ways to access the Redis container but have not been successful so far.

Steps to Reproduce

No reproductions steps as I am not sure what caused this issue.
No changes were made to the underlying server or Coolify instance except upgrading to the latest version.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.370

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 22.04.3 LTS

Additional Information

No response

[peaklabs-dev]

Can you please upgrade to the latest version as I am unable to reproduce this issue.

Did you manually set a Redis username prior to v4.0.0-beta.370?

[driaug]

I don't believe I did.

Issue still remains and at this point I would just like to remove the corrupted Redis instance from my setup but this is not possible since I cannot open it.

Can I just remove the affected server in my actual hosting? How will Coolify handle this?

[jekuer]

I have a similar issue.

How to reproduce:

1. Create a redis db
2. mount the /data path to another local directory (not sure if this has an impact, maybe can be skipped)
3. Clone the db to the same server (no matter if different env or not)

Result:
It create a new empty shell (app).
When hitting the app, the error mentioned by @driaug appears.
Problem with this approach: I cannot find the new resource anywhere. Guess it is only present as orphaned entry in some coolify db? With the current UI design, it is also impossible to delete it from there. It is possible to read and delete it via API though.