October 30, 20241 yr 11 minutes ago, ph.neutral said: Unfortunately not. I gave up and deleted the program. This workaround fixed it for me. Seems to be a known permission issue: On 12/9/2022 at 4:33 AM, msherman83 said: Access the Unraid CLI and enter: chmod -R 777 /mnt/user/appdata/TubeArchivist/es
January 16, 20251 yr On 10/30/2024 at 1:25 PM, Jaytie said: This workaround fixed it for me. Seems to be a known permission issue: Still an issue many years on. Thanks for the resolution
March 8, 20251 yr On 10/30/2024 at 12:25 PM, Jaytie said: This workaround fixed it for me. Seems to be a known permission issue: Thanks for the solution
March 12, 20251 yr Hi all, updated to v0.5.0 or reinstalling from scratch v0.5.0 always gives me those errors in the log. The webui works, videos playback as well, but I'm unable to refreshing the subscribed content or add video with a link, nothing happens. FWIW, official setup guide said that we can get rid of the tube archivist-redis own docker, and that the official redis docker works fine. -------------- celery@a079048d37d5 v5.4.0 (opalescent) --- ***** ----- -- ******* ---- Linux-6.6.78-Unraid-x86_64-with-glibc2.36 2025-03-12 20:42:54 - *** --- * --- - ** ---------- [config] - ** ---------- .> app: tasks:0x14958db71550 - ** ---------- .> transport: redis://LanIP:6378// - ** ---------- .> results: redis://LanIP:6378/ - *** --- * --- .> concurrency: 4 (prefork) -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) --- ***** ----- -------------- [queues] .> celery exchange=celery(direct) key=celery [tasks] . check_reindex . download_pending . extract_download . index_playlists . manual_import . rescan_filesystem . restore_backup . resync_thumbs . run_backup . subscribe_to . thumbnail_check . update_subscribed . version_check [2025-03-12 20:42:55,392: WARNING/MainProcess] /root/.local/lib/python3.11/site-packages/celery/worker/consumer/consumer.py:508: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine whether broker connection retries are made during startup in Celery 6.0 and above. If you wish to retain the existing behavior for retrying connections on startup, you should set broker_connection_retry_on_startup to True. warnings.warn( [2025-03-12 20:42:55,410: INFO/MainProcess] Connected to redis://LanIP:6378// [2025-03-12 20:42:55,412: WARNING/MainProcess] /root/.local/lib/python3.11/site-packages/celery/worker/consumer/consumer.py:508: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine whether broker connection retries are made during startup in Celery 6.0 and above. If you wish to retain the existing behavior for retrying connections on startup, you should set broker_connection_retry_on_startup to True. warnings.warn( [2025-03-12 20:42:55,418: INFO/MainProcess] mingle: searching for neighbors [2025-03-12 20:42:55,455: CRITICAL/MainProcess] Unrecoverable error: ContentDisallowed('Refusing to deserialize untrusted content of type pickle (application/x-python-serialize)') Traceback (most recent call last): File "/root/.local/lib/python3.11/site-packages/celery/worker/worker.py", line 202, in start self.blueprint.start(self) File "/root/.local/lib/python3.11/site-packages/celery/bootsteps.py", line 116, in start step.start(parent) File "/root/.local/lib/python3.11/site-packages/celery/bootsteps.py", line 365, in start return self.obj.start() ^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/worker/consumer/consumer.py", line 340, in start blueprint.start(self) File "/root/.local/lib/python3.11/site-packages/celery/bootsteps.py", line 116, in start step.start(parent) File "/root/.local/lib/python3.11/site-packages/celery/worker/consumer/mingle.py", line 37, in start self.sync(c) File "/root/.local/lib/python3.11/site-packages/celery/worker/consumer/mingle.py", line 41, in sync replies = self.send_hello(c) ^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/worker/consumer/mingle.py", line 54, in send_hello replies = inspect.hello(c.hostname, our_revoked._data) or {} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/app/control.py", line 389, in hello return self._request('hello', from_node=from_node, revoked=revoked) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/app/control.py", line 106, in _request return self._prepare(self.app.control.broadcast( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/app/control.py", line 776, in broadcast return self.mailbox(conn)._broadcast( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/pidbox.py", line 346, in _broadcast return self._collect(reply_ticket, limit=limit, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/pidbox.py", line 388, in _collect self.connection.drain_events(timeout=timeout) File "/root/.local/lib/python3.11/site-packages/kombu/connection.py", line 341, in drain_events return self.transport.drain_events(self.connection, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/transport/virtual/base.py", line 997, in drain_events get(self._deliver, timeout=timeout) File "/root/.local/lib/python3.11/site-packages/kombu/transport/redis.py", line 591, in get ret = self.handle_event(fileno, event) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/transport/redis.py", line 573, in handle_event return self.on_readable(fileno), self ^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/transport/redis.py", line 569, in on_readable chan.handlers[type]() File "/root/.local/lib/python3.11/site-packages/kombu/transport/redis.py", line 979, in _brpop_read self.connection._deliver(loads(bytes_to_str(item)), dest) File "/root/.local/lib/python3.11/site-packages/kombu/transport/virtual/base.py", line 1017, in _deliver callback(message) File "/root/.local/lib/python3.11/site-packages/kombu/transport/virtual/base.py", line 639, in _callback return callback(message) ^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/messaging.py", line 650, in _receive_callback decoded = None if on_m else message.decode() ^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/message.py", line 201, in decode self._decoded_cache = self._decode() ^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/message.py", line 205, in _decode return loads(self.body, self.content_type, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/serialization.py", line 255, in loads raise self._for_untrusted_content(content_type, 'untrusted') kombu.exceptions.ContentDisallowed: Refusing to deserialize untrusted content of type pickle (application/x-python-serialize) auto_start: False Edited March 12, 20251 yr by dunnno typo
March 12, 20251 yr 2 minutes ago, dunnno said: Hi all, updated to v0.5.0 or reinstalling from scratch v0.5.0 always gives me those errors in the log. The webui works, videos playback as well, but I'm unable to refreshing the subscribed content or add video with a link, nothing happens. FWIW, official setup guide said that we can get rid of the tube archivist-redis own docker, and that the official redis docker works fine. -------------- celery@a079048d37d5 v5.4.0 (opalescent) --- ***** ----- -- ******* ---- Linux-6.6.78-Unraid-x86_64-with-glibc2.36 2025-03-12 20:42:54 - *** --- * --- - ** ---------- [config] - ** ---------- .> app: tasks:0x14958db71550 - ** ---------- .> transport: redis://LanIP:6378// - ** ---------- .> results: redis://LanIP:6378/ - *** --- * --- .> concurrency: 4 (prefork) -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) --- ***** ----- -------------- [queues] .> celery exchange=celery(direct) key=celery [tasks] . check_reindex . download_pending . extract_download . index_playlists . manual_import . rescan_filesystem . restore_backup . resync_thumbs . run_backup . subscribe_to . thumbnail_check . update_subscribed . version_check [2025-03-12 20:42:55,392: WARNING/MainProcess] /root/.local/lib/python3.11/site-packages/celery/worker/consumer/consumer.py:508: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine whether broker connection retries are made during startup in Celery 6.0 and above. If you wish to retain the existing behavior for retrying connections on startup, you should set broker_connection_retry_on_startup to True. warnings.warn( [2025-03-12 20:42:55,410: INFO/MainProcess] Connected to redis://LanIP:6378// [2025-03-12 20:42:55,412: WARNING/MainProcess] /root/.local/lib/python3.11/site-packages/celery/worker/consumer/consumer.py:508: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine whether broker connection retries are made during startup in Celery 6.0 and above. If you wish to retain the existing behavior for retrying connections on startup, you should set broker_connection_retry_on_startup to True. warnings.warn( [2025-03-12 20:42:55,418: INFO/MainProcess] mingle: searching for neighbors [2025-03-12 20:42:55,455: CRITICAL/MainProcess] Unrecoverable error: ContentDisallowed('Refusing to deserialize untrusted content of type pickle (application/x-python-serialize)') Traceback (most recent call last): File "/root/.local/lib/python3.11/site-packages/celery/worker/worker.py", line 202, in start self.blueprint.start(self) File "/root/.local/lib/python3.11/site-packages/celery/bootsteps.py", line 116, in start step.start(parent) File "/root/.local/lib/python3.11/site-packages/celery/bootsteps.py", line 365, in start return self.obj.start() ^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/worker/consumer/consumer.py", line 340, in start blueprint.start(self) File "/root/.local/lib/python3.11/site-packages/celery/bootsteps.py", line 116, in start step.start(parent) File "/root/.local/lib/python3.11/site-packages/celery/worker/consumer/mingle.py", line 37, in start self.sync(c) File "/root/.local/lib/python3.11/site-packages/celery/worker/consumer/mingle.py", line 41, in sync replies = self.send_hello(c) ^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/worker/consumer/mingle.py", line 54, in send_hello replies = inspect.hello(c.hostname, our_revoked._data) or {} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/app/control.py", line 389, in hello return self._request('hello', from_node=from_node, revoked=revoked) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/app/control.py", line 106, in _request return self._prepare(self.app.control.broadcast( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/celery/app/control.py", line 776, in broadcast return self.mailbox(conn)._broadcast( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/pidbox.py", line 346, in _broadcast return self._collect(reply_ticket, limit=limit, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/pidbox.py", line 388, in _collect self.connection.drain_events(timeout=timeout) File "/root/.local/lib/python3.11/site-packages/kombu/connection.py", line 341, in drain_events return self.transport.drain_events(self.connection, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/transport/virtual/base.py", line 997, in drain_events get(self._deliver, timeout=timeout) File "/root/.local/lib/python3.11/site-packages/kombu/transport/redis.py", line 591, in get ret = self.handle_event(fileno, event) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/transport/redis.py", line 573, in handle_event return self.on_readable(fileno), self ^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/transport/redis.py", line 569, in on_readable chan.handlers[type]() File "/root/.local/lib/python3.11/site-packages/kombu/transport/redis.py", line 979, in _brpop_read self.connection._deliver(loads(bytes_to_str(item)), dest) File "/root/.local/lib/python3.11/site-packages/kombu/transport/virtual/base.py", line 1017, in _deliver callback(message) File "/root/.local/lib/python3.11/site-packages/kombu/transport/virtual/base.py", line 639, in _callback return callback(message) ^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/messaging.py", line 650, in _receive_callback decoded = None if on_m else message.decode() ^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/message.py", line 201, in decode self._decoded_cache = self._decode() ^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/message.py", line 205, in _decode return loads(self.body, self.content_type, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.local/lib/python3.11/site-packages/kombu/serialization.py", line 255, in loads raise self._for_untrusted_content(content_type, 'untrusted') kombu.exceptions.ContentDisallowed: Refusing to deserialize untrusted content of type pickle (application/x-python-serialize) auto_start: False Did you update your URL to start with http:// or https://(if reverse proxied) in the container template?
March 12, 20251 yr Either with or without http:// in TA_HOST variable results in this error. Or if I misunderstood, where are you talking about ? My TubeArchivist docker is only local, not open to the world.
March 12, 20251 yr 10 minutes ago, dunnno said: Either with or without http:// in TA_HOST variable results in this error. Or if I misunderstood, where are you talking about ? My TubeArchivist docker is only local, not open to the world. Yeah I had the issue where the web interface would load but if I tried to refresh subscriptions it would force me back to the login page. I was missing https://tube.mydomain.com -- after I added the https:// part to the front of TA_Host it worked w/out issue. is your TA_HOST then setup as http://192.168.1.X:YYYY ?
March 12, 20251 yr Yep, TA_HOST is http://LanIP:MyPort. Isn't redundant with the other port variable "Container Port: 8000" which I set to MyPort as well ?
March 12, 20251 yr Well, found the problem. Since we can use a plain Redis container, I happen to already have one running for Paperless. So I was asking TA to use that Redis container. But a Redis container cannot be used by two other containers at the same time. I have to install a second plain Redis container for the exclusive use of TA. Here is the answer
March 13, 20251 yr Can someone help me understand what is happening with TubeArchivist right now? I casually updated to 0.5.0 and found the Docker container will not run. I have very limited experience with Docker, console commands, Linux/Unix, etc. etc. etc. I know enough to get what I want running when I'm determined, and I can follow instructions to the T as long as I understand them and they don't assume knowledge or experience that is drastically above my amateur, ad-hoc collection for this realm. I've been reading TA's page on the latest release at https://www.tubearchivist.com/ but I'm struggling to understand what is happening. Seems they're upgrading the back-end, cannot merge/bring over certain data, so you have to migrate by pulling some data out and prepping it? Seems I'm in the boat that needs to "revert the image to bbilly1/tubearchivist:v0.4.13", and then can likely migrate? Can someone help me understand what reverting even means? TA seems to be one of those self-hosting softwares that is obscure enough to not regularly have a decent YouTuber consistently making laymen's terms explanations for issues like this. Sometimes I wonder how I even got this going to begin with. Any guidance is much appreciated. EDIT: OK, just found instructions for reverting an Unraid Docker Container. First time for everything. I'm almost certain good to go from here. Edited March 13, 20251 yr by AManOfCharacter
March 24, 20251 yr On 3/13/2025 at 2:39 PM, AManOfCharacter said: Can someone help me understand what is happening with TubeArchivist right now? I casually updated to 0.5.0 and found the Docker container will not run. I have very limited experience with Docker, console commands, Linux/Unix, etc. etc. etc. I know enough to get what I want running when I'm determined, and I can follow instructions to the T as long as I understand them and they don't assume knowledge or experience that is drastically above my amateur, ad-hoc collection for this realm. I've been reading TA's page on the latest release at https://www.tubearchivist.com/ but I'm struggling to understand what is happening. Seems they're upgrading the back-end, cannot merge/bring over certain data, so you have to migrate by pulling some data out and prepping it? Seems I'm in the boat that needs to "revert the image to bbilly1/tubearchivist:v0.4.13", and then can likely migrate? Can someone help me understand what reverting even means? TA seems to be one of those self-hosting softwares that is obscure enough to not regularly have a decent YouTuber consistently making laymen's terms explanations for issues like this. Sometimes I wonder how I even got this going to begin with. Any guidance is much appreciated. EDIT: OK, just found instructions for reverting an Unraid Docker Container. First time for everything. I'm almost certain good to go from here. did you get it back up and running ? im in the same boat right now
May 23, 20251 yr On 3/12/2025 at 2:03 PM, dunnno said:Well, found the problem. Since we can use a plain Redis container, I happen to already have one running for Paperless. So I was asking TA to use that Redis container.But a Redis container cannot be used by two other containers at the same time. I have to install a second plain Redis container for the exclusive use of TA.Here is the answerYou probably don't have an answer for this but for anyone reading in the future, I'm curious, is this a specific-to-TubeArchivist/similar niche setups thing? I was under the impression a single Redis instance is absolutely capable of serving a ton of different programs at once. I already use multiple other programs with mine. I'll go ahead and continue using my pre-existing dedicated TA instance but that's odd to me. I know almost nothing about it though so I'm curious to learn more. Also yeah, the v0.5 migration is absolutely brutal for a semi-layman lol. I'm about to give it an attempt now, let's see how it goes. May just try to fresh install if I can't get it working after a few.Edit: eh that actually wasn't that bad, the page looked a lot more intimidating because of the some of the extra info they provided. I'd recommend feeding the 0.5 update page into an LLM and telling it your setup (Unraid, Docker) and it'll walk you through pretty simply. Edited May 23, 20251 yr by Cressio
June 8, 20251 yr I am still unable to get tubearchivixt to connect to the ES container, i believe it is a permissions error based on this text from the es container{"@timestamp":"2025-06-08T16:06:51.389Z", "log.level": "INFO", "message":"Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[d4656d1911c9][get][T#13]","log.logger":"org.elasticsearch.xpack.security.authc.RealmsAuthenticator","elasticsearch.cluster.uuid":"SL8JPC9ETZKv4KXxtt4Prg","elasticsearch.node.id":"NRZKE2QbRA-JEnLjHrojpQ","elasticsearch.node.name":"d4656d1911c9","elasticsearch.cluster.name":"docker-cluster"}I've tried the command listed below but no dice, please help!"chmod -R 777 /mnt/user/appdata/TubeArchivist/es"Edit: Resolved this with this command from the TubeArchivist guide, wasn't working before but worked after reboot. 'newperms /mnt/user/appdata/TubeArchivist/' Edited June 8, 20251 yr by jakemuffins
June 17, 20251 yr Hello, I am brand new to the docker and originally got some issues with the ES not connecting, but with the help of this thread was able to get that working, now I have a new issue:I have read through the link provided, and done what I can, but this is a new install, never used before so I have no old one to change from. I am using port 6380 instead of 6379 due to another container using that port, but I made the appropriate changes as needed when setting up the 3 dockers.I am sure I am doing something wrong, just having a heck of a time figuring it out.
November 15, 2025Nov 15 It works for me just installed TA Tube Archivist.Follow these instruction.Unraid - Tube Archivist DocumentationNoneNote.First install TubeArchivist-Redisand start it.Then install TubeArchivist-ESand start it.=> TubeArchivist-ES will unfortunately soon stop and not work. !!!Access the Unraid CLI and enter:chmod -R 777 /mnt/user/appdata/TubeArchivist/esThis MUST be done and is not described in the Documentation above (but noted as a fix earlier in this thread).Otherwise TubeArchivist-ES will stop and later when starting TubeArchivist it will also stop and not work.Now you can start TubeArchivist-ESand it will not stop.And finally you install TubeArchivistedit according to instructions (insert your servers IP in the fields mentioned) APPLY and start it.Now it works perfectly.Each youtube channel will gets it's own random named share folder.It will look messy under user/shares.So I suggest you make a new share called TAMedia or somethingand change TubeArchivist Edit to "Youtube Media Path: /mnt/usr/TAMedia/" Edited November 20, 2025Nov 20 by Alexander
December 17, 2025Dec 17 Was able to update to v.0.5.0 with no problem, but updating to later versions causes my TubeArchivist app to crash on startup. Has anyone else dealt with this? Even when I try to view the logs, the window closes out on me. I changed permissions, increased the ES memory, deleted the dump.rdb and the db.sqlite3, and I'm left scratching my head. TubeArchivist-Redis and TubeArchivist-ES startup and stay running.But when I run TubeArchivist and I open the logs to check out what's going on, it runs until it just randomly closes out and the docker container stops. Obviously, I'm missing something. I was able to screen record and then catch a screenshot of what the logs looked like before it closed out and I've posted the picture here. If anyone can help, I'd much appreciate it. Edited December 17, 2025Dec 17 by N¿¿B Added better picture and more information.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.