-
Notifications
You must be signed in to change notification settings - Fork 819
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
DeserializationError: Deserialization error: Wrong directory fields #130
Comments
It's due to a change in the TOS. @thomastweets has been good enough to create a new version that works: https://hub.docker.com/r/thomastweets/docker-letsencrypt-nginx-proxy-companion/ But FYI, it doesn't work with the staging server. |
@alastaircoote that must be something else. Just got the same error while trying to get a cert for a It seems like this repo's image has got a right hash for the ToS because they haven't changed anything since August and I've been successfully getting certs for ASCII (non-IDE) domains since then. This issue is likely to be a duplicate for #130, which is probably still topical although marked as fixed. The reason why I decided to get a cert for an IDE domain is because they became supported by Letsencrypt just a few hours ago: letsencrypt/boulder#2277 (comment) |
Thank's @alastaircoote. I'll consider this for production. Do you know why it doesn't work with the staging server ? |
Yes, I take it back - it did work for me, and issued a cert for one subdomain. But now I'm trying with another and it's failing, so I'm not sure what is going on. The core problem seems to be relying on simp_le, which seems to be kind of dead: |
/cc @jsha |
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 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. |
@alastaircoote Great ! Works for me too (staging mode). I'll try with production mode. |
I agree that seems like the right choice. Older version of the |
@alastaircoote your fix is the good one. It works in production too. Thank's |
@Dabada why did you close this issue? Even if it works in |
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. |
It needs to stay open. I had the problem yesterday and this issue was necessary |
@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. |
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? |
@mlaitinen (and others), you are right. The issues is reopened. |
@alastaircoote fix still runs into #128 for me. |
@thatbudakguy that looks like a totally different error to me - this only fixes the |
@alastaircoote absolutely; sorry for off-topic - just wondering if anyone else has deployed the fix and also run into #128, since I'm at a loss |
@thatbudakguy Yes, I am having exactly the same problem. I use @alastaircoote fork and I am still running into #128. |
Glad it isn't just me! |
Just today I tried using this image for the first time and I encountered this issue. |
AFAIK, the problems described in this issue appear fixed when using the branch I made, and will hopefully go away when the pull request is merged This doesn't apply to the problems in #128 though. |
The Issue is not fixed for me using @thomastweets ... Still get this :
|
Oh yeah !!!! Thank you !!! ;) 👍 |
@alastaircoote hey man you are really dope! :D |
Thanks @alastaircoote |
@alastaircoote works like a charm, thanks, bro! |
Thanks @JrCs, for not forsaking us! ;) Switching back from @alastaircoote's. And thanks @alastaircoote for the quick fix! |
Happy to help. I strongly encourage everyone move back to this repo as I won't be maintaining my fork! |
Bug outlined in nginx-proxy/acme-companion#130 has now been resolved.
Got an error when starting a nodeBB virtual host container : DeserializationError: Deserialization error: Wrong directory fields
STEPS
Container nginx-proxy
Container nginx-letsencrypt
Container node-bb
Letsencrypt logs
docker logs -f nginx-letsencrypt
The text was updated successfully, but these errors were encountered: