# local registry, notification link still points to cloud

**URL:** <https://community.netdata.cloud/t/local-registry-notification-link-still-points-to-cloud/2817>\
**Category:** Help\
**Tags:** agent\
**Created:** [April 28, 2022, 5:11pm UTC](https://community.netdata.cloud/t/local-registry-notification-link-still-points-to-cloud/2817 "2022-04-28T17:11:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![user-945](https://avatars.discourse-cdn.com/v4/letter/u/278dde/32.png) [@user-945](https://community.netdata.cloud/u/user-945)\
**Post date:** [April 28, 2022, 5:11pm UTC](https://community.netdata.cloud/t/local-registry-notification-link-still-points-to-cloud/2817/1 "2022-04-28T17:11:02Z")

</div>

I only have one instance and I configured it as local registry.  
I can see in the browser dev-tools that the server is registering with itself.

But Notifications still point to [Netdata Cloud | Alarm Redirect](https://app.netdata.cloud/alarms/redirect?agentId=)…  
The link only redirects me to a login form.

What else do I need to configure so that my local registry is used as described here?

> <https://github.com/netdata/netdata/issues/3495>
>
> The notification mails i do receive so far all feature an URL following this pat…tern:
> 
> \> https://registry.my-netdata.io/goto-host-from-alarm.html?host=HOSTNAME&chart=disk\_backlog.sda&family=sda&alarm=10min\_disk\_backlog&.....
> 
> Visiting this link does some magic and redirects to the webinterface of the actual netdata installation which caused the notification.
> 
> I would prefer a link to the actual host itself, without redirect etc. Is that possible so far? 
> If not - could you consider that as option?

---

<div class="post-metadata">

**Author:** ![Manolis\_Vasilakis](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/manolis_vasilakis/32/820_2.png) [@Manolis\_Vasilakis](https://community.netdata.cloud/u/Manolis_Vasilakis)\
**Post date:** [April 29, 2022, 9:37am UTC](https://community.netdata.cloud/t/local-registry-notification-link-still-points-to-cloud/2817/2 "2022-04-29T09:37:31Z")

</div>

Hello ! Thank for your report.

It should use a different url (not going to the cloud) when you have a custom registry… will try to reproduce and will let you know!

---

<div class="post-metadata">

**Author:** ![user-945](https://avatars.discourse-cdn.com/v4/letter/u/278dde/32.png) [@user-945](https://community.netdata.cloud/u/user-945)\
**Post date:** [April 29, 2022, 11:32am UTC](https://community.netdata.cloud/t/local-registry-notification-link-still-points-to-cloud/2817/3 "2022-04-29T11:32:33Z")

</div>

thank you 🙂

I am using the native binary nightly packages on debian bullseye.  
It is a fresh installation on a proxmox server.

---

<div class="post-metadata">

**Author:** ![napkid](https://avatars.discourse-cdn.com/v4/letter/n/a8b319/32.png) [@napkid](https://community.netdata.cloud/u/napkid)\
**Post date:** [May 31, 2022, 2:24pm UTC](https://community.netdata.cloud/t/local-registry-notification-link-still-points-to-cloud/2817/4 "2022-05-31T14:24:48Z")

</div>

Hello !

Any updates about this ? I have the exact same problem.  
My Netdata registry is enabled and working, and Netdata cloud is disabled in the `/etc/netdata/cloud.d/cloud.conf` file, but my notifications still have the Netdata cloud link.  
Should I file an issue on Github ?

Thanks.

---

<div class="post-metadata">

**Author:** ![Manolis\_Vasilakis](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/manolis_vasilakis/32/820_2.png) [@Manolis\_Vasilakis](https://community.netdata.cloud/u/Manolis_Vasilakis)\
**Post date:** [June 3, 2022, 7:31am UTC](https://community.netdata.cloud/t/local-registry-notification-link-still-points-to-cloud/2817/5 "2022-06-03T07:31:36Z")

</div>

Hi, yes please (let’s move it to a github issue) and sorry for the late reply!