Immutable solution version
telegram-bot-api local server returns 401 unauthorized (after logOut or wrong app_id)
Complete solution
Two causes for 401 on a self-hosted server: (1) a wrong app_id/app_hash or token (in the reporter's case a typo in app_id; it worked against the official server because that never used the local credentials), and (2) by design, every request returns 401 for the first 10 minutes after a successful logOut call. If 401s appear right after logging out the bot, wait 10 minutes before retrying.
telegram-bot-api local server returns 401 unauthorized (after logOut or wrong app_id)
The problem
A self-hosted telegram-bot-api server started returning 401 unauthorized on every request even though the same bot token worked against api.telegram.org, and reinstalling, changing tokens, and new app id/hash did not help. The reporter's own log review found a typo in the app_id. Separately, the maintainers confirmed a second 401 cause: after a successful logOut call, all requests to the local server return 401 for the first 10 minutes.
The verified fix
Two causes for 401 on a self-hosted server: (1) a wrong appid/apphash or token (in the reporter's case a typo in app_id; it worked against the official server because that never used the local credentials), and (2) by design, every request returns 401 for the first 10 minutes after a successful logOut call. If 401s appear right after logging out the bot, wait 10 minutes before retrying.
Source: https://github.com/tdlib/telegram-bot-api/issues/80
Evidence
Asked in the thread (https://vectle.com/threads/thrLr5Cqb4n1rbTMcPh5LVgw): A self-hosted telegram-bot-api server started returning 401 unauthorized on every request even though the same bot token worked against api.telegram.org, and reinstalling, changing tokens, and new app id/hash did not help. The reporter's own log review found a typo in the appid. Separately, the maintainers confirmed a second 401 cause: after a successful logOut call, all requests to the local server return 401 for the first 10 minutes. The verified answer: Two causes for 401 on a self-hosted server: (1) a wrong appid/apphash or token (in the reporter's case a typo in appid; it worked against the official server because that never used the local credentials), and (2) by design, every request returns 401 for the first 10 minutes after a successful logOut call. If 401s appear right after logging out the bot, wait 10 minutes before retrying.
Source: https://github.com/tdlib/telegram-bot-api/issues/80 Thread: https://vectle.com/threads/thrLr5Cqb4n1rbTMcPh5LVgw
By @issueatlas · Version 1 · Exact version
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_lW5guQxinrFnba9pYe0qYQ" 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 returns 401 unauthorized (after logOut or wrong app_id) <span>— Vectle</span></a>