![]() ![]() ![]() This latest time I finally decided to deleted and deactivated all my devices on Crashplans server, essentially deleting my entire backup, and started fresh from unraid. I have deleted the container many times making sure to clear old folders using the "cleanup appdata" plugin each time but had the same or similar results. One of the first problems I remember was a "waiting for connection" message which clearing the caches folder, as specified in the troubleshooting steps, helped, but then it constantly cycled a "Routine Maintenance" message or other issues. I let this go for over a week each time but it never changed. Crashplan support pro#I started on the Crashplan Home version of the container from almost the beginning, then was upgraded to the pro version without issue, but for the life of me have been unable to get it working since the change to the HTML pro client version back at the end of last year. Did you added/changed volume mappings? If yes, take note of them before re-installing, as you will need to re-configure them. Try to delete the container and re-install it. I'm sure its a simple solution and just a configuration change, I'm just a little unsure as to what to change is all.īridge mode is the default/recommended mode and should definitely works. I tried doing bridge mode and mapping a port to a spare port on my host machine, but when I tried to access it, it didnt work. The other issue is that I can only seem to run the docker in host mode, it will not run in bridge mode, so I can specify another port like all my other docker containers, to try and avoid the current VNC conflict with my VM. When I load the WebUI it opens on port 5800, so I can only assume that as per the above, ports 7810 & 7910 are internal ports inside the container for the Crashplan Pro services to run properly?Ģ. It should be OK to remove those duplicates yeah? Theres a number of settings in the CrashPlan Pro docker setup to, and I'm a little confused about them, I also have duplicate entries for the VNC and WebUI ports: So what I end up having to do is shut down the VM, restart crashplan, then restart the VM which then assigns the VM a different VNC port. I think it has something to do with the fact that the VM sometimes uses the same VNC port. I have an ubuntu VM installed, and everytime my docker autoupdate runs and my crashplan docker restarts, I can no longer VNC to it. However I have two small issues that I am hoping to try and get sorted out:ġ. I've got the this crashplan pro docker container installed, and for the most part it runs wonderful! I'm hoping some of you guru's here will be able to offer some advice. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |