# Can't login because login email doesn't get delivered

**URL:** <https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441>\
**Category:** Help\
**Tags:** cloud\
**Created:** [January 20, 2022, 10:57am UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441 "2022-01-20T10:57:00Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![MattX](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@MattX](https://community.netdata.cloud/u/MattX)\
**Post date:** [September 15, 2022, 6:14pm UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441/24 "2022-09-15T18:14:36Z")

</div>

This problem is not resolved, I’ve same problem and cann’t login to my Netdata cloud account because don’t get any email delivered.

---

<div class="post-metadata">

**Author:** ![Christopher\_Akritid1](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/christopher_akritid1/32/419_2.png) [@Christopher\_Akritid1](https://community.netdata.cloud/u/Christopher_Akritid1)\
**Post date:** [September 16, 2022, 2:36pm UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441/25 "2022-09-16T14:36:51Z")

</div>

As above, send your email address to chris@netdata.cloud, so I can look you up in the deferred or blocked recipients.

---

<div class="post-metadata">

**Author:** ![otoole](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/otoole/32/3030_2.png) [@otoole](https://community.netdata.cloud/u/otoole)\
**Post date:** [July 28, 2023, 5:42am UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441/26 "2023-07-28T05:42:45Z")

</div>

I also have the same problem – I have been using netdata for a couple of years with no problems, but now no longer receive the emails. I have access to our spam filter system and can see that the mail is not even arriving there.

---

<div class="post-metadata">

**Author:** ![hugo](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/hugo/32/3714_2.png) [@hugo](https://community.netdata.cloud/u/hugo)\
**Post date:** [July 28, 2023, 5:21pm UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441/27 "2023-07-28T17:21:58Z")

</div>

@otoole could you please share with your email address so we can check?  
Mine is hugo@netdata.cloud

---

<div class="post-metadata">

**Author:** ![luckman212](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/luckman212/32/3726_2.png) [@luckman212](https://community.netdata.cloud/u/luckman212)\
**Post date:** [June 8, 2024, 10:22pm UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441/28 "2024-06-08T22:22:44Z")

</div>

In 2024 is there any other way to sign in using FIDO2 hardware token, Passkey, simple username + password + MFA, etc? “Login by magic link in email” is my most hated method of login.

---

<div class="post-metadata">

**Author:** ![luckman212](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/luckman212/32/3726_2.png) [@luckman212](https://community.netdata.cloud/u/luckman212)\
**Post date:** [October 3, 2026, 11:12am UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441/29 "2026-10-03T11:12:40Z")

</div>

Back again over 2 years later to check if anything’s changed or will be changing on this… I loathe “email me a code” login flow. We have passkeys, FIDO/Yubikeys, strong MFA, password managers… why are we using an unencrypted transport invented in 1971 ?

---

<div class="post-metadata">

**Author:** ![kostas\_apostol](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@kostas\_apostol](https://community.netdata.cloud/u/kostas_apostol)\
**Post date:** [October 5, 2026, 9:21am UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441/30 "2026-10-05T09:21:43Z")

</div>

Hi @luckman212,

]Nothing has changed yet. Netdata Cloud is passwordless by design.

We never store credentials, so there’s no password database to leak. The trade-off you’ve called out is real, the magic-link path leans on your email inbox, and we can’t layer MFA on it ourselves.

What works today:

• **Google or GitHub OAuth** : MFA (passkeys, YubiKeys, TOTP) enforced at every sign-in via those accounts  
• **Enterprise SSO (OIDC/Okta)** on paid plans : your own IdP enforces MFA and hardware keys

Passkeys/FIDO2/TOTP in Netdata Cloud aren’t supported yet. Your ask is tracked in [netdata-cloud#797](https://github.com/netdata/netdata-cloud/issues/797).

I’ve linked this thread there and will follow up here as soon as there’s movement.

---

<div class="post-metadata">

**Author:** ![luckman212](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/luckman212/32/3726_2.png) [@luckman212](https://community.netdata.cloud/u/luckman212)\
**Post date:** [October 5, 2026, 12:43pm UTC](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441/31 "2026-10-05T12:43:28Z")

</div>

Thank you. I subscribed to that GH issue. For now, I switched to GitHub auth, at least it is quick and can be done without opening my email client.

[Previous page](https://community.netdata.cloud/t/cant-login-because-login-email-doesnt-get-delivered/2441.md?page=1)
