Djoss

Can you check the content of these log files: tail -n 100 /mnt/user/appdata/Firefox/log/firefox/error.log tail -n 100 /mnt/user/appdata/Firefox/log/firefox/output.log My guess is that something went wrong with the Firefox profile. So probably that doing this would help starting from scratch: docker stop Firefox mv /mnt/user/appdata/Firefox /mnt/user/appdata/Firefox.bk docker start Firefox

Please provide the full container log by running the following command: docker logs Firefox

What is your backup destination ?

Yes, I'm fixing this. Thanks or reporting.

From what you are describing, it's not clear to me if the problem is specific to the container or is more general to the Docker system. You can see other topics with the same issue about the container not stopping: https://forums.unraid.net/topic/129333-unraid-fuse-dies-during-docker-container-operation-whole-os-gets-stuck/ https://forums.unraid.net/topic/128837-after-upgrating-to-unraid-v611-my-unraid-server-stop-respoing-everyday-at-same-time/#comment-1173788 https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-r2153/ https://forums.unraid.net/topic/129244-daily-crashes-after-upgrade-to-611/ Same issue reported here also: https://github.com/moby/moby/issues/43094

I also tried a couple of devices with Android Emulator, and they all worked. What is the model of your tablet ? Which Android version it is running ?

After some verifications, long press support is already there. So a right click can be simulated by either a long press (of at least 1 second) or by a two-fingers tap. Again, this is working for me, at least on iOS.

What do you mean exactly by the "dialog that appeared in previous releases" ? Are you talking about the menu in MKVToolNix that appears after a long press ? If that the case, then I confirm this is a bug and will re-integrate this functionality. Also note that a submit button is no longer needed for the clipboard, meaning that what type into the Clipboard text box is immediately available to the application. Thus, once you are done typing, you can close the menu. Ok I see what you mean. The whole application has been (initially) resized to fit the window of your browser. Can you try to set the scaling to "local" and then restart the container ? What happen exactly when they don't come up? You main they are not started automatically ? Or the start fails ? Do you have any error message ?

Can you provide the version of Windows and Chrome you are using ? I just tried with latest Chrome in Windows 10 and it works fine for me. Do you have the same result in an incognito window ? I think this is the same behaviour as before ? Ok I will verify this. In the new left menu, do you have the keyboard button (to show up the keyboard) ? What do you mean exactly ? The latest update was a huge update, so it's possible that few bugs remain. Thanks for reporting them, this way I can fix them. Yes there is always a way to use a specific version of the container, by using a specific Docker image tag. In your case, append ":v1.66.0" to the Repository field, under the container's settings.

Is it the first time you try to backup ? How much time did you let CrashPlan in that state ?

Problem fixed, please try the latest image.

I'm fixing this.

Can you try to clear your browser's cache or try in an incognito/private window to see if it's working ?

What is the issue exactly ? I'm using it frequently and it works fine.

Ah, from your screenshot you were restoring to /config. This location should work since it is read/write. /storage is read-only by default. If you want to restore to /storage, you first need to change it to read/write. This can be done in settings of the container.

I don't see anything obvious from the provided logs. For me the restore functionality works fine. You should probably try the contact the CrashPlan's support team. Provide the error messages and don't tell them that you are using CrashPlan in a Docker container, since they will tell you it's not supported.

What is following the "STACKTRACE:: java.lang.NullPointerException" message ?

Looks like everything is now back online.

You can try to restart the container if you think it is stuck. Then, try to restore just a single file. Run "tail -f /mnt/user/appdata/CrashPlanPRO/log/service.log.0" before starting the restore process so we can get all related logs.

I would be surprised that CloudBerry is dead. Probably a (big) technical issue. I contacted MSP360 to report the problem, let's see if I get any update.

Can you use the native UI, the one on port 7802?

New image is available.

The Docker image needs to be updated. I'm working on this.

Correct, it's the Linux version.

What the browser is showing exactly ?