Windows desktop: connection catalog stops decrypting (ElectronSafeStorageDecryptError) → no environments, empty sidebar, signed-out state#33746

opened7d agobyHHelios987

Summary

On Windows, the desktop app's encrypted connection catalog (~/.t3/userdata/connection-catalog.json) becomes unreadable some time after it was written. From then on the app loads no environments at all, including the Local environment, so Settings → Environments is empty and the sidebar shows no threads. The local server is healthy the whole time and still has its threads.

It happened on two machines a day apart:

MachineVersionWhat happened
A0.1.8 (Windows 11)After an update, the catalog was renamed to connection-catalog.json.bak-undecryptable and the app started fresh: signed out, saved environments gone.
B0.1.8 (Windows 11)The catalog was written and encrypted successfully, then failed to decrypt on every launch about an hour later. The file was left in place rather than set aside, so the app stayed stuck showing no environments.

Evidence (machine B, from desktop.trace.ndjson)

  • Two writes about 10 minutes apart: ElectronSafeStorage.encryptString → Success (catalog written).
  • Every launch starting about an hour after the last write (5 launches so far): ElectronSafeStorage.decryptString → ElectronSafeStorageDecryptError, then "Desktop connection catalog protection failed during decrypt-catalog at ….t3\userdata\connection-catalog.json"; desktop:get-connection-catalog fails.
  • The file is intact (about 3.5 KB), {"version":1,"encryptedCatalog":…}.
  • The safeStorage key file (%APPDATA%\t3code-v2\Local State) was not modified between the successful encrypt and the failed decrypts.
  • One install (%LOCALAPPDATA%\Programs\t3code, 0.1.8.0) and one server (the app-bundled one on 127.0.0.1:3773). No second data dir.
  • Also on B afterwards: t3 connect status → "Authorization: missing", and relay-client.ndjson showed "Unauthorized: Tunnel not found".

Workaround

Quit the app, rename connection-catalog.json aside, run t3 connect link, relaunch, sign in again and re-add each remote environment by hand.

Expected

  1. A catalog that decrypted fine an hour earlier keeps decrypting, with no key change on disk.
  2. If decryption does fail, the app always falls back the same way (set the file aside and start fresh, as on machine A) instead of staying stuck with no Local environment.
  3. The Local environment shows even when the catalog can't be read, since it doesn't need any saved credentials.

Questions

  • Is anything other than the Chromium Local State key involved in decrypting on Windows (for example, the DPAPI scope changing between an elevated and a non-elevated launch, or between a CLI-started and an app-started process)?
  • Machine B's last successful write may have come from a different process than the later reads. Can two processes encrypt with different keys?

This is the same problem as #8341, so I'm closing it in favour of that one. If it is different, say how and it will be reopened.