CalderaDock shows a sign-in loop

When CalderaDock on Linux accepts the password but returns to the sign-in screen, the issue is usually caused by a corrupted local session file. Renaming that file forces CalderaDock to create a fresh one and usually restores login.

Issue Summary

Some users can enter the correct Caldera account credentials, but CalderaDock does not complete the login. Instead, it shows an error like “An unknown error occurred while signing in” and stays on the sign-in screen.

This issue was confirmed on Linux, Mac, Windows and was resolved by resetting the local authentication file stored in the CalderaDock config folder.

Cause

CalderaDock stores login/session information locally in a file named storage.json. When that file becomes corrupted or invalid, the app may fail to keep the user signed in even after successful authentication.

Resolution

Rename the local storage.json file so CalderaDock can generate a new one the next time the user signs in.

Steps For Linux

1. Open a Terminal.

2. Go to the CalderaDock configuration folder:

   cd ~/.config/CalderaDock

3. Check that the file exists:

   ls

4. Rename the file:

   mv storage.json storage.json1

5. Start CalderaDock again.
6. Sign in with the user’s Caldera account credentials.

7. Confirm that the login completes successfully.

   

    

    

Steps For Windows

1. Close CalderaDock.
2. Open File Explorer and navigate to:

3. C:\Users\<username>\AppData\Roaming\CalderaDock

4. (If the AppData folder is hidden, enable View → Hidden items in File Explorer.)

5. Locate the storage.json file.
6. Rename it to storage.json1 (or any backup name).
7. Launch CalderaDock.
8. Sign in again with your Caldera account credentials.

Steps For Mac

1. Close CalderaDock.
2. In Finder, press ⌘ + Shift + G (Go to Folder).
3. Enter the following path:

~/Library/Application Support/CalderaDock

4. Locate the storage.json file.
5. Rename it to storage.json1 (or any backup name).
6. Launch CalderaDock.
7. Sign in again with your Caldera account credentials.

Expected Result:
CalderaDock automatically creates a new storage.json file, and the user should be able to sign in successfully.

Important Note

Renaming the file keeps a backup copy, so the original data is not lost. If needed, the backup can be deleted later after the issue is confirmed fixed.

Example

If the file path is /home/username/.config/CalderaDock/storage.json, rename it to /home/username/.config/CalderaDock/storage.json1, then reopen CalderaDock and log in again.

When To Escalate

If the login issue continues after renaming storage.json, collect the CalderaDock version, OS version, and the contents of ~/.config/CalderaDock, then escalate to support for further investigation.