Twake Login Fails with 'Failed to Fetch' When Using Stalwart Mail Helm Chart

[Nweke-cloud]

Hey everyone,

I’ve been trying out Stalwart Mail using the official Helm chart from Codeberg and got it running in our dev Kubernetes cluster. Everything seems to spin up fine services are up and no obvious errors on the surface.

But when I tried connecting Twake Mail to use Stalwart as the backend, I hit a roadblock:

"Unexpected error: Failed to fetch" shows up on the Twake login screen.

We didn’t make many changes to the chart — mostly just some tweaks for Ingress and secrets. I wanted to ask

What could be causing this error?

Are there any known steps or configs needed to make Twake and Stalwart work together?

Anything I should double-check in the Helm values?

I’ve attached a screenshot of the error for context.

Really appreciate any help or pointers 🙏
Thanks a lot!

[mdecimus]

Hi,

Try setting the log level to trace to find out which requests is TWake sending to Stalwart. If you can't find any meaningful requests then contact the TWake developers for assistance debugging the issue.

[Nweke-cloud]

HI Maurus Decimus, I hope this message finds you well. We’ve been working on deploying Stalwart Mail alongside Twake, with the goal of enabling webmail access. However, we run into some persistent issues connecting Twake to the JMAP endpoint. Despite thoroughly reviewing the configuration, the problem remains unresolved. We’ve reached out to the Twake developers for further assistance on that front. In the meantime, our team has decided to prioritize getting *Stalwart Mail properly integrated with Keycloak for 10 users*. Rather than continuing to troubleshoot this internally, we’d prefer to have it set up directly by your team. Could you please share: 1. A *cost estimate* for configuring Stalwart Mail with Keycloak for 10 users 2, The *expected timeline* for completion 3, Any specific technical requirements or details you’d need from our end We’re eager to get this integration up and running smoothly, and we would greatly appreciate your support in making it happen.

…

On Tue, Jul 29, 2025 at 6:02 PM Maurus Decimus ***@***.***> wrote: Hi, Try setting the log level to trace to find out which requests is TWake sending to Stalwart. If you can't find any meaningful requests then contact the TWake developers for assistance debugging the issue. — Reply to this email directly, view it on GitHub <#1911 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQANAM2TRRHK7Z3EDZ6MSPL3K6SIXAVCNFSM6AAAAACCIII3YWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJSGQ4TIOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[Nweke-cloud]

Hi Maurus Decimus, I hope you're doing well. I'm writing to kindly follow up on my earlier request. I’m still awaiting your response and would appreciate any updates you can share. Looking forward to hearing from you. Thank you.

…

On Mon, Aug 4, 2025 at 1:41 AM Nweke Henry ***@***.***> wrote: HI Maurus Decimus, I hope this message finds you well. We’ve been working on deploying Stalwart Mail alongside Twake, with the goal of enabling webmail access. However, we run into some persistent issues connecting Twake to the JMAP endpoint. Despite thoroughly reviewing the configuration, the problem remains unresolved. We’ve reached out to the Twake developers for further assistance on that front. In the meantime, our team has decided to prioritize getting *Stalwart Mail properly integrated with Keycloak for 10 users*. Rather than continuing to troubleshoot this internally, we’d prefer to have it set up directly by your team. Could you please share: 1. A *cost estimate* for configuring Stalwart Mail with Keycloak for 10 users 2, The *expected timeline* for completion 3, Any specific technical requirements or details you’d need from our end We’re eager to get this integration up and running smoothly, and we would greatly appreciate your support in making it happen. On Tue, Jul 29, 2025 at 6:02 PM Maurus Decimus ***@***.***> wrote: > Hi, > > Try setting the log level to trace to find out which requests is TWake > sending to Stalwart. If you can't find any meaningful requests then contact > the TWake developers for assistance debugging the issue. > > — > Reply to this email directly, view it on GitHub > <#1911 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BQANAM2TRRHK7Z3EDZ6MSPL3K6SIXAVCNFSM6AAAAACCIII3YWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJSGQ4TIOI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.*** > .com> >