Hyper Backup cannot connect to its destination even though the remote NAS opens in a browser. What should I check?

Applies to: Hyper Backup, including remote Synology NAS and supported cloud destinations.

Work through these checks

1. Record the failed task’s destination type, hostname, error and last successful run. Check whether the address, router, destination password or cloud authorisation recently changed. Keep the existing repository intact.
2. For a remote Synology destination, confirm Hyper Backup Vault is installed and running. Have the administrator check the task’s actual service route through the intended VPN or private network, rather than exposing DSM or backup ports publicly.
3. Review destination credentials and access to the selected shared folder. For cloud tasks, check the provider-specific authorisation and storage tier. A normal browser sign-in is not proof that the task’s saved authorisation remains valid.
4. Synchronise time on both systems and inspect destination-side logs for the matching attempt. Renew only the affected credentials or provider authorisation, then make one controlled retry.

Confirm the result

A completed backup and a successful small-file restore from that version confirm more than a successful login or connection test.

If you need help

Include these details in your ticket: Destination type, exact redacted error, versions, recent network/account changes and the destination log time.

Updated 261107