I'm guessing that the spam filter ate the body of your post. I've just manually updated your account so that it can bypass the bulk of the spam filters now.
I'm guessing you were posting to say that you are struggling to get Let's Encrypt certificates via our Confconsole Let's Encrypt integration. As you are possibly aware, some recent changes Let's Encrypt changes have broken things.
Most of the issues should be resolved if you follow the instructions in the top post of this issue on GitHub. Although unfortunately, even with those steps in place, if you are using a number of domains, there is still a chance that you're hitting this issue.
FWIW, I did start having a hack on it over the weekend and have the basis of a workaround. Unfortunately, I haven't yet completed it and it still requires integration with the hook script and a write up to make it easy for users to apply.
If anyone (including you) is willing and able to have a look at my code and give it a test drive, that would be awesome! I'll comment on the other thread to encourage the guys who have posted there to have a look at this thread.
To give a bit more context, I have developed a new script (add-water-ctl) to control add-water (the mini-server that we use to serve the challenges). I have tested that independently and it seems to be much more reliable.
I have also done a bit of adjustment to our dehydrated-wrapper to accommodate the new add-water-ctl script (which I haven't tested so well). What still remains is tweaking the dehydrated hook script to leverage the changes that have been made. And then obviously the whole thing needs testing...
I hope to have something completed and tested as soon as possible, but unfortunately, I can't give you a hard timeframe. If anyone has the skills and the patience and are able to have a look (and update the hook script and do some testing) , then I would be eternally grateful! FWIW to test it out, then I suggest testing against the staging server (so you don't get blocked by the "proper" server if it still isn't working quite right).
Hi Dan
I'm guessing that the spam filter ate the body of your post. I've just manually updated your account so that it can bypass the bulk of the spam filters now.
I'm guessing you were posting to say that you are struggling to get Let's Encrypt certificates via our Confconsole Let's Encrypt integration. As you are possibly aware, some recent changes Let's Encrypt changes have broken things.
Most of the issues should be resolved if you follow the instructions in the top post of this issue on GitHub. Although unfortunately, even with those steps in place, if you are using a number of domains, there is still a chance that you're hitting this issue.
FWIW, I did start having a hack on it over the weekend and have the basis of a workaround. Unfortunately, I haven't yet completed it and it still requires integration with the hook script and a write up to make it easy for users to apply.
If anyone (including you) is willing and able to have a look at my code and give it a test drive, that would be awesome! I'll comment on the other thread to encourage the guys who have posted there to have a look at this thread.
To give a bit more context, I have developed a new script (add-water-ctl) to control add-water (the mini-server that we use to serve the challenges). I have tested that independently and it seems to be much more reliable.
I have also done a bit of adjustment to our dehydrated-wrapper to accommodate the new add-water-ctl script (which I haven't tested so well). What still remains is tweaking the dehydrated hook script to leverage the changes that have been made. And then obviously the whole thing needs testing...
I hope to have something completed and tested as soon as possible, but unfortunately, I can't give you a hard timeframe. If anyone has the skills and the patience and are able to have a look (and update the hook script and do some testing) , then I would be eternally grateful! FWIW to test it out, then I suggest testing against the staging server (so you don't get blocked by the "proper" server if it still isn't working quite right).