backup.create silently no-ops for a database on a remote server

Version

v0.30.5 (still reproduces; not addressed in v0.30.6 nor in current canary)

Summary

Creating a backup for a database deployed on a remote server returns 200 with an empty body, but nothing is inserted and no backup is scheduled. No error is surfaced to the user.

The service-existence check during creation looks up the Docker service by appName against the local/control-plane daemon instead of the remote server's daemon. Control-plane logs show:

Error: (HTTP code 404) no such service - service <appName> not found

while the service is running fine on the remote server.

To Reproduce

1. Add a remote server.
2. Deploy a Postgres (or any DB) on that remote server.
3. Configure an S3 destination and call backup.create for that database.
4. Response is 200 + empty body; no backup row is created and no backup ever runs.

Expected behavior

The service-existence lookup should target the server the database is actually deployed on (via that server's SSH/Docker connection), matching how deploy and log operations already route to remote servers.

Which area(s) are affected?

Remote server, Backups

Are you deploying the applications where Dokploy is installed or on a remote server?

Remote server

Start at the backup.create entry point and compare its service-existence lookup with the existing deploy and log operations for remote servers. Trace the SSH/Docker connection used for the database, then verify that a remote backup creates a row and schedules successfully instead of returning an empty response.