error: ssh configuration...cannot connect

[foveann]

Error when running sync-all.sh

[user@host scripts]$ bash sync-all.sh dev stage
Reset the stage database and sync up from dev? [y/N] y
Sync the uploads folder? [y/N] y
Success: Exported to 'stage-backup.sql'.
Success: Database reset.
Error: Cannot connect over SSH using provided configuration.
sending incremental file list

Result
Strangely the demo file I placed in the /web/app/uploads folder did successfully get uploaded to the stage environment. But when I removed the demo file and tried to run that same command again, the demo file remained in the stage environment as if it was not updating. It can send the file but cannot delete the file so it doesn't seem to be syncing.

Debug attempts:
I also checked the user 'web' and was able to successfully ssh into my remote server.

.

[jasperf]

Two separate problems here, and only one has a clear answer.

"Cannot connect over SSH using provided configuration" — never reproduced, and there is not enough in the thread to diagnose it now. Typically it means the @stage alias in wp-cli.yml points somewhere the web user cannot reach, even when your own ssh works, because the alias uses its own user/host/path.

Uploads sent but not deleted — that one is expected behaviour, not a bug. sync-all.sh ran plain rsync -az with no --delete, so removals never propagate. Nothing was broken; the flag was absent.

Worth being straight about how the successor handles it, since it is only half a fix: wp-ops makes the choice explicit on pull, with a warning before anything is removed —

wp-ops files-pull example.com production --delete yes   # mirror exactly
wp-ops files-pull example.com production                # additive (default)

— but push is still additive only, deliberately, so a thin local uploads directory can never delete production media. So your dev → stage case behaves the same as it did; it is now documented rather than surprising.

I am evaluating packaging these sync playbooks as a standalone Trellis Galaxy role, which would be the place to revisit whether push should offer an opt-in mirror mode with the same guard rails as pull.

Closing as stale since this repo is being archived. Sorry for the silence.