Kyoo Unable to Detect Videos in Mounted Volumes Despite Correct Configuration

[djwizzer]

Kyoo Unable to Detect Videos in Mounted Volumes Despite Correct Configuration

Hello,

I am experiencing an issue where Kyoo is not detecting any videos in my mounted volumes. Here is a summary of the steps I’ve taken so far:

1. I have multiple mounted volumes on my Ubuntu server: /mnt/1to, /mnt/500go, /mnt/500go_vm, and /mnt/640gofreebox. These volumes contain various video files that I want Kyoo to scan.

2. I have configured my docker-compose.yml file to mount these volumes for both the transcoder and scanner services:

   x-transcoder: &transcoder-base
     image: ghcr.io/zoriya/kyoo_transcoder:edge
     networks:
       default:
         aliases:
           - transcoder
     restart: unless-stopped
     env_file:
       - ./.env
     environment:
       - GOCODER_PREFIX=/video
     volumes:
       - /mnt/1to:/video/1:ro
       - /mnt/500go:/video/500go:ro
       - /mnt/500go_vm:/video/500go_vm:ro
       - /mnt/640gofreebox:/video/640gofreebox:ro
       - ${CACHE_ROOT}:/cache
       - metadata:/metadata
   
   services:
     transcoder:
       <<: *transcoder-base
   
     scanner:
       image: ghcr.io/zoriya/kyoo_scanner:edge
       restart: unless-stopped
       depends_on:
         back:
           condition: service_healthy
       env_file:
         - ./.env
       environment:
         - KYOO_URL=${KYOO_URL:-http://back:5000}
       volumes:
         - /mnt/1to:/video/1:ro
         - /mnt/500go:/video/500go:ro
         - /mnt/500go_vm:/video/500go_vm:ro
         - /mnt/640gofreebox:/video/640gofreebox:ro

3. I have ensured that the .env file's LIBRARY_ROOT variable points to all the volumes:

   LIBRARY_ROOT=/mnt/1to,/mnt/500go,/mnt/500go_vm,/mnt/640gofreebox

4. I have verified the permissions on the directories, and Docker is able to access the files inside them when testing with a separate container.

5. After restarting the Kyoo services with docker compose down && docker compose up -d, no videos are detected, and the message "No video was found yet" appears on the web interface.

I would appreciate any insights or suggestions on what might be causing this issue or if there are any additional troubleshooting steps I should take.

Thank you!

[djwizzer]

Unable to Access Admin Interface on Kyoo Web Interface

I am having trouble accessing the admin panel on the Kyoo web interface. The installation appears to be working correctly, and I can access the main UI at http://localhost:8901. However, I can't find a way to access the admin settings or dashboard.

I have tried:

• Different web browsers (Chrome, Firefox).
• Clearing browser cache and cookies.
• Searching through the documentation and existing issues.

Is there a specific URL path or a configuration step required to access the admin interface? Or is there anything in the .env or docker-compose.yml file that needs to be adjusted for the admin panel to become accessible?

Any help or guidance would be greatly appreciated!

Thank you!

[zoriya]

The admin panel is accessible by all admin accounts. The first account created is automatically promoted to administrator.

If you lost the logins to the admin account, you would need to delete all accounts and create a new one. This can be done by re-initializing the database using docker compose down --volumes

[zoriya]

Can you send the output of docker compose logs -n 2000 scanner matcher?
(for future reference, LIBRARY_ROOT is only used in the docker-compose.yml. if you override the mount points yourself, the env var is unused)

[djwizzer]

Hello 👋,

Thank you so much for your response! 🙏

I managed to resolve the issue — it turns out I just needed to manually run the scanner from the console, and then everything started to be scanned properly. 🎉 All my media files were successfully detected!

I do have one more question: do you have any advice on how to connect the Kyoo server with the Android app? 📱 Also, do you have recommendations for the optimal hardware configuration? For example, would a Raspberry Pi (3, 4, or even 5) be powerful enough for smooth performance, or would it be better to go for a small PC like an Intel NUC or a mini PC book? 💻

Thanks again for the quick and helpful response! 🚀

Best regards,