[Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)

[icepic0]

On 5/18/2024 at 2:30 AM, egtrev said:

Yes, the bottom of your screen is being cut off.  I see Done and Restore Files at the bottom.  My Display Width and Height are 1280 and 1024.

 

 

You do need a writable location to restore to.  I created a /RESTORES location that is mounted R/W and points to a normally empty folder rather than making the entire user share writable. 

 

Edited May 19 by icepic0

[egtrev]

5 hours ago, icepic0 said:

 

 

My height looks to have been set to 840, I made it 1024 and I can see the Restore button now. Thanks for the help.

[landS]

Howdy @Djoss

 

I just wanted to let you know that the Crashplan WebGui is indicating "CrashPlan wasn't able to upgrade but will reattempt in one hour"

 

Checking for updates on Unraid's Docker Container tab indicates this is up to date. 

 

As always, thank you greatly for maintaining this wonderful container. 

[Djoss]

8 minutes ago, landS said:

Howdy @Djoss

 

I just wanted to let you know that the Crashplan WebGui is indicating "CrashPlan wasn't able to upgrade but will reattempt in one hour"

 

Checking for updates on Unraid's Docker Container tab indicates this is up to date. 

 

As always, thank you greatly for maintaining this wonderful container. 

 

Yes, I'm working on this !

[watevriwanabi]

Is anyone else having an issue where their Crashplan is stuck on "Waiting for connection"?

[SelfSD]

@watevriwanabi Same here. Both my instances has been unable to connect for 2 days.

[fr500]

Sa,e ossie pver jere fpr 2.7 days now

[watevriwanabi]

Looking at mine now and it's back to "Backup running". Whatever the issue was seems to be resolved now.

[SelfSD]

It's working again for me as well. I also found the CrashPlan status page. Looks like they've had an issue for over a week. https://status.crashplan.com/

[NDDan]

After upgrading to the latest version of this container a few weeks ago, I'm unable to login to the gui. 
 

There is nothing special about the way I've configured this container, it's configured in bridge mode, and it's been working stably for almost two years.  I'm on unraid 6.12.10, docker engine configured for macvlan network type.

 

Suffice it to say, I can login to the CrashPlan website with the same set of credentials, and before upgrading never experienced an issue logging in through the docker app UI.  I do have 2FA enabled, which I noted is now part of the login pop-up for the GUI, which was absent in previous versions of this docker app; I also have a particularly long password, and I'm wondering if there's perhaps a length limitation in the GUI that didn't previously exist?

 

I've scoured the service.log.0 file, and there is nothing in the log I can locate that time-correlates with this login failure.  Login error pop-up attached.

 

[Djoss]

On 8/10/2024 at 9:25 AM, NDDan said:

After upgrading to the latest version of this container a few weeks ago, I'm unable to login to the gui. 
 

There is nothing special about the way I've configured this container, it's configured in bridge mode, and it's been working stably for almost two years.  I'm on unraid 6.12.10, docker engine configured for macvlan network type.

 

Suffice it to say, I can login to the CrashPlan website with the same set of credentials, and before upgrading never experienced an issue logging in through the docker app UI.  I do have 2FA enabled, which I noted is now part of the login pop-up for the GUI, which was absent in previous versions of this docker app; I also have a particularly long password, and I'm wondering if there's perhaps a length limitation in the GUI that didn't previously exist?

 

I've scoured the service.log.0 file, and there is nothing in the log I can locate that time-correlates with this login failure.  Login error pop-up attached.

 

Note that you can copy the displayed URL and paste it in your browser to do the login yourself.

 

If you would like to provide more details about the failure, you can edit the container setting and add a new variable named "CONTAINER_DEBUG", with a value of "1". You can then reproduce the problem and get the file /tmp/cp_login.log inside the container. You can send me its content in a private message.

[NDDan]

22 hours ago, Djoss said:

Note that you can copy the displayed URL and paste it in your browser to do the login yourself.

 

If you would like to provide more details about the failure, you can edit the container setting and add a new variable named "CONTAINER_DEBUG", with a value of "1". You can then reproduce the problem and get the file /tmp/cp_login.log inside the container. You can send me its content in a private message.

Copying and pasting the session URL into another browser to complete the login, worked perfectly, that's what I'll roll with.  Thanks @DJoss!