unable to fetch crashplan server environment:insufficient randomness

[sol086]

Current Behavior

Updated to new docker container got the above response. rename container to .old recreated it from root with: docker run -d --name=jleasage-crashplan-pro-2 -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=8192M -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro

Expected Behavior

can't login get response "unable to fetch crashplan server environment:insufficient randomness"

Steps To Reproduce

No response

Environment

• OS:
• OS version:
• CPU:
• Docker version: latest container manager as of 08/06/24
• Device model: synolofy DS1817+
• Browser/OS: Crashplan Setup wrong docx.docx

Container creation

docker run -d --name=jleasage-crashplan-pro-2 -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=8192M -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro

Container log

don't know how to do

Container inspect

No response

Anything else?

Crashplan Setup wrong docx.docx

[jlesage]

Do you get the same error if you execute docker exec <container name> curl https://console.us2.crashplan.com ?

Also, could you share the output of the following commands:

• docker exec <container name> ls -l /dev/random
• docker exec <container name> ls -l /dev/urandom

[ThorEgilGit]

I got the same error when trying to log in through the small popup login window. If I copy the link and open the login in a separate tab, I am able to log in. Cumbersome but it works.

[jlesage]

Are you also using a Synology? See my previous comment for information that can be provided to help debug this problem.

[ThorEgilGit]

Yes, a DS1517+ running DSM 7.2.1

[sol086]

Do you get the same error if you execute docker exec <container name> curl https://console.us2.crashplan.com ?

Also, could you share the output of the following commands:

* `docker exec <container name> ls -l /dev/random`

* `docker exec <container name> ls -l /dev/urandom`

This is the output I get

root@SDYNAS:/volume1/docker/appdata# ls 'Configuration Json Files' crashplan-pro crashplan-pro-2 pihole unifi root@SDYNAS:/volume1/docker/appdata# docker exec crashplan-pro-2 ls -l /dev/random Error: No such container: crashplan-pro-2 root@SDYNAS:/volume1/docker/appdata# docker exec crashplan-pro-2 ls -l /dev/urandom Error: No such container: crashplan-pro-2 root@SDYNAS:/volume1/docker/appdata#

[sol086]

I got the same error when trying to log in through the small popup login window. If I copy the link and open the login in a separate tab, I am able to log in. Cumbersome but it works.

[jlesage]

It seems that you are not using the correct container name. You can run docker ps to see the name of the container.

[sol086]

It seems that you are not using the correct container name. You can run docker ps to see the name of the container.

This is what I get

root@SDYNAS:/volume1/docker/appdata# ls 'Configuration Json Files' crashplan-pro crashplan-pro-2 pihole unifi

root@SDYNAS:/volume1/docker/appdata# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8540a4e99cbf jlesage/crashplan-pro "/init" 2 days ago Up 8 hours 0.0.0.0:5800->5800/tcp, :::5800->5800/tcp, 5900/tcp jleasage-crashplan-pro-2

root@SDYNAS:/volume1/docker/appdata# docker exec 8540a4e99cbf ls -l /dev/random crw-rw-rw- 1 root root 1, 8 Aug 8 16:49 /dev/random root@SDYNAS:/volume1/docker/appdata# docker exec 8540a4e99cbf ls -l /dev/urandom crw-rw-rw- 1 root root 1, 9 Aug 8 16:49 /dev/urandom

root@SDYNAS:/volume1/docker/appdata#

root@SDYNAS:/volume1/docker/appdata# docker exec crashplan-pro ls -l /dev/random Error: No such container: crashplan-pro root@SDYNAS:/volume1/docker/appdata# docker exec crashplan-pro ls -l /dev/urandom Error: No such container: crashplan-pro root@SDYNAS:/volume1/docker/appdata#

[sol086]

here is my synology log file jleasage-crashplan-pro-2.json

[teiffs]

@sol086 you should do docker exec jleasage-crashplan-pro-2 ls -l /dev/random

[davidjjj]

I am experiencing the same issue

docker exec curl https://console.us2.crashplan.com

% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

docker exec ls -l /dev/random

crw-rw-rw- 1 root root 1, 8 Aug 18 14:10 /dev/random

docker exec ls -l /dev/urandom

crw-rw-rw- 1 root root 1, 9 Aug 18 14:10 /dev/urandom

[jacko306]

Hi, I also have the same issue when using the popup login window, it's ok if I copy the URL in the box to a new tab and log in that way.

root@xxxx:/volume1/docker/appdata# docker exec b1948d7fa402 curl https://console.us2.crashplan.com % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0

root@xxxx:/volume1/docker/appdata# docker exec b1948d7fa402 ls -l /dev/random crw-rw-rw- 1 root root 1, 8 Aug 4 15:52 /dev/random root@xxxx:/volume1/docker/appdata# docker exec b1948d7fa402 ls -l /dev/urandom crw-rw-rw- 1 root root 1, 9 Aug 4 15:52 /dev/urandom

[Darknight016]

I'm also seeing this issue and it looks like no solution has been found yet based on reading this thread.

Here's my output too, but it seems to be the same as everyone elses:

crw-rw-rw- 1 root root 1, 8 Oct 2 06:42 /dev/random crw-rw-rw- 1 root root 1, 9 Oct 2 06:42 /dev/urandom

Any ideas or suggestions on how to move forward? Appreciate all your work on this.

Edit: I see what people mean now by copying the URL from the side bar now and that it lets you login that way. A bit of an extra step, but at least there's a way.