OpenSSL crypto error (bug #2175)


#1

Hi,
After accepting the terms for the letsencrypt https-setup, the server reports an error.

It’s the same error as reported in bug 2175.

Is there a workaround on this, or am I a sitting duck until this issue has been resolved?
I have no problem modifying the source code, but I wanted to ask if someone is on this before I did anything…


#2

After our dealing, we understood that it’s a UX and backend bug, where client side it does not check that the hostname is “saved” before activating LE and on the backend it does not check that the hostname is empty.

Ticket #2175 will fix those