You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just yesterday, I set up new tubesync container through docker-compose, using ghcr.io/meeb/tubesync:latest. When scanning a source, everything fails with no media available. Docker logs show each video causing: [tubesync/WARNING] Could not compute published from timestamp for: <video> with "name 'posix_epoch' is not defined".
I don't see any other warnings or errors in the logs.
Manually skipping/unskipping the video simply causes the same error. This happens regardless of feed configuration, as far as I can tell.
I am using a /config/cookies.txt, and if I run yt-dlp inside the container manually, it can download videos without issue.
Let me know if there's any other info you need, and if there's an older version of tubesync I can fall back to in the meantime, to rule out any configuration error on my end. Thanks!
The text was updated successfully, but these errors were encountered:
Just yesterday, I set up new tubesync container through docker-compose, using
ghcr.io/meeb/tubesync:latest
. When scanning a source, everything fails with no media available. Docker logs show each video causing:[tubesync/WARNING] Could not compute published from timestamp for: <video> with "name 'posix_epoch' is not defined"
.I don't see any other warnings or errors in the logs.
Manually skipping/unskipping the video simply causes the same error. This happens regardless of feed configuration, as far as I can tell.
I am using a
/config/cookies.txt
, and if I runyt-dlp
inside the container manually, it can download videos without issue.Let me know if there's any other info you need, and if there's an older version of tubesync I can fall back to in the meantime, to rule out any configuration error on my end. Thanks!
The text was updated successfully, but these errors were encountered: