-
Notifications
You must be signed in to change notification settings - Fork 94
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
GPG key is invalid or missing, you must provide "config.gpgSigningKey" #155
Comments
Hey there, I just got the same issue, my "solution" for that was to change the Dockerfile to use a newer tag like this:
the biggest difference was the docker image tag being "oidc-support" without it, it'll fail for me, it seems to be newest release as well: https://hub.docker.com/layers/atlassian/nucleus/oidc-support/images/sha256-4c038327eeed6edb01217af5894cf275c2e0b2dfddee3616ff4ed9404e24ded6?context=explore |
im still getting the same error using this docker image |
theris error in regex condition change
const keyMatch = keyImport.match(/ key ([A-Za-z0-9]+):/);
to
const keyMatch = keyImport.match(/ ([A-Z0-9]+):/); |
Could this problem possibly be related to the encryption algorithm used? I ran into it with a ECC key generated by gpg 2.3.7, but a RSA key generated by the same gpg version on the same machine appears to work. |
@pfn-shi Same thing happened with me - I went through the same steps with gpg's defaults (ECC) and kept getting an error that the key was invalid. After following the exact same steps but using RSA instead, nucleus started up properly. |
Hi im trying to run this on my aws server i used the docker file but i get this error
GPG key is invalid or missing, you must provide "config.gpgSigningKey"
.I also tried locally with docker
i also followed the instructions here #37 (comment) to generate the GPG keys
here is my config.js
The text was updated successfully, but these errors were encountered: