From 05ac6d7a3b7c0546d92c598c7d1c74a3ad4ba28c Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Fri, 22 May 2026 22:55:15 +0300 Subject: [PATCH] Make sure network.api_id is provided as an integer to mautrix-telegram Otherwise "login phone" results in: "Failed to submit input: send code: rpc error code 400: API_ID_INVALID" --- .../matrix-bridge-mautrix-telegram/templates/config.yaml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2 index 98ba72461..55f5ff0fe 100644 --- a/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2 @@ -2,7 +2,7 @@ # Network-specific config options network: # Get your own API keys at https://my.telegram.org/apps - api_id: {{ matrix_mautrix_telegram_api_id | to_json }} + api_id: {{ matrix_mautrix_telegram_api_id | int | to_json }} api_hash: {{ matrix_mautrix_telegram_api_hash | to_json }} # Device info shown in the Telegram device list.