search

jlesage / docker-crashplan-pro

Docker container for CrashPlan PRO (aka CrashPlan for Small Business)
290 stars 39 forks source link

VNC "Failed to Connect" error #425

Closed menos08642 closed 1 year ago

menos08642 commented 1 year ago

Frequently when hitting the IP:port for my running container, I get a red bar at the top with a "Failed to Connect" message. This is resolved by restarting the container. This can have the unintended consequence of really mucking with the running crashplan instance. I've also noticed that I can fix it by killing the xvnc process running inside the container itself. There is nothing in the logs that looks relevant. Ideas on what to look for?

jlesage commented 1 year ago

Do you see the problem with different browsers ?

menos08642 commented 1 year ago

Yes, I've tried with Edge, Chrome and Firefox. I've set CONTAINER_DEBUG to 1 but I'm not seeing any additional logging or indication of what is crashing/hanging. Is there anyway to turn on additional verbosity of the xvnc process?

jlesage commented 1 year ago

CONTAINER_DEBUG already increases verbosity of xvnc...

Did you see the problem with the latest image ? In this image, xvnc has been upgraded to the latest version.

menos08642 commented 1 year ago

The latest version has been up for 4 days now without the xvnc crash. That looks like it may have solved it.

jlesage commented 1 year ago

Thanks for the update, closing this issue.