[Bug]: Clone supabase (created from templates) to another server

[gojnimer6553]

Error Message and Logs

Didn't found any relevant logs because i tried to move throught the UI

Steps to Reproduce

1. Create supabase from template (only changing FQDN)
2. Deploy for the first time
3. Stop the running container
4. Navigate through the UI to Resource (supabase instace) > Resource Operations
5. Click to clone into another server
6. Done, the resource will be cloned, but in the same server and not in the target one.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.341

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

ubuntu 24

Additional Information

I've done the same steps for cloning other resources and that worked just fine, the problem seems to be with supabase template

[pencilcheck]

Yea, it is a bug, also created a discussion to request allowing deploy to target server for all source type including services as well.
#4328

[oelhammouchi]

I'm having similar difficulties with other services!

[volfadar]

up, i also having this issue for blank compose file option.

[ReWWeR]

having the same issue with Minio

[pencilcheck]

I am trying to clone services like windmill to another server but it never worked. This is not just a bug but not working at all.

[pencilcheck]

@peaklabs-dev sorry to bother but can you get the right person to look into this? This is a crucial feature that I believe is essential to those who has multiple servers

[peaklabs-dev]

I have implemented a fix for this issue and it will be available in an upcoming release. Thanks for your patience.