“Signed in, but the credentials could not be saved”: OS keychain in Senzoukria
With “Save my credentials” ticked, Senzoukria stores your password in the operating system keychain. If that write fails, you are still signed in, and the app shows the real error for a moment instead of pretending the credentials were saved.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- Message
- “Signed in, but the credentials could not be saved: {error}”
- Checkbox
- “Save my credentials (OS keychain)”, ticked by default
- Storage
- Windows Credential Manager on Windows, Keychain on macOS, Secret Service on Linux
- Consequence
- The next start asks for the password again
What you see
Right after a successful sign-in, the card shows “Signed in, but the credentials could not be saved: {error}” for about two seconds, then the app opens. At the next start the form is empty or not submitted automatically.
Why it happens
The password goes to the operating system’s credential store, never to a file. When that store refuses the write, the sign-in itself still succeeded, so the app lets you in and surfaces the error rather than letting “remember me” silently do nothing. Typical causes: a locked or unavailable keyring on Linux, a Credential Manager policy on a managed Windows machine, or security software blocking access. Broker credentials and API keys use the same keychain, so the same cause can affect them.
How to fix it
- On Linux, make sure a Secret Service keyring is running and unlocked in your session.
- On a managed Windows machine, ask your administrator whether apps may write to Credential Manager.
- Sign out and sign in again with the box ticked to retry the write.
- If saving stays impossible, untick the box and type the password at each start.
What it is not
- Not a failed sign-in: you are signed in.
- Not a password problem.
When to contact support
If the steps above do not change anything, send the case from Menu → Report a problem (it works without being signed in), or ask on the Senzoukria Discord. Copy the error shown after “could not be saved:” and your operating system version.
Related pages
In the same section
- News source rate-limited
- Sign in in the main window
- Import stopped: memory limit
- Script stopped after 2000 ms
- System name not on the gateway
- Connect needs a saved password
- History refused (rp_code 13)
- Replay load refused (rp_code 13)
This page in other languages
Frequently asked questions
- Is my password written to a file if the keychain fails?
- No. The app never writes it to a file; it simply cannot remember it.
- Does signing out delete the saved credentials?
- Signing out keeps the keychain entry. Untick the box at the next sign-in to clear it.