# Solving Gemini API key errors in Discourse

**URL:** https://meta.discourse.org/t/solving-gemini-api-key-errors-in-discourse/411545
**Category:** Self-hosting
**Tags:** ai
**Created:** [September 3, 2026, 4:43am UTC](https://meta.discourse.org/t/solving-gemini-api-key-errors-in-discourse/411545 "2026-09-03T04:43:15Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![satonotdead](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/satonotdead/32/447830_2.png) [@satonotdead](https://meta.discourse.org/u/satonotdead)
#### Post date: [September 4, 2026, 7:21am UTC](https://meta.discourse.org/t/solving-gemini-api-key-errors-in-discourse/411545/15 "2026-09-04T07:21:50Z")

</div>

> [@Karthik\_K1](#):
>
> @atonotdead Do you experience any latency with LiteLLM method?

Not at all, and I also used a Nginx internal proxy with a script to rotate the token login on Vertex.

LiteLLM is really good if you have plans to deploy more keys, MCP servers and want to use more LLM endpoints.

You can use almost any subscription tier as LLM API with it.

---

_[View the full topic](https://meta.discourse.org/t/solving-gemini-api-key-errors-in-discourse/411545)._