Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot login #10

Closed
kerrhome opened this issue Dec 5, 2017 · 10 comments
Closed

Cannot login #10

kerrhome opened this issue Dec 5, 2017 · 10 comments

Comments

@kerrhome
Copy link

@kerrhome kerrhome commented Dec 5, 2017

I just set this up for the first time and when I go to login to my existing Crashplan account, I get "The information you entered is incorrect". I verified it is correct by logging into the Crashplan website: https://web-lbm-msp.crashplanpro.com/login/#/login and I have the right username and password. Here is my docker run command:

docker run -d --name=crashplan-pro --restart=always -e VNC_PASSWORD="password" -e TZ="US/Eastern" -p 5800:5800 -p 5900:5900 -v /var/lib/docker/crashplan/data:/config:rw --volume /var/lib/docker/crashplan/storage:/storage:ro jlesage/crashplan-pro:latest

I'm then connecting via vnc (also tried web at 5800 and had same result) at

:5900 password

That gets me to the create account/login screen, but then I am unable to login successfully.

@jlesage

This comment has been minimized.

Copy link
Owner

@jlesage jlesage commented Dec 6, 2017

This should work, your command is correct. Just to make sure you have the right password, you can copy and paste it in the application using the web interface.
Else, you can look/provide the log file located at /config/log/service.log.0 in the container. Just to see if there is any errors that could explain your problem...

@kerrhome

This comment has been minimized.

Copy link
Author

@kerrhome kerrhome commented Dec 6, 2017

Our network is pretty strict as far as open ports in our firewall. I have Crashplan running on a Win7 host and it is having no problems. I even changed my password using the Win7 hosted Crashplan and then went to the website to login and it was fine. Here is what I see in the docker+Crashplan log:

[12.06.17 13:57:31.164 INFO  99693_AUTH-6 backup42.service.peer.Authorizer] AUTH:: *** START *** with Authorizer@728370555[ LOGIN, username=myusername@company.com, passwordExists=true]
[12.06.17 13:57:31.264 INFO  99693_AUTH-6 up42.service.peer.PeerController] Attempting to connect to CPC. delay=60000
[12.06.17 13:57:32.805 INFO  e-listen-1-1 .handler.ChannelExceptionHandler] SABRE:: Uncaught IOException in channel pipeline! msg=not an SSL/TLS record: 8063000000412d31383738327c636f6d2e636f646534322e6d6573736167696e672e73656375726974792e536563757269747950726f766964657252656164794d657373616765 Closing ctx=ChannelHandlerContext(EXCEPTION, [id: 0xb19ddc89, L:/172.17.0.2:50314 - R:/216.17.8.56:443])
[12.06.17 13:57:32.805 WARN  e-listen-1-1 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0xb19ddc89, L:/172.17.0.2:50314 ! R:/216.17.8.56:443]
[12.06.17 13:57:32.806 INFO  e-listen-1-1 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0xb19ddc89, L:/172.17.0.2:50314 ! R:/216.17.8.56:443]), remotePeer=RemotePeer-[guid=42, SERVER]; PeerConnectionState-[state=CONNECTING, mode=PRIVATE, currentAddressIndex=0, layer=1/2(Peer::Sabre), connecting=2017-12-06T13:57:32:729, connected=0, disconnected=2017-12-06T13:57:32:483, attempts=0, connectActivity=2017-12-06T13:57:32:729, keepAliveSent=0, minRetry=28614, reconnectable, location=central.crashplanpro.com:443, transportPbK=null, transportPbKRequestable=true]; Session-null
[12.06.17 13:57:32.806 INFO  e-listen-1-1 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.56:443. connectFuture.isDone=true, channel=[id: 0xb19ddc89, L:/172.17.0.2:50314 ! R:/216.17.8.56:443]
@bigtfromaz

This comment has been minimized.

Copy link

@bigtfromaz bigtfromaz commented Dec 6, 2017

@kerrhome

This comment has been minimized.

Copy link
Author

@kerrhome kerrhome commented Dec 6, 2017

Yes we are for some content. We're in the process of migrating some build content to docker containers. I want to be able to backup some of the persistent volumes offsite. I thought using a crashplan-pro docker container to do this made sense. We'll just mount the volumes on the crashplan-pro container and tell crashplan-pro to watch it.

@jlesage

This comment has been minimized.

Copy link
Owner

@jlesage jlesage commented Dec 6, 2017

Do you need to use a proxy on your network?

@kerrhome

This comment has been minimized.

Copy link
Author

@kerrhome kerrhome commented Dec 6, 2017

No

@jlesage

This comment has been minimized.

Copy link
Owner

@jlesage jlesage commented Dec 6, 2017

And you tried to start with an empty appdata (/var/lib/docker/crashplan/data in your case)?

@kerrhome

This comment has been minimized.

Copy link
Author

@kerrhome kerrhome commented Dec 6, 2017

This is a good question. I started off with crashplan (not pro) and even another docker crashplan before that. I never got to the login, so I did not wipe crashplan/data. I'll try wiping that and restart this.

@kerrhome

This comment has been minimized.

Copy link
Author

@kerrhome kerrhome commented Dec 6, 2017

That was it. Sorry to waste time on that. I'm logged in fine now. Thank you!

@kerrhome kerrhome closed this Dec 6, 2017
@jlesage

This comment has been minimized.

Copy link
Owner

@jlesage jlesage commented Dec 6, 2017

Great, happy to see that it's working!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.