Djoss

Community Developer
  • Posts

    2355
  • Joined

  • Last visited

  • Days Won

    9

Djoss last won the day on April 12 2019

Djoss had the most liked content!

6 Followers

Converted

  • Gender
    Male
  • Location
    Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Djoss's Achievements

Rising Star

Rising Star (9/14)

437

Reputation

  1. Looks like you are not using the latest version of the container ? Your log shows you are not running the latest version of CrashPlan.
  2. Did you specified a CrashPlan server, either from the container's config or from the UI ?
  3. Did you see https://github.com/jlesage/docker-freefilesync?tab=readme-ov-file#scheduled-batch-jobs ?
  4. Recycle bin is not supported, so files are permanently removed :)
  5. In container settings, the fields "User ID" and "Group ID" define the user under which the application will run.
  6. I would suggest to check at /mnt/user/appdata/CrashPlanPRO/log/service.log.0 to see if there is anything useful.
  7. Ok, the CrashPlan cache can get large and the size depends on a lot of factors. Do you have a large backup size? Maybe this article can help: https://support.crashplan.com/hc/en-us/articles/8834209890829-CrashPlan-app-cache-files
  8. This kind of issue is usually caused by a browser plugin. Do you see the same problem in an incognito/private window ? With another browser ?
  9. What I'm maintaining is the container image. In other words, the integration of the MSP360 software itself. The MSP360 software is not open source, so we cannot change it. If there is a bug with it, it's MPS360 that has to fix it. I'm working to integrate a new version of MSP360 Backup. Once done, we can verify if you still get the problem. This is strange. Do you see this behaviour with other containers ?
  10. To be precise, the software has only been renamed/rebranded. So this is the same software as before. Licenses for MSP360 Standalone Backup (Linux editions) apply to this container. Yes this is still maintained and updated. You should provide more details about the issue you got. You are right, the new name should be reflected in documentation. I don't see this issue. Maybe you can provide a screenshot showing the problem ?
  11. See https://support.jdownloader.org/Knowledgebase/Article/View/fix-jdownloader-installation
  12. Ok, I also got the update for my account. I will update the Docker image.
  13. What do you mean by "reorganizing audio" ?
  14. Did you try "{source-path}/{source}" ?