Activate valid license

[droidbot]

I'm encountering a situation where, even after successfully activating my license via the terminal inside the Docker container—complete with a notification confirming the activation and the creation of the license.txt file—it still displays the message "Bad License (>_<)." just before moving my files.




Im running filebot in a Synology container manager.

This is the yaml config I'm using:

Code: Select all

version: '3.3'
services:
  filebot:
    container_name: FileBot
    image: rednoah/filebot:watcher
    restart: always
    environment:
      - SETTLE_DOWN_TIME=300
      - SETTLE_DOWN_CHECK=60
      - PUID=1026
      - PGID=100
    volumes:
      - /volume1/docker/filebot:/data
      - /volume1/downloads:/down
      - /volume1/media:/media
    command: >
      /down/COMPLETE
      --output /media
      --action move
      --def unsorted=y
      --def artwork=n
      --def clean=y
      --def movieFormat="./movies/{n}/{n} ({vf}) [{rating}]"
      --def seriesFormat="./series/{n}/{'Season '+s}/{s00e00} - {t} ({vf})"
      --def unsortedFormat="./misc/"
      --def movieDB=TheMovieDB seriesDB=TheTVDB

I dont get it why it is not working.... worked many weeks before. System wasn't touch for months...

[droidbot]

Never mind.... had to switch within the container to the user "filebot" with "su - filebot" and apply the license command.... Wouldn't it be easier to throw the .psm file within the filebot data folder and do this job automatically?

[rednoah]

You'd typically activate your license as the default non-root user via a user-interactive terminal like so:

Shell: Select all

# Read License Key from Console Input
docker run --rm -it -v "data:/data" rednoah/filebot --license

See How do I activate my license? for details.

Wouldn't it be easier to throw the .psm file within the filebot data folder

That is what the command above does. It'll save the license key at the correct file path so you don't have to. You could do this yourself of course, but you would ask what exactly is the correct file path I would answer run filebot --license and read the console output. Also, if you use named volume -v data:/data as shown in all the examples, then you may not be be able to easily find and access the files inside the container from the host.

e.g. if the correct path inside the container is /data/filebot/license.txt then you could map a specific license file path from the host into the container file system and thus skip the filebot --license configuration step:

Shell: Select all

-v "/path/to/FileBot_License_P12345678.psm:/data/filebot/license.txt"

[droidbot]

Thx this one did the trick for the future coming licenses

"-v "/path/to/FileBot_License_P12345678.psm:/data/filebot/license.txt""