acme-companion: DeserializationError: Deserialization error: Wrong directory fields
Got an error when starting a nodeBB virtual host container : DeserializationError: Deserialization error: Wrong directory fields
STEPS
Container nginx-proxy
docker run -d -p 80:80 -p 443:443 \
--name nginx-proxy \
-v /srv/nginx/certs:/etc/nginx/certs:ro \
-v /etc/nginx/vhost.d \
-v /usr/share/nginx/html \
-v /var/run/docker.sock:/tmp/docker.sock:ro \
jwilder/nginx-proxy
Container nginx-letsencrypt
docker run -d \
--name nginx-letsencrypt \
-v /srv/nginx/certs:/etc/nginx/certs:rw \
--volumes-from nginx-proxy \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
jrcs/letsencrypt-nginx-proxy-companion
Container node-bb
docker run -e "VIRTUAL_HOST=xxx.ovh.net" \
-e "LETSENCRYPT_HOST=xxx.ovh.net" \
-e "LETSENCRYPT_TEST=true" \
--name node-bb \
--link node-bb-redis:redis \
-p 4567:4567 -P -t -i \
benlubar/nodebb:latest
Letsencrypt logs
docker logs -f nginx-letsencrypt
2016/12/08 13:01:38 Received event start for container 16ba23c35d3f
2016/12/08 13:01:53 Debounce minTimer fired
2016/12/08 13:01:53 Generated '/app/letsencrypt_service_data' from 3 containers
2016/12/08 13:01:53 Running '/app/update_certs'
Creating/renewal vps350014.ovh.net certificates... (vps350014.ovh.net)
2016-12-08 13:01:53,873:INFO:simp_le:1211: Generating new account key
2016-12-08 13:01:55,068:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
Traceback (most recent call last):
File "build/bdist.linux-x86_64/egg/simp_le.py", line 1401, in main
return main_with_exceptions(cli_args)
File "build/bdist.linux-x86_64/egg/simp_le.py", line 1386, in main_with_exceptions
persist_new_data(args, existing_data)
File "build/bdist.linux-x86_64/egg/simp_le.py", line 1282, in persist_new_data
client = registered_client(args, existing_data.account_key)
File "build/bdist.linux-x86_64/egg/simp_le.py", line 1224, in registered_client
client = acme_client.Client(directory=args.server, key=key, net=net)
File "build/bdist.linux-x86_64/egg/acme/client.py", line 63, in __init__
self.net.get(directory).json())
File "build/bdist.linux-x86_64/egg/acme/messages.py", line 169, in from_json
raise jose.DeserializationError(str(error))
DeserializationError: Deserialization error: Wrong directory fields
Unhandled error has happened, traceback is above
Debugging tips: -v improves output verbosity. Help is available under --help.
Sleep for 3600s
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 7
- Comments: 30
Commits related to this issue
- quickfix #130 — committed to ecobytes/nginx-letsencrypt by deleted user 8 years ago
- avoid connect error * see: https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/issues/130 — committed to machu/machu-jp by machu 8 years ago
- Switched back to JrCs image Bug outlined in JrCs/docker-letsencrypt-nginx-proxy-companion#130 has now been resolved. — committed to SystemDocker/nginx-proxy by flungo 7 years ago
@Dabada why did you close this issue? Even if it works in
alastaircoote/docker-letsencrypt-nginx-proxy-companion
it doesn’t mean that it works in the JrCs version (=this repository). IMO this is still an issue with jrcs.OK, I believe I have a fix. But I should preface this by saying that I am not well versed in either LetsEncrypt or SSL certs in general, so if I were you I wouldn’t trust me.
As mentioned in the issue I linked to, simp_le pull request #112 seems to fix the issue, but it hasn’t been merged. So I made a fork of this repo that switches to the
acme-0.8
branch before it builds:https://github.com/alastaircoote/docker-letsencrypt-nginx-proxy-companion
Then put that on Docker hub:
https://hub.docker.com/r/alastaircoote/docker-letsencrypt-nginx-proxy-companion/
It’s working for me. But as I say, this needs someone with more knowledge than me to look it over if you’re going to use it in a production environment or anything like that.
@trash-anger try using https://hub.docker.com/r/alastaircoote/docker-letsencrypt-nginx-proxy-companion/
Agree on keeping this open, if only so that people can find it on the issues page (it’s how I found it).
I’ve submitted pull request #132 to incorporate my change into this repo - I’d much rather do that than have more and more people using my branch, which I won’t be actively maintaining.
Happy to help. I strongly encourage everyone move back to this repo as I won’t be maintaining my fork!
Thanks @JrCs, for not forsaking us! 😉 Switching back from @alastaircoote’s.
And thanks @alastaircoote for the quick fix!
While this is slightly off-topic, is @JrCs even active on this project anymore? If not, wouldn’t it be better just to fork this repo and move to that permanently?
@Dabada this project is broken and a lot of users experiment this problem in production!
This issue should be re-open and @alastaircoote temp fixed should be merge until a better solution is fount.
@mlaitinen (and others), you are right. The issues is reopened.
@alastaircoote hey man you are really dope! 😄