# Message "Cannot login as..." on cert renewal \<= should this be an FAQ?

**URL:** <https://forum.delta.chat/t/message-cannot-login-as-on-cert-renewal-should-this-be-an-faq/5819>\
**Category:** Mutual Help\
**Tags:** solved, core, multi-transport\
**Created:** [September 23, 2026, 8:23pm UTC](https://forum.delta.chat/t/message-cannot-login-as-on-cert-renewal-should-this-be-an-faq/5819 "2026-09-23T20:23:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hal](https://forum.delta.chat/letter_avatar_proxy/v4/letter/h/ee7513/32.png) [@Hal](https://forum.delta.chat/u/Hal)\
**Post date:** [September 23, 2026, 8:23pm UTC](https://forum.delta.chat/t/message-cannot-login-as-on-cert-renewal-should-this-be-an-faq/5819/1 "2026-09-23T20:23:06Z")

</div>

I’m new to delta chat, and was confused by seeing a “Cannot login as” message. After research here pointed to [this github issue](https://github.com/chatmail/core/issues/1910) and checking the server’s current cert, I see that the message was generated right as the updated tls cert became effective.

That [issue](https://github.com/chatmail/core/issues/1910) was closed in 2020, after opening a [“improve usability”](https://github.com/chatmail/core/issues/1923) issue, which was (as I read it) deemed “fixed by [march2022 cleanup](https://github.com/orgs/deltachat/projects/48)”.

**Delta Chat version**  
iOS: v2.59.1 _and_ win11 desktop v2.59.1

**Expected behavior**

1. To have tls cert updates happen transparently.
2. To have a simple way to tell “all is okay” about account and relays.

**Actual behavior**

1. n00b panics that their account is gone, and unsure how to migrate to a new relay!
2. has no clue how to verify “health” of account & relays.
  - the error message remains in the “Device Messages”
  - the error message “link” just opens the “saved messages” chat.

**Steps to reproduce the problem**

1. Create account on not-the-main relay
2. Try to use delta chat as a new tls cert becomes valid
3. Be unsure for days if things are working correctly (i.e. n00b)

---

<div class="post-metadata">

**Author:** ![WofWca](https://forum.delta.chat/user_avatar/forum.delta.chat/wofwca/32/1702_2.png) [@WofWca](https://forum.delta.chat/u/WofWca)\
**Post date:** [September 24, 2026, 7:27am UTC](https://forum.delta.chat/t/message-cannot-login-as-on-cert-renewal-should-this-be-an-faq/5819/2 "2026-09-24T07:27:33Z")

</div>

This message is going to be removed in the upcoming release. See

> <https://github.com/chatmail/core/pull/8629>
>
> Authentication failures may happen because of internal server errors. Device mes…sage saying "Please check if the email address and the password are correct" was written for classic email setups when the user knows the password. For users of chatmail relays this message is not actionable, but still appears when relay fails to check the password.
> 
> Closes #8614 if merged.
> 
> https://github.com/chatmail/core/pull/8589 (preferring login errors over connection errors) still makes sense even if device message is deleted as it is important for the error during configuration.

IMU it’s just no longer that important, with the [multi-relay stuff](https://delta.chat/en/2026-03-31-zero#maximizing-availability-and-resilience-through-multi-path-delivery). The status of servers is still available in the “Connectivity” dialog.

---

<div class="post-metadata">

**Author:** ![Hal](https://forum.delta.chat/letter_avatar_proxy/v4/letter/h/ee7513/32.png) [@Hal](https://forum.delta.chat/u/Hal)\
**Post date:** [September 24, 2026, 5:52pm UTC](https://forum.delta.chat/t/message-cannot-login-as-on-cert-renewal-should-this-be-an-faq/5819/3 "2026-09-24T17:52:25Z")

</div>

Thanks, Ian! Good to know. There are a lot of “oh, that’s not how it works anymore” pieces of Delta Chat that I’m still learning. Removal of these leftover noise messages will make things less confusing for us new folk.