docker-crashplan icon indicating copy to clipboard operation
docker-crashplan copied to clipboard

Unable to connect, check you network error

Open 062bel313 opened this issue 8 years ago • 3 comments

First of all, thank you for this docker image, It is going to make my life easier. I am not very good at Linux but will not hesitate to learn to sort things out.

My system: I have Synology NAS (IP: 10.0.1.10 with Docker version 1.6.2). I have been trying to install CrashPlan to backup my Synology and tried the instruction provided in the readme file. The docker command gave me an error so had to remove -h and -e options to make it work. The command I used is

$ docker run -d \
  --name crashplan \
  --publish 4242:4242 --publish 4243:4243 \
  --volume /volume1/docker/CrashPlan/data:/var/crashplan \
  --volume /volume1:/storage \
  jrcs/crashplan:latest

After the successful installation of the docker, I installed the CrashPlan in my Mac and changed the .ui_info in my Mac. /Library/Application Support/CrashPlan/.ui_info to 4243,5d8f748d-5028-4f42-a288-143f463b4e9e,10.0.1.10 5d8f748d-5028-4f42-a288-143f463b4e9e -> This I got from .ui_info from the docker.

Issue: When I open the CrashPlan app in Mac and try to log in, I get an error: Unable to connect, check your network. However, my other dockers are able to access the internet.

My Understanding: My CrashPlan docker is not able to access the internet, or my app is not able to communicate with the docker CrashPlan.

Running netstat from my Synology (HOST):

$ netstat -ap tcp | grep -i "listen"

tcp        0      0 ::%134877389:4242       ::%134877389:*          LISTEN      17687/docker-proxy
tcp        0      0 ::%134877389:4243       ::%134877389:*          LISTEN      17695/docker-proxy

I am assuming 4243 and 4242 in my host is accessible. I am completely stuck, What have I missed? Can anybody guide me in the right direction?

Thank you again!

062bel313 avatar Jun 25 '17 15:06 062bel313

i have similar problem with you. on my nas, it seems crashplan is only listen to ipv6 address. then backup client always stuck on “waiting for connection”

esojourn avatar Jul 04 '17 04:07 esojourn

i just solved connection problem by using host network. add "--net=host"

sudo docker run -d --net=host --name Crashplan02 -p 4242:4242 -p 4243:4243 -v /volume1/docker/crashplan:/volume1/docker/crashplan jrcs/crashplan:latest

esojourn avatar Jul 04 '17 07:07 esojourn

I changed my DNS to OpenDNS in my Synology NAS and now I am able to sign on and it has started back up. I am not sure what the issue is with any other DNS.

062bel313 avatar Jul 05 '17 16:07 062bel313