[GH-ISSUE #13515] Account sign-in errors in the ollama app #70965

Closed
opened 2026-05-04 23:35:54 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @tm-coder-484 on GitHub (Dec 17, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/13515

What is the issue?

I was trying to sign in to my ollama account because I was getting 401s trying to use cloud models, so I clicked sign in, nothing happened, then it gave me the error: Failed to get connect URL. I also have this error, but nothing in the logs: [GIN] 2025/12/16 - 22:35:29 | 200 | 224.9456ms | 127.0.0.1 | POST "/api/me"
time=2025-12-16T22:35:31.290+10:00 level=ERROR source=routes.go:1749 msg="something went wrong, please see the ollama server logs for details" I have also redone the ollama signin and private key, but no change. Testing api/me with curl returns null even though I have a public key. I also fully uninstalled and re-installed ollama, and downgraded to 0.13.2 and back up again, but the best improvement I could get was being able to click a signin link, but the link opened that app and didn't sign me in.

Image

Relevant log output

Other logs have no errors apart from this one: [GIN] 2025/12/16 - 22:35:20 | 200 |     233.535ms |       127.0.0.1 | POST     "/api/me"
time=2025-12-16T22:35:22.315+10:00 level=ERROR source=routes.go:1749 msg="something went wrong, please see the ollama server logs for details"

OS

Windows

GPU

Intel iGPU (not being used by ollama)

CPU

Intel

Ollama version

0.13.4 but I think it started in 0.13.3

Originally created by @tm-coder-484 on GitHub (Dec 17, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/13515 ### What is the issue? I was trying to sign in to my ollama account because I was getting 401s trying to use cloud models, so I clicked sign in, nothing happened, then it gave me the error: Failed to get connect URL. I also have this error, but nothing in the logs: [GIN] 2025/12/16 - 22:35:29 | 200 | 224.9456ms | 127.0.0.1 | POST "/api/me" time=2025-12-16T22:35:31.290+10:00 level=ERROR source=routes.go:1749 msg="something went wrong, please see the ollama server logs for details" I have also redone the ollama signin and private key, but no change. Testing api/me with curl returns null even though I have a public key. I also fully uninstalled and re-installed ollama, and downgraded to 0.13.2 and back up again, but the best improvement I could get was being able to click a signin link, but the link opened that app and didn't sign me in. <img width="1117" height="214" alt="Image" src="https://github.com/user-attachments/assets/765da923-6338-40af-8ed0-cbcbf738743d" /> ### Relevant log output ```shell Other logs have no errors apart from this one: [GIN] 2025/12/16 - 22:35:20 | 200 | 233.535ms | 127.0.0.1 | POST "/api/me" time=2025-12-16T22:35:22.315+10:00 level=ERROR source=routes.go:1749 msg="something went wrong, please see the ollama server logs for details" ``` ### OS Windows ### GPU Intel iGPU (not being used by ollama) ### CPU Intel ### Ollama version 0.13.4 but I think it started in 0.13.3
GiteaMirror added the appbug labels 2026-05-04 23:35:54 -05:00
Author
Owner

@tm-coder-484 commented on GitHub (Dec 18, 2025):

Yeah, A day later I randomly got signed in.

<!-- gh-comment-id:3672514695 --> @tm-coder-484 commented on GitHub (Dec 18, 2025): Yeah, A day later I randomly got signed in.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#70965