[SOLUTION] Tube Archivist Elasticsearch Container Unhealthy - Fix: Add NFSv4 ACL Entry for UID 1000

If you’re experiencing Elasticsearch failing to start in Tube Archivist on TrueNAS Scale with the error “dependency failed to start: container ix-tubearchivist-elastic-search-1 is unhealthy,” the issue is likely missing NFSv4 ACL permissions.

The Fix:

Navigate to your ElasticSearchDataStorage dataset → Edit ACL → Add a new entry:

  • Type: User

  • ID: 1000 (the apps container UID)

  • Access: Full Control

Why This Works:

Elasticsearch runs as UID 1000 inside the container. While group-level permissions (builtin_users) may appear sufficient, the container needs explicit user-level access to read/write data and complete health checks. Without this, Elasticsearch fails initialization before the health check passes.

Result: Elasticsearch starts successfully, dependency resolves, and Tube Archivist comes online.

This solved the issue after hours of troubleshooting memory allocation and permissions. Hopefully saves someone else the time!

Can you give your opinion about the app? I was looking (from time to time) to replace youtube-dl, which went off into the sunset.

Brilliant. That sorted it for me. :slightly_smiling_face: