In theory, you should be able to just remove the /etc/dehydrated/confconsole.hook.sh file. If it doesn't exist, running the Confconsole plugin will copy the latest version across.
But having said that, there are 2 different releases which fixed the initial problem, the first included a new bug. So to be 100% sure that all is as it should be, I'd urge you to carefully read through the complete v1.1.2 Release notes. I recommend that you follow all the steps as outlined in "How to install/update" section (it won't matter if you've already run some of them).
Once you've done that, you should have a valid Let's Encrypt cert. But to ensure that everything is as it should be, please reboot. If your server comes back up and everything is working as it should, you're good to go. If it doesn't, then please run these commands (as root, or prefix both with sudo):
systemctl disable add-water
reboot
Although having said that, the current release (v16.x) should just work. This issue only occurs in our old v15.x appliances. So you are probably best off getting the latest version if possible...
I recommend that you carefully read through the release notes
In theory, you should be able to just remove the /etc/dehydrated/confconsole.hook.sh file. If it doesn't exist, running the Confconsole plugin will copy the latest version across.
But having said that, there are 2 different releases which fixed the initial problem, the first included a new bug. So to be 100% sure that all is as it should be, I'd urge you to carefully read through the complete v1.1.2 Release notes. I recommend that you follow all the steps as outlined in "How to install/update" section (it won't matter if you've already run some of them).
Once you've done that, you should have a valid Let's Encrypt cert. But to ensure that everything is as it should be, please reboot. If your server comes back up and everything is working as it should, you're good to go. If it doesn't, then please run these commands (as root, or prefix both with sudo):
Although having said that, the current release (v16.x) should just work. This issue only occurs in our old v15.x appliances. So you are probably best off getting the latest version if possible...