Following a few recent posts in the forums (namely here and here) it's apparent that the most recent fix for Confconsole's Let's Encrypt plugin still has a bug...
It turns out that somewhere along the line the add-water service (our mini challenge server) is set to start on boot (not what we want at all). So whilst everything works fine when initially installing (as per the release notes), if/when the server is rebooted, add-water will (attempt to) start up. If it starts before the main webserver (which is likely) then it will stop the normal webserver from starting (because port 80 is already in use by add-water).
The workaround is to simply disable add-water:
systemctl disable add-water
Following a few recent posts in the forums (namely here and here) it's apparent that the most recent fix for Confconsole's Let's Encrypt plugin still has a bug...
It turns out that somewhere along the line the
add-waterservice (our mini challenge server) is set to start on boot (not what we want at all). So whilst everything works fine when initially installing (as per the release notes), if/when the server is rebooted, add-water will (attempt to) start up. If it starts before the main webserver (which is likely) then it will stop the normal webserver from starting (because port 80 is already in use by add-water).The workaround is to simply disable add-water: