github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #12384] Unable to signin #8226

New Issue
Closed
opened 2026-04-12 20:43:10 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 20:43:10 -05:00
Owner
Copy Link

Originally created by @it-s on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12384

What is the issue?

Hi team.
I have an active subscription and trying to use in locally on my Fedora Linux system. My ollama server/client is at ollama version is 0.12.0.
When I do ollama signin I get a message to go to a URL. After I go to that URL it tells me "Device Connected Successfully", but if I now try to use any of the cloud models I get
"You need to be signed in to Ollama to run Cloud models.

To sign in, navigate to:
"
followed by the same link I just visited.

Relevant log output

No errors or warnings in journalctl log

OS

Linux

GPU

Nvidia

CPU

AMD

Ollama version

0.12.0

Originally created by @it-s on GitHub (Sep 23, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12384 ### What is the issue? Hi team. I have an active subscription and trying to use in locally on my Fedora Linux system. My ollama server/client is at `ollama version is 0.12.0`. When I do `ollama signin` I get a message to go to a URL. After I go to that URL it tells me "Device Connected Successfully", but if I now try to use any of the cloud models I get "You need to be signed in to Ollama to run Cloud models. To sign in, navigate to: " followed by the same link I just visited. ### Relevant log output ```shell No errors or warnings in journalctl log ``` ### OS Linux ### GPU Nvidia ### CPU AMD ### Ollama version 0.12.0
GiteaMirror added the bug label 2026-04-12 20:43:10 -05:00
GiteaMirror commented 2026-04-12 20:43:14 -05:00
Author
Owner
Copy Link

@billygrant24 commented on GitHub (Sep 23, 2025):

Same version, same issue. It appears to be a bug resolved in https://github.com/ollama/ollama/releases/tag/v0.12.1

<!-- gh-comment-id:3325500048 --> @billygrant24 commented on GitHub (Sep 23, 2025): Same version, same issue. It appears to be a bug resolved in https://github.com/ollama/ollama/releases/tag/v0.12.1
GiteaMirror commented 2026-04-12 20:43:16 -05:00
Author
Owner
Copy Link

@it-s commented on GitHub (Sep 23, 2025):

@billygrant24 thanks for quick answer. Updating to latest ollama 0.12.1 worked. The funny thing is that I updated earlier today, and somehow managed to get v0.12.0 :D Thanks

<!-- gh-comment-id:3325527423 --> @it-s commented on GitHub (Sep 23, 2025): @billygrant24 thanks for quick answer. Updating to latest ollama 0.12.1 worked. The funny thing is that I updated earlier today, and somehow managed to get v0.12.0 :D Thanks
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#8226
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?