Deployment successful, login account

[lambq]

2024-01-18 11:39:21] [warning] The database settings have changed! [2024-01-18 11:39:21] [warning] Connecting to DC 1 [2024-01-18 11:39:21] [warning] Resetting session in DC 1.0... [2024-01-18 11:39:21] [warning] Connecting to DC 1.0 via tcp://149.154.175.57:443 main DC 1, via ipv4 using AbridgedStream => BufferedRawStream => DefaultStream [2024-01-18 11:39:21] [warning] Connected to DC 1.0 via tcp://149.154.175.57:443 main DC 1, via ipv4 using AbridgedStream => BufferedRawStream => DefaultStream! [2024-01-18 11:39:22] [warning] Received bad_msg_notification: incorrect server salt (in this case, the bad_server_salt response is received with the correct salt, and the message is to be re-sent with it) [2024-01-18 11:39:22] [warning] Received bad_msg_notification: incorrect server salt (in this case, the bad_server_salt response is received with the correct salt, and the message is to be re-sent with it) [2024-01-18 11:39:22] [critical] USER_DEACTIVATED_BAN [2024-01-18 11:39:22] [critical] !!!!!!! WARNING !!!!!!! Telegram's flood prevention system suspended this account. To continue, manual verification is required. Send an email to recover@telegram.org, asking to unban the phone number +177****, and shortly describe what will you do with this phone number. Then login again. If you intentionally deleted this account, ignore this message.

[lambq]

After restarting Docker, the session file will expire

[xtrime-ru]

This is not the issue. Telegram blocked your account, because it suspicious. Dont buy accounts and dont use fresh and suspicious accounts. Follow steps in your error log. Please check this doc for additional info: https://docs.madelineproto.xyz/docs/LOGIN.html#getting-permission-to-use-the-telegram-api

After manual verification wait for 10-60 minutes. Then remove session and try to login with this number again.