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

SSL Certificates not generating #7

Closed
danipolo opened this issue Dec 9, 2016 · 7 comments
Closed

SSL Certificates not generating #7

danipolo opened this issue Dec 9, 2016 · 7 comments

Comments

@danipolo
Copy link

danipolo commented Dec 9, 2016

Hi,

I tried to install the Colabora compose and the HTTPS protocol is not responding.
I think the certificates are not generating. The folder for each subdomain on the cert/ folder is empty.

Here's the log:

letsencrypt-companion    | 2016-12-09 11:22:04,088:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
letsencrypt-companion    | Traceback (most recent call last):
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/simp_le.py", line 1401, in main
letsencrypt-companion    |     return main_with_exceptions(cli_args)
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/simp_le.py", line 1386, in main_with_exceptions
letsencrypt-companion    |     persist_new_data(args, existing_data)
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/simp_le.py", line 1282, in persist_new_data
letsencrypt-companion    |     client = registered_client(args, existing_data.account_key)
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/simp_le.py", line 1224, in registered_client
letsencrypt-companion    |     client = acme_client.Client(directory=args.server, key=key, net=net)
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/acme/client.py", line 63, in __init__
letsencrypt-companion    |     self.net.get(directory).json())
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/acme/messages.py", line 169, in from_json
letsencrypt-companion    |     raise jose.DeserializationError(str(error))
letsencrypt-companion    | DeserializationError: Deserialization error: Wrong directory fields
letsencrypt-companion    | 
letsencrypt-companion    | Unhandled error has happened, traceback is above
letsencrypt-companion    | 
letsencrypt-companion    | Debugging tips: -v improves output verbosity. Help is available under --help.
letsencrypt-companion    | Creating/renewal office.menorca24.com certificates... (office.menorca24.com)
letsencrypt-companion    | 2016-12-09 11:22:05,390:INFO:simp_le:1211: Generating new account key
letsencrypt-companion    | 2016-12-09 11:22:07,053:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
letsencrypt-companion    | Traceback (most recent call last):
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/simp_le.py", line 1401, in main
letsencrypt-companion    |     return main_with_exceptions(cli_args)
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/simp_le.py", line 1386, in main_with_exceptions
letsencrypt-companion    |     persist_new_data(args, existing_data)
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/simp_le.py", line 1282, in persist_new_data
letsencrypt-companion    |     client = registered_client(args, existing_data.account_key)
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/simp_le.py", line 1224, in registered_client
letsencrypt-companion    |     client = acme_client.Client(directory=args.server, key=key, net=net)
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/acme/client.py", line 63, in __init__
letsencrypt-companion    |     self.net.get(directory).json())
letsencrypt-companion    |   File "build/bdist.linux-x86_64/egg/acme/messages.py", line 169, in from_json
letsencrypt-companion    |     raise jose.DeserializationError(str(error))
letsencrypt-companion    | DeserializationError: Deserialization error: Wrong directory fields
letsencrypt-companion    | 
letsencrypt-companion    | Unhandled error has happened, traceback is above
letsencrypt-companion    | 
letsencrypt-companion    | Debugging tips: -v improves output verbosity. Help is available under --help.
letsencrypt-companion    | Sleep for 3600s

Thanks

@SnowMB
Copy link
Owner

SnowMB commented Dec 9, 2016

Hey,

this is an issue of the letsencrypt companion container that seems to have occured today.

See
nginx-proxy/acme-companion#130
nginx-proxy/acme-companion#131

@danipolo
Copy link
Author

danipolo commented Dec 9, 2016

Ok, as a temporal patch, just modify the letsencrypt image for:

alastaircoote/docker-letsencrypt-nginx-proxy-companion

@eriteric
Copy link

eriteric commented Dec 16, 2016

I tried switching out for alastaircoote/docker-letsencrypt-nginx-proxy-companion but now the site doesn't load - what am I missing? Was working before albeit no https because they weren't being generated, now they are generated and get a too many redirects error

@danipolo
Copy link
Author

Can you please show some debug logs?

@eriteric
Copy link

eriteric commented Dec 16, 2016

Sure thing:
Letsencrypt log: http://pastebin.com/A8BFCdiB
mariadb log: http://pastebin.com/SbZGHd8E
Indiehosters-nextcloud log: http://pastebin.com/uUBbf6q4
nginx log: http://pastebin.com/zycwgcK7
nginx-proxy log: http://pastebin.com/TwJRdVbd
collabora log: http://pastebin.com/WGsBZGF4
redis log: http://pastebin.com/wamKSPEb

Tried running the recommended delete/reset commands and docker-compose up -d again, getting the same result. Also tried thomastweets/docker-letsencrypt-nginx-proxy-companion

With a fresh install and alastaircoote/docker-letsencrypt-nginx-proxy-companion the site loads without https, then the pages constantly reload by themselves / tries to go to https but doesn't work (too many redirects error).
Tried collabora and reverseproxy versions.

@Pegasuz
Copy link

Pegasuz commented Dec 16, 2016

Changing the image to alastaircoote/docker-letsencrypt-nginx-proxy-companion did the trick for me. The certs are new being renewed.

@eriteric
Copy link

Mine is a separate issue. I had letsencrypt certs generated at one time, hit the issues above, but now have hit the letsencrypt rate limit and went with standard certs for now.

@SnowMB SnowMB mentioned this issue Dec 20, 2016
6 tasks
@SnowMB SnowMB closed this as completed in a97078d Dec 20, 2016
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