Djoss

Note that you can copy the displayed URL and paste it in your browser to do the login yourself. If you would like to provide more details about the failure, you can edit the container setting and add a new variable named "CONTAINER_DEBUG", with a value of "1". You can then reproduce the problem and get the file /tmp/cp_login.log inside the container. You can send me its content in a private message.

You are using the wrong thread (this one is for a different container). Under the Docker page, click the container icon and then select "Support".

I never saw this problem... are you using the container with default settings ? You may also try to start with a clean /mnt/user/appdata/MKVToolNix

@alturismo, do you get the same behaviour with all kind of videos? Just tried one on my side and the preview worked correctly.

Try this: su-exec app env HOME=/config avidemux3_jobs_qt5

Thanks for reporting. This was working for me when I worked on the new version, but I will check if I forgot something.

The current beta key is expired. We need for a new one to be published.

No, nothing resets everything You can check the uptime of the container to see if it has been restarted.

Did you change "Automated Media Center: Input Directory" ?

FileBot tries to work with /Movies, which doesn't exist. What are you trying to achieve exactly ? Are you using the GUI or the AMC ?

Yes, I'm working on this !

Do you have more details about the crash ? Something in the container's log ? Just so we can better understand, what is the "original" path of your medias and what is the path where you found the medias after the crash ?

How do you reproduce this ?

Freefilesync itself has an option to run command on completion (Action->Synchronization settings). But I think there is nothing for the start. However, you can open a feature request on https://github.com/jlesage/docker-freefilesync/issues. It should be possible to add some hooks for scheduled jobs.

You did a type in the variable name: it should be "FFS_SCHEDULED_BATCH_JOB_2_NAME" and not "FFS_SCHEDULED_JOB_2_NAME".

I think you figured out the issue and it's now working for you?

No it's not! Yes, you can add another "Path" in container's config and use it. This is the default folder selected by Tixati. You can change it in Tixati's settings, under Transfers->Locations.

MKVToolNix doesn't transcode or re-encode videos... so a GPU would not help here.

Did you try to edit the container settings and add a new "Path" ?

Looks like you are not using the latest version of the container ? Your log shows you are not running the latest version of CrashPlan.

Did you specified a CrashPlan server, either from the container's config or from the UI ?

Did you see https://github.com/jlesage/docker-freefilesync?tab=readme-ov-file#scheduled-batch-jobs ?

Recycle bin is not supported, so files are permanently removed :)

In container settings, the fields "User ID" and "Group ID" define the user under which the application will run.

I would suggest to check at /mnt/user/appdata/CrashPlanPRO/log/service.log.0 to see if there is anything useful.