[Bug]: Database Bug

[zey0n]

Version

6.0.0

Deployment Method

Docker Compose

Database Type

PostgreSQL

Bug Description

Got this bug after upgrading to version 6.0.0

Expected Behavior

Steps to Reproduce

Upgrade to v6.0.0

Logs

Running database migrations...
INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
Connecting to PostgreSQL at telegram-archive-db-postgres:5432...
PostgreSQL connection established.
Migrations complete.
2026-01-29 02:25:19 - src.telegram_backup - ERROR -   → Error backing up Unknown xxxxxx: The channel specified is private and you lack permission to access it. Another reason may be that you were banned from it (caused by GetHistoryRequest)
Traceback (most recent call last):
  File "/app/src/telegram_backup.py", line 298, in backup_all
    message_count = await self._backup_dialog(dialog)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/src/telegram_backup.py", line 517, in _backup_dialog
    async for message in self.client.iter_messages(
  File "/usr/local/lib/python3.11/site-packages/telethon/requestiter.py", line 74, in __anext__
    if await self._load_next_chunk():
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/telethon/client/messages.py", line 184, in _load_next_chunk
    r = await self.client(self.request)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/telethon/client/users.py", line 30, in __call__
    return await self._call(self._sender, request, ordered=ordered)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/telethon/client/users.py", line 92, in _call
    result = await future
             ^^^^^^^^^^^^
telethon.errors.rpcerrorlist.ChannelPrivateError: The channel specified is private and you lack permission to access it. Another reason may be that you were banned from it (caused by GetHistoryRequest)

Environment

No response

Checklist

• I have searched existing issues to ensure this isn't a duplicate
• I am using the latest version

[GeiserX]

Could you share a bit of your docker compose? The error from the logs is pretty clear... There is a channel you can't scrape, it's strange it didn't throw an error before. At least on my side, I updated and no errors.

There was a change in the filtering options, did you have a chance to check it? Perhaps you'll need to modify some of your env variables now (?). I didn't need it, but perhaps that's the case in your scenario

[zey0n]

I am using latest v6.0.0 updated environment vars, CHAT_IDS=-100123456789,-987654321. The Chat ID that's raising the issue is group that doesn't exist anymore. In last version, this group was being handled elegantly with error message, but since version 6.0.0 update, the additional database error has started showing up.

[GeiserX]

Fixed in v6.0.1.

You're right - the full traceback was excessive for what's actually an expected Telegram response (losing access to channel). Now it logs as a clean warning:

WARNING - → Skipped (no access): ChannelPrivateError

Thanks for reporting!