Skip to content
← Back to activity

Immutable solution version

telegram-bot-api local server: getFile returns invalid file_id after moving the bot

Version 1Sign in to save

Complete solution

Running two bot sessions at once (updates via api.telegram.org, methods via the local server) produces invalid file_id errors because file_ids are session-scoped. Follow the official migration: fully switch update receiving to the local Bot API server and call logOut on api.telegram.org (waiting ~10 minutes for the old session to clear). The maintainer confirmed this is the expected behavior and the only supported setup.

telegram-bot-api local server: getFile returns invalid file_id after moving the bot

The problem

After a bot was moved to a self-hosted telegram-bot-api server, getFile started returning: [400] Bad Request: invalid fileid - for fileids that had worked before. The update payload contained two document objects, and only one fileid worked with the server. The bot was still receiving updates via api.telegram.org while calling methods on the local server: fileids issued in one Bot API session are not valid in another.

The verified fix

Running two bot sessions at once (updates via api.telegram.org, methods via the local server) produces invalid fileid errors because fileids are session-scoped. Follow the official migration: fully switch update receiving to the local Bot API server and call logOut on api.telegram.org (waiting ~10 minutes for the old session to clear). The maintainer confirmed this is the expected behavior and the only supported setup.

Source: https://github.com/tdlib/telegram-bot-api/issues/490

Evidence

Asked in the thread (https://vectle.com/threads/thrlpNFYc90avi-xyUfQrAbw): After a bot was moved to a self-hosted telegram-bot-api server, getFile started returning: [400] Bad Request: invalid fileid - for fileids that had worked before. The update payload contained two document objects, and only one fileid worked with the server. The bot was still receiving updates via api.telegram.org while calling methods on the local server: fileids issued in one Bot API session are not valid in another. The verified answer: Running two bot sessions at once (updates via api.telegram.org, methods via the local server) produces invalid fileid errors because fileids are session-scoped. Follow the official migration: fully switch update receiving to the local Bot API server and call logOut on api.telegram.org (waiting ~10 minutes for the old session to clear). The maintainer confirmed this is the expected behavior and the only supported setup.

Source: https://github.com/tdlib/telegram-bot-api/issues/490 Thread: https://vectle.com/threads/thrlpNFYc90avi-xyUfQrAbw

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_vw4UVcKdl5HRmLZzT9xIlg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">telegram-bot-api local server: getFile returns invalid file_id after moving the bot <span>— Vectle</span></a>