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

Increase RSA key size for dummy certificate. #72

Closed
wants to merge 1 commit into from

Conversation

DocDagbjort
Copy link

With the key size set to 1024, startup of the 'nginx' container fails on some systems (see error message below). This results in what certbot suggests is a firewall issue, but is actually the lack of any container running to receive the authentication requests.

nginx | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
nginx | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
nginx | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
nginx | 10-listen-on-ipv6-by-default.sh: IPv6 listen already enabled, exiting
nginx | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
nginx | /docker-entrypoint.sh: Configuration complete; ready for start up
nginx | [redacted timestamp] [emerg] 1#1: SSL_CTX_use_certificate("/etc/letsencrypt/live/[redacted].com/fullchain.pem") failed (SSL: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small)
nginx | nginx: [emerg] SSL_CTX_use_certificate("/etc/letsencrypt/live/[redacted].com/fullchain.pem") failed (SSL: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small)
nginx exited with code 1

With the key size set to 1024, startup of the 'nginx' container fails on some systems (see error message below).  This results in what certbot suggests is a firewall issue, but is actually the lack of any container running to receive the authentication requests.
--------
nginx    | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
nginx    | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
nginx    | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
nginx    | 10-listen-on-ipv6-by-default.sh: IPv6 listen already enabled, exiting
nginx    | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
nginx    | /docker-entrypoint.sh: Configuration complete; ready for start up
nginx   | [redacted timestamp] [emerg] 1#1: SSL_CTX_use_certificate("/etc/letsencrypt/live/[redacted].com/fullchain.pem") failed (SSL: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small)
nginx    | nginx: [emerg] SSL_CTX_use_certificate("/etc/letsencrypt/live/[redacted].com/fullchain.pem") failed (SSL: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small)
nginx exited with code 1
--------
Copy link

@Koen1999 Koen1999 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I approve that this fix work. Newer nginx versions will complain that the old key size is too small. Verification does succeed with the modification made.

@weleoka
Copy link

weleoka commented Jun 15, 2020

Resolves issue #73?

@DocDagbjort
Copy link
Author

Resolves issue #73?

Yup, that appears to be the case.

@DocDagbjort
Copy link
Author

Resolves issue #73?

May also resolve #75. I'd link the pull request to these issues, but don't appear to have permissions to edit the 'Linked issues' section.

@234146326
Copy link

Resolves issue #73?

May also resolve #75. I'd link the pull request to these issues, but don't appear to have permissions to edit the 'Linked issues' section.

#75

Are our problems the same?

@Koen1999
Copy link

@wmnnd I think you could do some people a favor by pressing the merge button. Thanks!

@234146326
Copy link

Resolves issue #73?

May also resolve #75. I'd link the pull request to these issues, but don't appear to have permissions to edit the 'Linked issues' section.

I applied your suggestion, and the same error occurred.

forgive me!

@DocDagbjort
Copy link
Author

Resolves issue #73?

May also resolve #75. I'd link the pull request to these issues, but don't appear to have permissions to edit the 'Linked issues' section.

#75

Are our problems the same?

Looking at subsequent issue history, no. Your issue appears unrelated. Apologies.

@dtom90
Copy link

dtom90 commented Sep 13, 2020

@wmnnd Could this be merged? #80 is also a nice solution

@wmnnd
Copy link
Owner

wmnnd commented Nov 3, 2020

Thank you everyone for figuring this out, this has now been fixed via #77.

@wmnnd wmnnd closed this Nov 3, 2020
@wmnnd wmnnd mentioned this pull request Nov 3, 2020
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

Successfully merging this pull request may close these issues.

6 participants