NAS Codex › Synology › Synology Hyper Backup can't connect to the remote NAS or reach its login portal
Synology Hyper Backup can't connect to the remote NAS or reach its login portal
Hyper Backup can back up a Synology NAS to another Synology NAS or a file server. When the task is created over the internet, Synology says Hyper Backup may fail to open the destination's DSM login portal if the router forwards a different external port to the internal DSM port. Its remote-backup guide lists the other requirements: Hyper Backup Vault on the destination, and the right ports open between the two networks.
Written against: DSM 6.0 or above and DSM Enterprise (Synology KB: Hyper Backup fails to reach the DSM login portal of the destination; back up to a remote Synology storage system; Hyper Backup Vault). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
If your router forwards, for example, external port 8001 to DSM port 5001 on the destination, Hyper Backup can't open its login portal during task creation. Temporarily change the rule so the external port equals the internal DSM port (both 5001), create and sign in to the task, then put the rule back. Also make sure Hyper Backup Vault is installed on the destination, at the same or a later version.
1. Login portal won't open when creating the task
Synology explains that during task creation, Hyper Backup connects to the destination using the DSM port set in Control Panel > Login Portal on that destination. There is currently no option to enter a custom external port at this stage, so a port forwarding rule with different external and internal numbers makes the connection fail. Its fix:
- Sign in to your router's configuration interface.
- Find the port forwarding rule for the destination NAS's DSM port.
- Change it so the external port matches the internal DSM port, for example both 5001.
- Once the backup task is created and authenticated, you can change the rule back to how it was.
Synology notes that if you aren't sure how to change your router's port forwarding, ask the router manufacturer.
2. Hyper Backup Vault on the destination
To back up to another Synology NAS, Synology's guide says to choose Remote NAS Device as the destination and make sure Hyper Backup Vault is installed on the destination, at the same or a later version than Hyper Backup. Synology describes Vault as a package for DSM 6.0 or later that turns a Synology NAS into a Hyper Backup destination, where you can view the backup data and logs. It notes that LUN backup tasks created on DSM can't be viewed in Hyper Backup Vault.
3. Ports between two networks
If the source and destination are on different networks, Synology says to make sure the ports and firewall settings are configured correctly. The ports it lists for external access are:
- Hyper Backup Vault: 5000 (HTTP), 5001 (HTTPS) and 6281. For Hyper Backup Vault on DSM 6.0: 6281.
- Other backup destinations: 873 and 22 (rsync server only); 5000 (HTTP), 5005 (WebDAV) and 5006 (WebDAV with HTTPS only).
4. Create the task step by step
- Install Hyper Backup from Package Center if needed, open it, click + and choose Folders and Packages.
- Choose Remote NAS Device, select Create backup task, enter the remote NAS's address and account details, and click Log In to connect.
- Pick a shared folder on the destination (you can rename the Directory), then the shared folders and packages to back up.
- Set the options: task name, notifications, compression, backup schedule, integrity check schedule and client-side encryption, then the version rotation (earliest versions or Smart Recycle, and the maximum number of versions).
- Click Done, then Yes to run the task now.
5. Encrypted shared folders
Synology says that if the destination folder is an encrypted shared folder, it must be mounted: go to Control Panel > Shared Folder, select it, click Encryption > Mount, and enter or import the key. Encrypted shared folders in the backup source must stay mounted throughout the backup.
When to stop and get help
Synology's login-portal fix is temporary: after the task is created and authenticated you can restore your original port forwarding rule. Its guide also notes that Hyper Backup does not support WriteOnce; to protect backup data that way, Synology says to create immutable snapshots.
Questions
Why can't Hyper Backup open the login portal of the destination NAS?
Synology says it happens when the router forwards a different external port to the DSM port. Make the external and internal ports match while you create the task.
What do I need on the destination for a Hyper Backup remote NAS task?
Synology says Hyper Backup Vault must be installed on the destination NAS, at the same or a later version than Hyper Backup.
Which ports does Hyper Backup Vault use?
Synology lists 5000 (HTTP), 5001 (HTTPS) and 6281 for Hyper Backup Vault, and 6281 for Hyper Backup Vault on DSM 6.0.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.
- Synology KB: Why does Hyper Backup fail to reach the DSM login portal of the destination Synology storage system when creating a backup task?
- Synology KB: How do I back up my data to a remote Synology storage system using Hyper Backup?
- Synology KB: What backup tasks can be viewed on Hyper Backup Vault?