jlesage / docker-crashplan-pro

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

Server? #445

Closed Slartybart closed 7 months ago

Slartybart commented 7 months ago

Current Behavior

Am being asked for a server for the first time. Have tried all the ones I can find on the Crashplan webpage, I'm using Cloud US 5, apparently.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

Container creation

Docker

Container log

gulp!

Container inspect

No response

Anything else?

No response

Slartybart commented 7 months ago

Screenshot 2023-11-29 at 15 36 31

jlesage commented 7 months ago

Which CrashPlan plan/product did you subscribe to ? Did you create the container for the first time ?

If you are using the Small Business version, you can set the CRASHPLAN_SERVER_ADDRESS environment variable to SMB. See https://github.com/jlesage/docker-crashplan-pro#environment-variables

Slartybart commented 7 months ago

Thanks.... Yes, I tried that. It's definitely Crashplan for Small Business. I'll have another go.

jlesage commented 7 months ago

The SMB value is to be set to the environment variable CRASHPLAN_SERVER_ADDRESS. This variable is set during the creation of the container.

When CRASHPLAN_SERVER_ADDRESS=SMB, you should not be asked for a server address.

Slartybart commented 7 months ago

I'm really sorry... I'm obviously being really dim here. Now I'm getting this: Screenshot 2023-11-29 at 18 22 44

jcormier commented 7 months ago

Ive even tried putting the '=SMB' in

Drop the =

jlesage commented 7 months ago

The Value field should be set to SMB.

So the left field is CRASHPLAN_SERVER_ADDRESS, the right one is SMB.

Slartybart commented 7 months ago

Ok. Working now... I'd originally updated the container, but now I've deleted it and made a new one and used SMB in the last variable box. Thanks for everyone's help.......

Slartybart commented 7 months ago

Needed to delete container and re enter everything... NOT update as I'd normally done. After adopting my backup it seems to be scanning happily away.

jlesage commented 7 months ago

Great. Note that normally a container update would have been seamless, without requiring you to add CRASHPLAN_SERVER_ADDRESS nor to ask for a server address.