# Active Backup Agent Recovery Portal option

**URL:** <https://forums.spacerex.co/t/active-backup-agent-recovery-portal-option/3447>\
**Category:** Synology\
**Tags:** active-backup\
**Created:** [August 24, 2025, 9:56pm UTC](https://forums.spacerex.co/t/active-backup-agent-recovery-portal-option/3447 "2025-08-24T21:56:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_D](https://forums.spacerex.co/user_avatar/forums.spacerex.co/mark_d/32/1464_2.png) [@Mark\_D](https://forums.spacerex.co/u/Mark_D)\
**Post date:** [August 24, 2025, 9:56pm UTC](https://forums.spacerex.co/t/active-backup-agent-recovery-portal-option/3447/1 "2025-08-24T21:56:39Z")

</div>

Version 3.0.0-4638

Using the Recovery portal option in the agent, It attempts to use my nas hostname and port instead of the local ip address and port thru the web browser that is displayed in the client agent. I get a Sorry the page you are looking for is not found. I always have to modify that to the local ip address and port of the nas to be able to login and restore. Where do I go to change this to use the local nas ip addres instead?

Thanks

---

<div class="post-metadata">

**Author:** ![Sky](https://forums.spacerex.co/user_avatar/forums.spacerex.co/sky/32/753_2.png) [@Sky](https://forums.spacerex.co/u/Sky)\
**Post date:** [August 29, 2025, 9:45pm UTC](https://forums.spacerex.co/t/active-backup-agent-recovery-portal-option/3447/2 "2025-08-29T21:45:41Z")

</div>

I’ve seen issues with this in the past as well. It’s in the design of ABB Agent not to work that way, which can be quite annoying _in some circumstances_ but very understandable in others. ABB Agent is designed to work from multiple endpoints, including mobile endpoints such as laptops. This being the case, say a laptop is the endpoint and it’s off-site, having it trying to connect to a local IP would be a problem.

The solution is to use either a static IP addressable from the internet, or a DDNS service such as the free DDNS service available from Synology on your NAS. There you can name your own “site”, e.g., _mysite_. **dscloud.biz** and simply point your ABB Agent there. (`DSM > Control Panel > Connectivity > External Access > DDNS`). You can also get a free security certificate through the NAS for your new “site” so when you want to use ABB Agent to do a restore it will recognize the secure connection, something that is convoluted and definitely more difficult to achieve trying to work it internally. (`DSM > Control Panel > Connectivity > Security > Certificate)`

This works well with _dscloud, et al.,_ but _QuickConnect_ is another beast altogether. Because it uses relay servers to get you to the fastest connection, the original connection will not show it as a secure connection. This can cause issues depending on how you’ve setup ABB.

You can find more information on ABB Agent here: [Synology KB — ABB Agent](https://kb.synology.com/en-global/DSM/help/ActiveBackupBusinessAgent/activebackupbusinessagent?version=7)

---

<div class="post-metadata">

**Author:** ![Mark\_D](https://forums.spacerex.co/user_avatar/forums.spacerex.co/mark_d/32/1464_2.png) [@Mark\_D](https://forums.spacerex.co/u/Mark_D)\
**Post date:** [September 3, 2025, 1:20pm UTC](https://forums.spacerex.co/t/active-backup-agent-recovery-portal-option/3447/3 "2025-09-03T13:20:10Z")

</div>

Thanks for your insight Sky,

I do have 2 DNS addresses for the nas but looks like under External Access\>Advanced it was set to my nas Server name rather than a full DNS hostname. Changed that now it is working correcly.

Thanks

---

<div class="post-metadata">

**Author:** ![SpiceRex](https://forums.spacerex.co/user_avatar/forums.spacerex.co/spicerex/32/644_2.png) [@SpiceRex](https://forums.spacerex.co/u/SpiceRex)\
**Post date:** [September 21, 2025, 7:47pm UTC](https://forums.spacerex.co/t/active-backup-agent-recovery-portal-option/3447/4 "2025-09-21T19:47:00Z")

</div>

I believe the recovery portal uses the same connection credentials as the backup agent. If you set your backup agent to use a local IP then the portal will use the same path. If you use DDNS thrn that’s the way the portal will try to connect.
