Cloudbox / autoscan

Autoscan replaces the default Plex and Emby behaviour for picking up changes on the file system.
MIT License
597 stars 49 forks source link

Performing a full scan in Plex with Autoscan #112

Closed TheNexter closed 3 years ago

TheNexter commented 3 years ago

Plex, Sonarr and radarr : Docker linuxserver.io Autoscan : docker hotio

My config πŸ‘

port: 3030

triggers:
  sonarr:
    - name: sonarr
      - from: /tv/
      to: /Plex/

  manual:
    rewrite:
    - from: /Google/
      to: /Plex/Google/

targets:
  plex:
    - url: http://192.168.0.28:32400
      token: *mytoken*

My log πŸ‘

image

When i stop the container autoscan, in plex log πŸ‘ image

Anyone have a idea ? :(

TheNexter commented 3 years ago

image I have this error :( I ask manualy plex to search inside my mount plex, not found :(

radarr is mount with > /movies/........ sonarr > /tv/........ Plex > /Plex/.......

Why it's not working ? :(

m-rots commented 3 years ago

I don't think this has anything to do with networking at all. In fact, the Plex screenshot takes place 4 minutes later than the events in the Autoscan logs.

The failed determining libraries indicates that Autoscan successfully retrieved the libraries of your Plex server, but the path of your current request /Plex/Google/Anime is not part of any of your configured Plex libraries.

Please make sure that the path you pass to the manual trigger actually is the same path that Plex can reach from inside the Docker container. If you're not sure, just click on one of your libraries within the Plex webui and check which path it's set to.

TheNexter commented 3 years ago

I don't think this has anything to do with networking at all. In fact, the Plex screenshot takes place 4 minutes later than the events in the Autoscan logs.

The failed determining libraries indicates that Autoscan successfully retrieved the libraries of your Plex server, but the path of your current request /Plex/Google/Anime is not part of any of your configured Plex libraries.

Please make sure that the path you pass to the manual trigger actually is the same path that Plex can reach from inside the Docker container. If you're not sure, just click on one of your libraries within the Plex webui and check which path it's set to.

Thx for you reply men πŸ‘ but i have a library already with this path

image

m-rots commented 3 years ago

Autoscan does not improve over a regular Plex scan when scanning a whole library. In fact, they do the same as Autoscan simply tells Plex to fully scan the library. While not recommended, passing the path as /Plex/Google/Anime/ (notice the slash at the end) should fix your issue.

TheNexter commented 3 years ago

Ok i have find the solution... i feel like the most stupid guy on this planet

/Plex/Google/Anime/animename/ πŸ‘Ž /Plex/Google/Anime/animename πŸ‘

And :

When you start the container hotio autoscan, they give you a "token" on the container first start can connect to plex, but this token don't have access to start plex scan... Hotio need to remove that it's a source of problem...

And other thing, a weird bug :)

m-rots commented 3 years ago

We really have zero affiliation to the hotio image

TheNexter commented 3 years ago

We really have zero affiliation to the hotio image

Yep i know but it's the most simple way to install your program when you understandπŸ˜