search

jlesage / docker-crashplan-pro

Docker container for CrashPlan PRO (aka CrashPlan for Small Business)
MIT License
301 stars 38 forks source link

CPP: "Unable to sign in. Can't connect to the server." #217

Open JasterMereel opened 4 years ago

JasterMereel commented 4 years ago

I currently have a DS418play on my home network. I installed Docker manually back in August or so and I have the latest version of jlesage/crashplan-pro image. It was working fine until about a month ago. At that point, the CPP image stopped being able to connect to the CPP website. I have installed a new image, I have logged out of the original image, and a few other things. Either way, neither of the current images can connect to the CrashPlan Pro service. The literal message on the log in screen is "Unable to sign in. Can't connect to the server."

I checked through the logs and I don't see anything obvious. Can someone point me in the direction as to why the image isn't connecting to CPP? Let me know what I need to look for and paste into here from the logs.

JasterMereel commented 4 years ago

@jlesage just checking in to see if you could help me out with this in any way, please.

jlesage commented 4 years ago

Can you try to clear the cache to see if it helps: https://github.com/jlesage/docker-crashplan-pro#device-status-is-waiting-for-connection

JasterMereel commented 4 years ago

@jlesage I'm really trying here, but I don't have a dev background. I'm looking at the link that you sent me. When I see stuff such as "For example, if the /config folder of the container is mapped to /docker/appdata/crashplan-pro on the host", I'm looking through the Synology and I can't find anything that looks anything like that. I've SSHed into the Synology so I am at the root file structure. There is a docker folder at /volume1/docker/, but there isn't anything related to 'appdata' under it. I've poked around at this for over an hour over the last week and I still am not any closer to getting this resolved.

Any other tips on how to figure this out? Or how to learn to navigate the Synology file structure?

jlesage commented 4 years ago

In the container's settings, you should have a "Volume" tab. This is where the mappings are done. You should see a "Mount path" set to /config. The associated path to its left is the path on your Synology.

JasterMereel commented 4 years ago

@jlesage I actually didn't have a /config set up for my docker image. I did map /config on the docker container to docker/appdata/crashplan-pro after I created the last 2 directories. As soon as the image booted up, I tried to connect to CPP. I got the exact same error. I stopped the image and checked the docker/appdata/crashplan-pro/cache/ folder and there was nothing in it.

Is there anything else that I can try? CPP hasn't been backed up for almost 2 months now.

jlesage commented 4 years ago

Did you look at the log/service.log.0 log file ? It should be under docker/appdata/crashplan-pro in your case.

JasterMereel commented 4 years ago

@jlesage thanks so much for the continued help with this.

I just looked at the log and I have posted a screenshot here. I keep seeing messages such as "up42.service.peer.PeerController] Couldn't connect to CPC at known location, attempting to connect to CPC via authority fallbacks list" and "up42.service.peer.PeerController] DENIED! Ignore connect, we are not authorized."

Screen Shot 2020-02-16 at 10 52 40 AM
jlesage commented 4 years ago

I see in the logs that central.crashplanpro.com cannot be resolved. Is your Synology DNS configuration correct?

JasterMereel commented 4 years ago

@jlesage I'm poking around about that. I'm using the OpenDNS servers for my DNS servers for my entire home network and right now, even this laptop can't resolve central.crashplanpro.com.

JasterMereel commented 4 years ago

@jlesage I can ping that server from my internal network. Here are the current logs. Anything else look like an issue?

Screen Shot 2020-02-16 at 12 18 25 PM
jlesage commented 4 years ago

There are still errors about the DNS not being resolved.

You can try this command to see if the DNS name can be resolved from the container:

docker exec <name of the container> nslookup central.crashplanpro.com
JasterMereel commented 4 years ago

Hi,

I'm bumping this because after getting frustrated with not getting it to work, I put it aside for a few months. Now, I have decided to pick it back up.

I now think I need to poke a hole in my firewall on the Synology to get this working properly. Would you happen to know the ports that the CPP image uses? I have a bunch of rules allowing 443, 4242-4244, and 4287 to go through the firewall. Then, I have a Deny All rule at the very end. If I turn off the Deny All rule, CPP works. If I turn it on, CPP won't connect.

Any other ports I need to allow through?

jlesage commented 4 years ago

I don't know which port would be missing... However, don't you have the ability to see in your firewall what is blocked ?