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

[GH-ISSUE #15741] Kimi models require pro ? #56547

New Issue
Open
opened 2026-04-29 10:59:48 -05:00 by GiteaMirror · 15 comments
GiteaMirror commented 2026-04-29 10:59:48 -05:00
Owner
Copy Link

Originally created by @Azecko on GitHub (Apr 22, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15741

What is the issue?

I've always used kimi-k2.5:cloud for Ollama. Mainly with the Hermes Agent.

Today, when I tried to message my Hermes, I got the error HTTP 403: Error code: 403 - {'error': 'this model requires a subscription, upgrade for access: https://ollama.com/upgrade.

I tried to prompt kimi using just ollama run, same thing.
Using the new Kimi CLI from v0.21.1 (because I also tried to update Ollama), same thing.
With kimi-k2.6:cloud, I also get the same error.
But I do not get this error when I try with other cloud models, like gemma.

I'm correctly signed in when I run ollama signin.

My Cloud usage for this week is at 37%, and 0% for the session at the time I write this issue.

Am I the only one who get this error ? Is there something that I missed and now Kimi models require Ollama pro ?

Relevant log output

Error: 403 Forbidden: this model requires a subscription, upgrade for access: https://ollama.com/upgrade

OS

Linux

GPU

No response

CPU

Intel

Ollama version

0.21.1

Originally created by @Azecko on GitHub (Apr 22, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15741 ### What is the issue? I've always used `kimi-k2.5:cloud` for Ollama. Mainly with the Hermes Agent. Today, when I tried to message my Hermes, I got the error `HTTP 403: Error code: 403 - {'error': 'this model requires a subscription, upgrade for access: https://ollama.com/upgrade`. I tried to prompt kimi using just `ollama run`, same thing. Using the new Kimi CLI from `v0.21.1` (because I also tried to update Ollama), same thing. With `kimi-k2.6:cloud`, I also get the same error. But I do not get this error when I try with other cloud models, like gemma. I'm correctly signed in when I run `ollama signin`. My Cloud usage for this week is at 37%, and 0% for the session at the time I write this issue. Am I the only one who get this error ? Is there something that I missed and now Kimi models require Ollama pro ? ### Relevant log output ```shell Error: 403 Forbidden: this model requires a subscription, upgrade for access: https://ollama.com/upgrade ``` ### OS Linux ### GPU _No response_ ### CPU Intel ### Ollama version 0.21.1
GiteaMirror added the bug label 2026-04-29 10:59:48 -05:00
GiteaMirror commented 2026-04-29 10:59:56 -05:00
Author
Owner
Copy Link

@sruizcarmona commented on GitHub (Apr 22, 2026):

Same here, no updates from ollama anywhere...

<!-- gh-comment-id:4296487030 --> @sruizcarmona commented on GitHub (Apr 22, 2026): Same here, no updates from ollama anywhere...
GiteaMirror commented 2026-04-29 11:00:00 -05:00
Author
Owner
Copy Link

@AngelSanchezB commented on GitHub (Apr 22, 2026):

Same here since last night...

<!-- gh-comment-id:4297472028 --> @AngelSanchezB commented on GitHub (Apr 22, 2026): Same here since last night...
GiteaMirror commented 2026-04-29 11:00:02 -05:00
Author
Owner
Copy Link

@ACheshirov commented on GitHub (Apr 22, 2026):

They disabled for free users almost all big models.

<!-- gh-comment-id:4297502872 --> @ACheshirov commented on GitHub (Apr 22, 2026): They disabled for free users almost all big models.
GiteaMirror commented 2026-04-29 11:00:03 -05:00
Author
Owner
Copy Link

@LeoLP1 commented on GitHub (Apr 22, 2026):

@ACheshirov Is that something you think, or did you read it somewhere?

<!-- gh-comment-id:4297696517 --> @LeoLP1 commented on GitHub (Apr 22, 2026): @ACheshirov Is that something you think, or did you read it somewhere?
GiteaMirror commented 2026-04-29 11:00:04 -05:00
Author
Owner
Copy Link

@ACheshirov commented on GitHub (Apr 22, 2026):

@LeoLP1 I tried a lot of their large cloud models - all of them are disabled for free users.

People on their Discord server says that it's not confirmed that the restrictions are permanent...
However, considering the number of people with paid subscriptions who have complained about interruptions and very slow responses from the models, this free tier restriction was expected...

More likely, they will think of another way to give access to free users that is more difficult to abuse.

<!-- gh-comment-id:4298304095 --> @ACheshirov commented on GitHub (Apr 22, 2026): @LeoLP1 I tried a lot of their large cloud models - all of them are disabled for free users. People on their Discord server says that it's not confirmed that the restrictions are permanent... However, considering the number of people with paid subscriptions who have complained about interruptions and very slow responses from the models, this free tier restriction was expected... More likely, they will think of another way to give access to free users that is more difficult to abuse.
GiteaMirror commented 2026-04-29 11:00:05 -05:00
Author
Owner
Copy Link

@geerdwedda-create commented on GitHub (Apr 22, 2026):

Even me still as pro user, non stop disconnecting, time outs, model wont do anything, Ollama sucks

<!-- gh-comment-id:4298755540 --> @geerdwedda-create commented on GitHub (Apr 22, 2026): Even me still as pro user, non stop disconnecting, time outs, model wont do anything, Ollama sucks
GiteaMirror commented 2026-04-29 11:00:06 -05:00
Author
Owner
Copy Link

@asahu commented on GitHub (Apr 23, 2026):

Same here :(

<!-- gh-comment-id:4301552518 --> @asahu commented on GitHub (Apr 23, 2026): Same here :(
GiteaMirror commented 2026-04-29 11:00:07 -05:00
Author
Owner
Copy Link

@Azecko commented on GitHub (Apr 23, 2026):

I'm glad to see that I'm not the only one encountering this issue.
I hope that we will have a communication asap about the situation from the Ollama team, because this is really weird.

<!-- gh-comment-id:4302244544 --> @Azecko commented on GitHub (Apr 23, 2026): I'm glad to see that I'm not the only one encountering this issue. I hope that we will have a communication asap about the situation from the Ollama team, because this is really weird.
GiteaMirror commented 2026-04-29 11:00:08 -05:00
Author
Owner
Copy Link

@25kgozon commented on GitHub (Apr 23, 2026):

Free models got pay walled bc some users were abusing them too much apparently. I'm having the same 403 issue still too

<!-- gh-comment-id:4304746801 --> @25kgozon commented on GitHub (Apr 23, 2026): Free models got pay walled bc some users were abusing them too much apparently. I'm having the same 403 issue still too
GiteaMirror commented 2026-04-29 11:00:09 -05:00
Author
Owner
Copy Link

@MCOoost commented on GitHub (Apr 23, 2026):

Same issue here. Both kimi-k2.5:cloud and kimi-k2.6:cloud were working perfectly fine for me yesterday (April 22), and today they both return:

Error: this model requires a subscription, upgrade for access

I'm still well within my free cloud usage limits, and other cloud models (e.g., Gemma) continue to work without any issues on the same account.

I completely understand that business models evolve, but the lack of transparency here is disappointing. A silent, unannounced paywall on models that were freely accessible 24 hours ago creates a frustrating experience for users who have come to rely on them. If a subscription is now required, that is fair, but some advance notice or a clear changelog would have been greatly appreciated.

Could the team please clarify:

  • Was this an intentional change for Kimi models specifically?
  • Is this a temporary issue or a permanent requirement going forward?

Thank you for the otherwise excellent work on Ollama.

<!-- gh-comment-id:4305672276 --> @MCOoost commented on GitHub (Apr 23, 2026): Same issue here. Both kimi-k2.5:cloud and kimi-k2.6:cloud were working perfectly fine for me yesterday (April 22), and today they both return: ` Error: this model requires a subscription, upgrade for access ` I'm still well within my free cloud usage limits, and other cloud models (e.g., Gemma) continue to work without any issues on the same account. I completely understand that business models evolve, but the lack of transparency here is disappointing. A silent, unannounced paywall on models that were freely accessible 24 hours ago creates a frustrating experience for users who have come to rely on them. If a subscription is now required, that is fair, but some advance notice or a clear changelog would have been greatly appreciated. Could the team please clarify: - Was this an intentional change for Kimi models specifically? - Is this a temporary issue or a permanent requirement going forward? Thank you for the otherwise excellent work on Ollama.
GiteaMirror commented 2026-04-29 11:00:10 -05:00
Author
Owner
Copy Link

@siathalysedI commented on GitHub (Apr 23, 2026):

Same issue here, kimi-k2.6-cloud and I got:
Error code: 403 - {'error': 'this model requires a subscription, upgrade for access: https://ollama.com/upgrade (ref: 9d6c4cd4-b628-4882-b652-f71f638e117c)'}

I can't understand why this happens and with no further notice and such obscured information about it.

<!-- gh-comment-id:4306469178 --> @siathalysedI commented on GitHub (Apr 23, 2026): Same issue here, kimi-k2.6-cloud and I got: `Error code: 403 - {'error': 'this model requires a subscription, upgrade for access: https://ollama.com/upgrade (ref: 9d6c4cd4-b628-4882-b652-f71f638e117c)'}` I can't understand why this happens and with no further notice and such obscured information about it.
GiteaMirror commented 2026-04-29 11:00:11 -05:00
Author
Owner
Copy Link

@dnky-1 commented on GitHub (Apr 24, 2026):

same here trying to use glm-5.1 model

<!-- gh-comment-id:4315712302 --> @dnky-1 commented on GitHub (Apr 24, 2026): same here trying to use glm-5.1 model
GiteaMirror commented 2026-04-29 11:00:11 -05:00
Author
Owner
Copy Link

@FALLEN-01 commented on GitHub (Apr 25, 2026):

I am facing the same issues

<!-- gh-comment-id:4320164129 --> @FALLEN-01 commented on GitHub (Apr 25, 2026): I am facing the same issues
GiteaMirror commented 2026-04-29 11:00:13 -05:00
Author
Owner
Copy Link

@mahiarirani commented on GitHub (Apr 25, 2026):

same issue trying to use kimi-k2.6:cloud

<!-- gh-comment-id:4320598123 --> @mahiarirani commented on GitHub (Apr 25, 2026): same issue trying to use kimi-k2.6:cloud
GiteaMirror commented 2026-04-29 11:00:14 -05:00
Author
Owner
Copy Link

@freerider7777 commented on GitHub (Apr 26, 2026):

"There's no such thing as a free lunch."

<!-- gh-comment-id:4322174298 --> @freerider7777 commented on GitHub (Apr 26, 2026): "There's no such thing as a free lunch."
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#56547
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?