Stops recieving messages after 10-20 hours

[AustinTurney]

Code that causes the issue

async def main():
    await client.start(phone=phone_number)  # Start the client
    print("Listening for messages...")
    await client.run_until_disconnected()  # Keep the client running   

if __name__ == "__main__":
    import asyncio
    asyncio.run(main())

Expected behavior

The program would run until disconnected or user interrupted

Actual behavior

after 10-20h the program stop logging messages. I then have to manually interrupt the program and restart the script.

Traceback

The last log is usually this:

2024-12-21 11:31:39,980 - WARNING - Server sent a very old message with ID xxxxxxxxxxxxxxxx, ignoring (see FAQ for details)
2024-12-21 11:31:39,980 - WARNING - Security error while unpacking a received message: Too many messages had to be ignored consecutively

Telethon version

1.38.1

Python version

3.11.9

Operating system (including distribution name and version)

Windows 10

Other details

No response

Checklist

• The error is in the library's code, and not in my own.
• I have searched for this issue before posting it and there isn't an open duplicate.
• I ran pip install -U https://github.com/LonamiWebs/Telethon/archive/v1.zip and triggered the bug in the latest version.

[Sal0ID]

I use telethon for 24/7 monitoring of specific telegram channels, have not encountered any problems yet. Here is my code:

from telethon import TelegramClient, events

# Create a Telegram client
client = TelegramClient(SESSION_NAME, API_ID, API_HASH)

async def main():
    print("Starting Telegram client...")
    await client.start()
    await client.run_until_disconnected()
    
if __name__ == "__main__":
    import asyncio
    asyncio.run(main())
    
@client.on(events.NewMessage())
async def new_message_handler(event):
    #Your program goes here

[saurabh-bitpack]

We’ve been experiencing the same issue:
Security error while unpacking a received message: Too many messages had to be ignored consecutively

This occurred for the first time recently. The client was running continuously for 2 days without issues, and then it started throwing this error. Restarting the service temporarily resolves the problem.

Our setup had been running stably for months, and there were no significant code or environmental changes before this started happening.

[CipherSight]

@AustinTurney I've been using it to monitor 24/7 some chats for months without problem. Maybe you can try to filter chats:

@client.on(events.NewMessage(chats=[]))
async def handle_new_message(event):
       # Your program goes here

[luigirovani]

I had this problem with real accounts too, they stop receiving updates. This doesn't happen with bots, I think Telegram doesn't allow normal users to be online 24/7. My solution was to call _disconnect() every 24 hours, wait 30 seconds and reconnect at a convenient time.

Attention! Call _disconnect and not disconnect, because disconnect() ends up disconnecting the database too, unless you want to recreate the Client Object again.