> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/possible-errors/the-telegram-bot-does-not-respond-or-the-button-leads-to-the-wrong-place.md).

# The Telegram bot does not respond or the button leads to the wrong place

Bot is silent, does not show the Mini App button, the button opens an old address, or the catalog does not open.

### Symptoms

* bot does not respond to `/start`;
* Mini App button is missing;
* the button leads to an old link;
* the new bot opens 404;
* one language version opens instead of another;
* after changing the token, the bot works unstably.

### Possible causes

{% tabs %}
{% tab title="Token" %}
An incorrect Telegram bot token is specified, or the token was revoked in BotFather.
{% endtab %}

{% tab title="Multiple versions" %}
The same token is being used in several language versions.
{% endtab %}

{% tab title="Mini App" %}
Telegram saved the old button or did not accept the new URL.
{% endtab %}

{% tab title="Domain" %}
Mini App leads to a domain or language path that is not set up on the server.
{% endtab %}
{% endtabs %}

### What to check

Check the status of the bot service:

```bash
sudo /opt/bloggers_platform/apps/ru/manager.sh status
sudo /opt/bloggers_platform/apps/ru/manager.sh logs bot
```

Check that the storefront opens in the browser:

```
https://example.com/bloggers/ru/
```

### How to fix it

1. For each language version, use a separate Telegram bot and a separate token.
2. Check the token in the admin panel of the required version.
3. Save the token again so the platform updates the bot settings.
4. Restart the bot service:

```bash
sudo /opt/bloggers_platform/apps/ru/manager.sh restart
```

{% hint style="info" %}
If the old button remains in the old bot, this is not always critical. The main thing is that the new active bot receives the correct Mini App link for the current language version.
{% endhint %}

### When to contact support

If the new bot still opens 404 after saving the token, logs are needed `bot`, the current version language, and the actual link opened by the button.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/possible-errors/the-telegram-bot-does-not-respond-or-the-button-leads-to-the-wrong-place.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.