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

Troubleshooting Let's Encrypt Certificate Failures #269

Closed
own3mall opened this issue Mar 1, 2018 · 3 comments
Closed

Troubleshooting Let's Encrypt Certificate Failures #269

own3mall opened this issue Mar 1, 2018 · 3 comments

Comments

@own3mall
Copy link
Contributor

own3mall commented Mar 1, 2018

How do we figure out why Let's Encrypt is failing?

Is the reason why Let's Encrypt integration failed logged anywhere? I can't seem to figure out why my certificate won't pull / renew anymore.

I run this command:

docker run --restart=always -p 33333:33333 -p 443:443 -v /var/www/geoservices:/tmp/www -i -t fiorix/freegeoip -http :33333 -https :443 -public /tmp/www -letsencrypt -letsencrypt-email [email protected] -letsencrypt-hosts www.{MYDOMAIN},{MYDOMAIN}

and get this output when using https://

[error] 2018/03/01 17:31:33 http: TLS handshake error from {MYIP}: acme/autocert: missing certificate
[error] 2018/03/01 17:31:34 http: TLS handshake error from {MYIP}: acme/autocert: missing certificate

I had it working at one point, but now it appears to be failing, and I don't know how to troubleshoot the error code received from Let's Encrypt. Can anyone help?

@own3mall
Copy link
Contributor Author

own3mall commented Mar 1, 2018

@OlagStegan
Copy link

Thanks own3cloud, I've been fighting this one for the last 3 days without any progress or insight to the error.
The resolution appears to be simple - a rebuild with the updated "golang.org/x/crypto/acme/autocert"
As that seems like a priority, is their any news on when this will be upgraded?
or
as I have a valid cert outside docker how we could implement the external cert?

@fiorix
Copy link
Owner

fiorix commented Mar 14, 2018

Hey please see #268. Closing this.

@fiorix fiorix closed this as completed Mar 14, 2018
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

3 participants