# 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 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.
Source: https://github.com/tdlib/telegram-bot-api/issues/80