meeb
Thanks for the update. It's possible the updates to yt-dlp have resolved this passively. I'll keep an eye on it.
The actual error here buried in your traceback is "Temporary failure in name resolution". That would imply that tubesync can't resolve the host "www.youtube.com". Something would appear to be broken...
That does seem like way too much RAM allocated. Some other people have reported some memory issues previously but I've never been able to replicate it to find the cause....
The issue is the current (jank) worker system. On my system it releases RAM after downloads regardless of what channels I add. It seems in some deployments it doesn't and...
@alexander-henkes thanks for the input, however a 404 error isn't likely to be a network issue. The 404 error is returned by YouTube so @mavrik132 's container can connect out...
@ZTiKnl I don't think this issue is related to premium streams, your issue looks to be an application block. Your tubesync instance requested https://www.youtube.com/watch?v=BBWmRvIT0QY however it received information on https://www.youtube.com/watch?v=aQvGIIdgFDM...
The error is because you're trying to save downloads outside of the download root, check the source directory. Try setting a name like `watch-later`. If you've specified a full path...
If you are trying to sync a private playlist (a playlist that requires you to be logged into a browser to view) you'll need to export your cookies and use...
Absolutely no idea, sorry. I've never used Edge and this is well outside the scope of TubeSync itself. I'd assume a plugin? https://microsoftedge.microsoft.com/addons/search/export%20cookies
Try deleting and re-adding the source, then check the logs of the container for details.