Windows Desktop 1.3.3 repeatedly fails with “Cloudflare sign-in expired

[Steverino17]

I’m trying to install Second Brain Desktop 1.3.3 on Windows using the advertised simple setup.

Cloudflare sign-in succeeds and Wrangler authorization succeeds.

Setup then completes:

✅ Creating private space
✅ Building memory store
✅ Turning on smart recall

But always fails on:

❌ Finishing up

with:

“Cloudflare sign-in expired.”

I retried, signed out/in, reauthorized Cloudflare, and restarted the setup from scratch with a new Second Brain password. Same result every time.

After signing back in, the app also reported that it could not find a Second Brain in that Cloudflare space.

Is this a known issue with Desktop 1.3.3, and is there a straightforward fix that does not require manually configuring Cloudflare/Workers/Wrangler?

Thanks!

[rahilp]

Hi @Steverino17, sorry you hit this, and thanks for the clear report. You've done all the right things on your end; this looks like a bug on ours.

What's happening: "Cloudflare sign-in expired" at the Finishing up step is a misleading message. Your Cloudflare sign-in is fine. That message can also appear when the freshly deployed brain doesn't yet recognize the password that was just set for it (for example, if an earlier setup attempt left a partial brain behind, or the new deployment hasn't fully propagated yet). The app currently treats that as fatal instead of waiting and retrying, which is the bug we need to fix.

A couple of things that would help us narrow it down:

1. Did anything touch this Cloudflare account before? Any earlier Second Brain setup attempt (even one that failed), or any Workers-related project created in this account, even by another app?
2. Same Cloudflare account each time? When you retried and signed in again, was it definitely the same account as the first attempt?
3. Please try Desktop 1.4.0, released today. It includes installer changes since 1.3.3. If it still fails at Finishing up, let us know.

If 1.4.0 doesn't fix it, we'll ship a fix that makes setup wait through propagation instead of failing fast, and report what actually went wrong rather than blaming your sign-in.

[Steverino17]

I updated to Desktop 1.4.1 and ran setup again. It failed at the same two steps and still displays “Cloudflare sign-in expired”—the exact error 1.4.1 was supposed to eliminate.

The fix has not resolved my issue.

[rahilp]

Thanks for the update @Steverino17 -- are you able to share your logs. If you're on a mac, they should be available at ~/Library/Logs/Second\ Brain/second-brain.log

That may help us narrow what the issue is

[Steverino17]

I am on windows...

[rahilp]

In windows, the logs will be located at

%LOCALAPPDATA%\Second Brain\logs\second-brain.log

[Steverino17]

this is what we found : [1787529152411 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529154862 WARN second_brain_desktop_lib::commands] provisioning failed: Cloudflare sign-in expired
[1787529177558 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529179677 WARN second_brain_desktop_lib::commands] provisioning failed: Cloudflare sign-in expired
[1787529388865 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529392770 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529393760 WARN second_brain_desktop_lib::commands] provisioning failed: Cloudflare sign-in expired
[1787529402791 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529404646 WARN second_brain_desktop_lib::commands] provisioning failed: Cloudflare sign-in expired
[1787529435866 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529437704 WARN second_brain_desktop_lib::commands] provisioning failed: Cloudflare sign-in expired
[1787529627768 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529632990 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529634035 WARN second_brain_desktop_lib::commands] provisioning failed: Cloudflare sign-in expired
[1787529659512 INFO second_brain_desktop_lib::cf::api] deploy_worker: 3708686 bytes of code, 999 bytes of metadata, 6 bindings
[1787529661702 WARN second_brain_desktop_lib::commands] provisioning failed: Cloudflare sign-in expired

[rahilp]

Hi @Steverino17, good news: Desktop 1.4.1 is out and it fixes this.

We were able to reproduce and root-cause what you hit. The short version: "Cloudflare sign-in expired" was the wrong explanation. What actually happened at that step is that the freshly deployed brain briefly refused the password it was being set up with (new deployments take a few seconds to reach every server on Cloudflare's edge, and during that window an older copy can still be answering). The app used to give up on the first refusal and show the sign-in message, which sent you re-authorizing a login that was never the problem.

What changed in 1.4.1:

1. Setup now waits through that window instead of failing on the first refusal
2. If setup genuinely cannot verify the password, the error says exactly that instead of blaming your Cloudflare sign-in
3. The app now keeps a small diagnostic log file, so if anything ever fails again there is real evidence instead of just a screen

Please update to 1.4.1 (the app should offer it automatically, or grab it from the Releases page) and try setup again. If it fails, open a new issue and mention your log file location and we will take it from there: %LOCALAPPDATA%\Second Brain\logs\second-brain.log

One note since you will see it in that log: it deliberately redacts your brain's address and any credentials before writing, so it is safe to share.