Pangolin windows client: "failed to save olm credentials"

[qroac]

Describe the Bug

I just installed the pangolin windows client and logged in to my selfhosted pangolin instance.
When I try to connect, I see the following alert error: "failed to set up device credentials: failed to save olm credentials"

In the client logs, I see the following errors:

2025-12-16 09:56:24.000 [ERROR] Failed to save secret for key olm-id-uetnfswv2aq9mcu: Eine angegebene Anmeldesitzung ist nicht vorhanden. Sie wurde gegebenenfalls bereits beendet.
2025-12-16 09:56:24.000 [ERROR] Failed to save secret for key olm-secret-uetnfswv2aq9mcu: Eine angegebene Anmeldesitzung ist nicht vorhanden. Sie wurde gegebenenfalls bereits beendet.
2025-12-16 09:56:24.000 [ERROR] Failed to ensure OLM credentials: failed to save OLM credentials
2025-12-16 09:56:24.000 [ERROR] Failed to start tunnel: failed to save OLM credentials

Environment

• OS Type & Version: Windows 11
• Pangolin Version: 1.13.1
• Gerbil Version: 1.3.0
• Traefik Version: 3.6.4
• Newt Version:
• Olm Version: (if applicable) 0.1.1

To Reproduce

As windows non-admin user, but having admin credentials to authorize admin actions:

• Install pangolin client
• login to selfhosted instance
• try to connect to selfhosted instance

Expected Behavior

• pangolin client should connect

[oschwartz10612]

Hum looks like the following two log messages are indicating some sort of keyring issue maybe?

2025-12-16 09:56:24.000 [ERROR] Failed to save secret for key olm-id-uetnfswv2aq9mcu: The specified login session does not exist. It may have already been terminated.
2025-12-16 09:56:24.000 [ERROR] Failed to save secret for key olm-secret-uetnfswv2aq9mcu: The specified login session does not exist. It may have already been terminated.

You mention you are not ad administrator. Are you running the pangolin app as an administrator? If not could you try that?

[qroac]

I tried:

• right click, "Run as administrator"
• Choose the login option from menu to connect to my instance
• After logging in, tried to connect to my instance
  Result is the same

Btw: When starting pangolin client as normal user it automatically asks for admin privileges for allowing configuration changes. So it should already have elevated permissions at runtime.

[BolleoOg]

I can confirm the same issue. This is the error from pangolin when connecting the client:
2025-12-17T11:57:51+00:00 [warn]: Olm not found for client 12, skipping peer updates

[oschwartz10612]

@BolleoOg thats a separate issue from storing the credentials I think!

@miloschwartz

[BolleoOg]

I do have the same issue but this was the only log entry relating to this issue on the pangolin server.
I have added my client log.

pangolin-log-2025-12-18T132156.txt

[oschwartz10612]

Ahh yep I do see it there