-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Encrypted And Non-Encrypted Files Fail to Play with 400 ERROR After Upgrading to 1.6.5/1.6.6, Works on 1.6.4 #430
Comments
Working fine for me post upgrade to 1.6.6. Non encrypted files play just fine. |
i experienced this as well and had to revert to 1.6.4 |
On |
am .9 and will update to .10 just now. and am not experiencing this issue. make sure to update the db name etc. there was some breaking changes few updates back |
I kinda mentioned, that i've created new |
|
@aniel300 Just to double-check,
This issue is quite awkward. Since 1.65.5, most of the files are failing to play. |
u trying to play them direcly or via rclone? |
Directly, the same situation would be with rclone. |
is ur db coming from an old version of tgdrive? |
Yep, I'm on PostgreSQL 16. Using Teldrive since 1.4 / 1.5, can't really remember. |
are u using his db container or the official one? |
|
ohh man hopefully ur db is not corrupted or somehting, i cant help on this becuase it is outside of my skillset. someone smarter than me tried to help me with something similar. try to get in touch with him to see if he can help u or try tg discord server |
Found issue, it was redis cache. After i've cleared it, everything works. |
ohh bro am glad for u |
Describe the bug
Some of the encrypted files after upgrading to 1.6.5/6 are not functioning, leading to a 400 ERROR message in the logs. I am uncertain if any changes are required and what the cause might be, but following a restart of Docker, some of the encrypted files began to play, while others failed to do so, and after a second restart, the files that were playing previously now do not play again. This problem is not present in version 1.6.4.
In version 1.6.6, even some non-encrypted files fail to play, displaying the same error message in the logs. I’ve indeed created a new
storage.db
file and linked the Docker container to it.Repoduction
Not entirely certain if you can accomplish that. Attempt with previously encrypted files that were uploaded some time ago.
Expected behavior
I was unable to replicate that issue on versions 1.6.4 and earlier.
Version
1.6.5 and 1.6.6
Which Platform are you using?
Linux (Docker)
Additional context
The text was updated successfully, but these errors were encountered: