Please describe what you are doing to trigger the bug:
Trying to make my linux Web GUI visible over HTTPS connection.
As per Gilbert’s response to previous support request 2191, I set settings.json like this:
{
“listening_address”: “:80”,
“https_address”: “:8080”,
“https_domain”: “my.domain.name”,
“temporary_directory”: “/home/brian/.duplicacy-web/repositories”,
“log_directory”: “/home/brian/.duplicacy-web/logs”,
“dark_mode”: false
}
And opened up the relevant ports in my firewall.
Please describe what you expect to happen (but doesn’t):
I expected to open a web page with the secure lock icon against the URL
Please describe what actually happens (the wrong behaviour):
Firefox reports:
This site can’t provide a secure connection
my.domain.name sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
and the log shows:
2020/02/08 12:38:36 Failed to marshal the configuration: json: error calling MarshalJSON for type main.StorageCredentials: No master password provided
2020/02/08 12:38:36 Temporary directory set to /home/brian/.duplicacy-web/repositories
2020/02/08 12:38:36 Duplicacy Web Edition 1.1.0 (818F2B)
2020/02/08 12:38:36 Duplicacy CLI 2.3.0
2020/02/08 12:38:37 http: TLS handshake error from 192.168.88.1:33064: 403 urn:acme:error:unauthorized: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See End of Life Plan for ACMEv1 - API Announcements - Let's Encrypt Community Support for details.
2020/02/08 12:38:37 http: TLS handshake error from 192.168.88.1:33062: acme/autocert: missing certificate
If I set the https_address & https_domain fields to empty strings, it all works fine, but only as an HTTP connection with a local numeric IP address.
The “MarshalJSON” error in the log also goes away when I blank out the https fields. Whether this relates to the ACME problem I have no idea.
Note that I have a current LetsEncrypt certificate for the domain name that I’m using, issued on 11-Dec-2019 and due to expire on 10-Mar-2020. My normal web server (running on the same machine) is visible via the domain name on both HTTP and HTTPS.
Regards
Brian