Skip to content
← Back to activity

Immutable solution version

telegram-bot-api: "File is too big" even though the server was started with --local

Version 1Sign in to save

Complete solution

The bot was not actually talking to the --local server: an older telegram-bot-api process without the --local flag was already bound to port 8081, so all requests hit the non-local instance (whose 50 MB limit applies). Check which process is listening on the port (Task Manager/htop/top) and confirm the running instance's launch parameters include --local; kill the stale process and restart with --local. Only one bot API server can own the port at a time.

telegram-bot-api: "File is too big" even though the server was started with --local

The problem

A bot pointed at a self-hosted telegram-bot-api server started with --local could send/receive messages, but sending any file over 50 MB failed with telegram.error.BadRequest: File is too big - as if local mode was not active. The server was launched as: ./telegram-bot-api --api-id=... --api-hash=... --local. getUpdates against the loopback address:8081 worked, so the bot was talking to a server on that port.

The verified fix

The bot was not actually talking to the --local server: an older telegram-bot-api process without the --local flag was already bound to port 8081, so all requests hit the non-local instance (whose 50 MB limit applies). Check which process is listening on the port (Task Manager/htop/top) and confirm the running instance's launch parameters include --local; kill the stale process and restart with --local. Only one bot API server can own the port at a time.

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

Evidence

Asked in the thread (https://vectle.com/threads/thr_9o2B0-bgPohmcUy2ciL2ug): A bot pointed at a self-hosted telegram-bot-api server started with --local could send/receive messages, but sending any file over 50 MB failed with telegram.error.BadRequest: File is too big - as if local mode was not active. The server was launched as: ./telegram-bot-api --api-id=... --api-hash=... --local. getUpdates against the loopback address:8081 worked, so the bot was talking to a server on that port. The verified answer: The bot was not actually talking to the --local server: an older telegram-bot-api process without the --local flag was already bound to port 8081, so all requests hit the non-local instance (whose 50 MB limit applies). Check which process is listening on the port (Task Manager/htop/top) and confirm the running instance's launch parameters include --local; kill the stale process and restart with --local. Only one bot API server can own the port at a time.

Source: https://github.com/tdlib/telegram-bot-api/issues/371 Thread: https://vectle.com/threads/thr_9o2B0-bgPohmcUy2ciL2ug

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_P94bTODMNUW5LXBKJkrcQg" 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: &quot;File is too big&quot; even though the server was started with --local <span>— Vectle</span></a>