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 initialize bridge #34

Open
mmaderic opened this issue May 8, 2021 · 3 comments
Open

Cannot initialize bridge #34

mmaderic opened this issue May 8, 2021 · 3 comments

Comments

@mmaderic
Copy link

mmaderic commented May 8, 2021

Both Ubuntu 20.04 and CentOS 7.6 are stuck while trying to initialize using:

docker run --rm -it -v protonmail:/root shenxn/protonmail-bridge init

Both server instances are fresh deployments on DigitalOcean cloud provider.

[dev@centos-s-1vcpu-1gb-ams3-01 root]$ docker run --rm -it -v protonmail:/root shenxn/protonmail-bridge init
Unable to find image 'shenxn/protonmail-bridge:latest' locally
latest: Pulling from shenxn/protonmail-bridge
6e0aa5e7af40: Pull complete
d47239a868b3: Pull complete
49cbb10cca85: Pull complete
a8171dcf7e77: Pull complete
8e2a3ba9a014: Pull complete
f3be2eca7aa1: Pull complete
Digest: sha256:2a2dde3dd3f080349474d2a38086d569bec4176aaaf626a2d459c1fd631c2902
Status: Downloaded newer image for shenxn/protonmail-bridge:latest
+ [[ init == init ]]
+ gpg --generate-key --batch /protonmail/gpgparams
gpg: directory '/root/.gnupg' created
gpg: keybox '/root/.gnupg/pubring.kbx' created
gpg: Generating a basic OpenPGP key

this is where it gets stuck and doesn't move after this point. Waited for more than 10 minutes without results.

@cdestefano
Copy link

Had the same issue.

This post gave me a workaround. Kill the two processes, run init, and continue as normal.

#25 (comment)

@shenxn
Copy link
Owner

shenxn commented May 15, 2021

Seems you have problem generating gpg key. Try solutions here https://serverfault.com/questions/471412/gpg-gen-key-hangs-at-gaining-enough-entropy-on-centos-6.

@pushad
Copy link

pushad commented Sep 12, 2021

For anyone out there who still has this issue, you can get around this by installing rng-tools.
I'm running ubuntu, so installing it was as simple as sudo apt-get install rng-tools followed by sudo service rng-tools start.

Running the init command afterwards instantly resolved the issue.

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

No branches or pull requests

4 participants