> For the complete documentation index, see [llms.txt](https://docs.mobb.ai/mobb-user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobb.ai/mobb-user-docs/common-troubleshooting-scenarios/broker-token-expired.md).

# Broker & Tokens - Expired broker token

{% hint style="warning" %}
This scenario applies **only to on-premises deployments** that use the [Mobb Broker](/mobb-user-docs/more-info/mobb-broker.md) to connect to a self-hosted SCM (GitLab, GitHub, or Azure DevOps).
{% endhint %}

**Symptoms**

* Fix analysis or pull-request creation that used to work suddenly fails.
* The failure starts roughly 90 days after the broker was last set up or rotated.

**Likely cause**

By default, a Mobb broker token expires **92 days (about three months) after it is created**. When it expires, the encrypted tunnel between your SCM and Mobb can no longer be established, so Mobb loses access to your repositories.

**Resolution**

1. Check when your current token was created (and therefore when it expires) using `GET /api/rest/getbrokerconfigurations`.
2. Generate a new token with `POST /api/rest/createbrokerapitoken`.
3. Set the new value in the `FRP_BROKER_AUTH_TOKEN` environment variable of your broker container.

Full steps are in [Mobb Broker Token Rotation](/mobb-user-docs/more-info/mobb-broker/mobb-broker-token-rotation.md).

{% hint style="info" %}
Set a calendar reminder to rotate tokens a few days before the 92-day expiry so fixes are never interrupted. Still stuck? Contact <support@mobb.ai>.
{% endhint %}