LetsEncrypt multiple subdomains not working? [FIXED]
-
hedgehog90
- Posts: 25
- Joined: Wed Sep 09, 2015 7:19 pm
LetsEncrypt multiple subdomains not working? [FIXED]
As I understand it, the usage of v-add-letsencrypt-domain is:
v-add-letsencrypt-domain USER DOMAIN [ALIASES] [RESTART] [NOTIFY]
The ALIASES parameter is a comma separated list, which I gleamed from looking at the source code.
For some reason any time I had more than one subdomain I would get this very unhelpful error message back:
LetsEncrypt challenge request 400
Sometimes, even if there was one subdomain it would return this error.
I don't understand why this was happening.
My guess is it couldn't reach the .well-known validation but nothing I was doing should have prevented that.
I've also tried using the web interface for this but it simply doesn't work, I get a very nondescript error every time, presumably it's running into the same issue.
[In the middle of writing this post I fixed my problem, but it was not at all intuitive and is a complete mystery]
After struggling with the web interface to enable LetsEncrypt support, trying it now all of a sudden worked.
Before I was getting a message saying that 2 of the certificate fields were blank (which they would be if you hadn't enabled SSL support) or the even more infuriating 'Error code: 3'
I have no idea what happened, but I just tried using the web interface again and it generated an SSL certificate for both my aliases and was working correctly.
I'd love to know what it was doing differently to my attempts using the command line...
BTW, this all came about when I received an email the other day saying my SSL renewal had failed with the 'LetsEncrypt challenge request 400' message.
After much hair pulling, it seems to have fixed itself.
I can only assume the system is riddled with bugs, but unfortunately I can't offer much more help than that.
I'd appreciate it if someone looked into this.
v-add-letsencrypt-domain USER DOMAIN [ALIASES] [RESTART] [NOTIFY]
The ALIASES parameter is a comma separated list, which I gleamed from looking at the source code.
For some reason any time I had more than one subdomain I would get this very unhelpful error message back:
LetsEncrypt challenge request 400
Sometimes, even if there was one subdomain it would return this error.
I don't understand why this was happening.
My guess is it couldn't reach the .well-known validation but nothing I was doing should have prevented that.
I've also tried using the web interface for this but it simply doesn't work, I get a very nondescript error every time, presumably it's running into the same issue.
[In the middle of writing this post I fixed my problem, but it was not at all intuitive and is a complete mystery]
After struggling with the web interface to enable LetsEncrypt support, trying it now all of a sudden worked.
Before I was getting a message saying that 2 of the certificate fields were blank (which they would be if you hadn't enabled SSL support) or the even more infuriating 'Error code: 3'
I have no idea what happened, but I just tried using the web interface again and it generated an SSL certificate for both my aliases and was working correctly.
I'd love to know what it was doing differently to my attempts using the command line...
BTW, this all came about when I received an email the other day saying my SSL renewal had failed with the 'LetsEncrypt challenge request 400' message.
After much hair pulling, it seems to have fixed itself.
I can only assume the system is riddled with bugs, but unfortunately I can't offer much more help than that.
I'd appreciate it if someone looked into this.