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

Install instruction doesn't work, return gpg: keyserver receive failed: Network is unreachable #5291

Open
adonis-wyc opened this issue Jan 13, 2023 · 5 comments · May be fixed by rvm/rvm-site#346
Labels
Milestone

Comments

@adonis-wyc
Copy link

gpg export commands fail even with the 3 alternative URLs.
image
The response is here:
image

@mathieujobin
Copy link
Contributor

the workaround I found is to use a different server

gpg2 --keyserver keyserver.ubuntu.com --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB

@mathieujobin
Copy link
Contributor

maybe we should update the website... ? @pkuczynski ?

@mathieujobin mathieujobin reopened this Feb 15, 2023
@thomas-outing
Copy link

I agree. The website should be updated. I ran into this issue as well and the solution was to use the server specified above.

@pkuczynski
Copy link
Member

maybe we should update the website... ? @pkuczynski ?

Absolutely we should. Deployment fails currently. Would you find some time to work on rvm/rvm-site#346 @mathieujobin ?

@pkuczynski pkuczynski added this to the rvm-1.29.13 milestone Feb 16, 2023
@pkuczynski pkuczynski added the bug label Feb 16, 2023
@pkuczynski pkuczynski linked a pull request Feb 16, 2023 that will close this issue
@mathieujobin
Copy link
Contributor

FYI - It appears this is caused by gpg default server being down for like ~2 years

See last comment on https://unix.stackexchange.com/a/530784/29312
and git commit

https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blobdiff;f=configure.ac;h=e651db8a0df4f8ad76f08a0df64d1e099ca77938;hp=0bdd90ed728aa56bbd31719141bfe555b90950fb;hb=47c4e3e00;hpb=5fe4b978875271fb55f1f674ab545bed2b97a7a8

upgrading to latest gpg should work
and make sure you don't have it hardcoded in your config

$ grep keyserver ~/.gnupg/gpg.conf | sed 's/#.*$//'  | sort -u 

$

just in case rvm/rvm-site#365

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

Successfully merging a pull request may close this issue.

4 participants