LetsEncrypt confirmation form is very badly designed
The LetsEncrypt enabling confirmation form is terrible.
First off, it requires that the user wait for something before they hit Continue, while the Continue button is readly enabled and very prominent. The instruction to wait on DNS change, is described in a tiny final sentence on the form. This is as bad UX as it gets.
Also, it doesn't describe how the user should check whether the change (adding the TXT record) was completed.
There's also two Cancel buttons for some reason.
Joris W
shared this idea
We have tested different scenarios but were unable to reproduce a scenario that is described in this feature request. Without detailed further information what is meant it is not possible to follow-up on this suggestion at this time. For that reason we must decline this request.
-- PD
-
Joris W
commented
Admittedly, I'm just a Plesk user so I don't know whether LetsEncrypt is an extension or something else. But I'm talking about the form that comes after choosing to enable LetsEncrypt for a site, in which it says to make sure a TXT entry is visible on the domain before proceeding.