Error requesting or renewing a certificate

When trying to enable a new Let’s Encrypt certificate in the panel, I get “Error: Let’s Encrypt acme/authz bad status 400 (example.com)”.

The following error appears in the log:
2025-06-08 22:24:13 v-add-letsencrypt-domain ‘Miscellaneous’ ‘unisite.com’ ‘www.unisite.com’ ‘’ [Error 15]

I also noticed that the certificates are not being renewed and some have even expired.

@sahsanu

No need to tag any person…

Check the docs and follow the steps for a proper debugging: SSL Certificates | Hestia Control Panel

Most likley you may hit the openfiöes limit, but debugging should show it.

1 Like

Hello, thank you for your reply.

I couldn’t find any solution through the documentation, because I don’t use Cloudflare, Nginx or Apache load correctly and IPv6 is not enabled for any of my sites.

When checking the URL mail.sitedauni.com on letsdebug.net everything seems fine and no errors are displayed.

I can only create a certificate by manually inserting the certificate and key in the domain panel.

When following the URL in the JSON response I found no clue in step 5 of the LE-Diversos-mail.sitedauni.com.log file. The problem occurs at step 6, which is when acme.sh tries to send the CSR (Certificate Signing Request) to Let’s Encrypt.

==[Step 5]==
- status: 200
- url: https://acme-v02.api.letsencrypt.org/acme/chall/2434490277/533186113442/HYoxmw
- nonce: fvgmYp28QJ029zHQMcgrLzThj_UeAliDvXUZdL7D5zi4v_Q4tFQ
- validation: https://acme-v02.api.letsencrypt.org/acme/chall/2434490277/533186113442/HYoxmw
- details: 
- answer: HTTP/2 200 
server: nginx
date: Mon, 09 Jun 2025 04:12:45 GMT
content-type: application/json
content-length: 553
boulder-requester: 2434490277
cache-control: public, max-age=0, no-cache
link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
link: <https://acme-v02.api.letsencrypt.org/acme/authz/2434490277/533186113442>;rel="up"
location: https://acme-v02.api.letsencrypt.org/acme/chall/2434490277/533186113442/HYoxmw
replay-nonce: fvgmYp28QJ029zHQMcgrLzThj_UeAliDvXUZdL7D5zi4v_Q4tFQ
x-frame-options: DENY
strict-transport-security: max-age=604800

{
  "type": "http-01",
  "url": "https://acme-v02.api.letsencrypt.org/acme/chall/2434490277/533186113442/HYoxmw",
  "status": "valid",
  "validated": "2025-06-09T04:12:39Z",
  "token": "eEpwFDGMLI153A5lNysDPDdpFOiub1Au5uOS5QD2o2c",
  "validationRecord": [
    {
      "url": "http://webmail.sitedauni.com/.well-known/acme-challenge/eEpwFDGMLI153A5lNysDPDdpFOiub1Au5uOS5QD2o2c",
      "hostname": "webmail.sitedauni.com",
      "port": "80",
      "addressesResolved": [
        "38.210.210.203"
      ],
      "addressUsed": "38.210.210.203"
    }
  ]
}

==[Step 6]==
- status: 400
- nonce: cUIsp5VzrXL9dKBTWIt7i4DAxQjRUOR-lzH0DHINohHMH3aGq7Y
- payload: {"csr":""}
- certificate: 
- answer: HTTP/2 400 
server: nginx
date: Mon, 09 Jun 2025 04:12:53 GMT
content-type: application/problem+json
content-length: 158
boulder-requester: 2434490277
cache-control: public, max-age=0, no-cache
link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
replay-nonce: cUIsp5VzrXL9dKBTWIt7i4DAxQjRUOR-lzH0DHINohHMH3aGq7Y

{
  "type": "urn:ietf:params:acme:error:malformed",
  "detail": "Error parsing certificate request: asn1: syntax error: sequence truncated",
  "status": 400
}

Could updating Nginx via apt have any relation to the problem? This was done some time ago and updated to nginx-1.27.5

There isn’t payload, seems Hestia is not generating the CSR.

Could you please show the output of these commands?

v-generate-ssl-cert "mail.sitedauni.com" "[email protected]" "US" "California" "San Francisco" "Hestia" "IT" "webmail.sitedauni.com" | tail -n1 | awk '{print $2}'

You should get a temporal dir like /tmp/tmp.kgcirK2Zka, with the dir you get, execute this replacing the dir name:

openssl req -in /tmp/tmp.kgcirK2Zka/mail.sitedauni.com.csr | cat | base64 | tr '+/' '-_' | tr -d '\r\n='
root@painel:~# v-generate-ssl-cert "mail.sitedauni.com" "[email protected]" "US" "California" "San Francisco" "Hestia" "IT" "webmail.sitedauni.com" | tail -n1 | awk '{print $2}'
/tmp/tmp.QmOuS3DV1Q
root@painel:~# openssl req -in /tmp/tmp.QmOuS3DV1Q/mail.sitedauni.com.csr | cat | base64 | tr '+/' '-_' | tr -d '\r\n='
Can't open "/tmp/tmp.QmOuS3DV1Q/mail.sitedauni.com.csr" for reading, No such file or directory
40477943CC7F0000:error:80000002:system library:BIO_new_file:No such file or directory:../crypto/bio/bss_file.c:67:calling fopen(/tmp/tmp.QmOuS3DV1Q/mail.sitedauni.com.csr, r)
40477943CC7F0000:error:10000080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:75:
Unable to load X509 request
root@painel:~#
df -h /tmp
ls -la /tmp/tmp.QmOuS3DV1Q
root@painel:~# df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2       937G  340G  549G  39% /
root@painel:~# ls -la /tmp/tmp.cttpkBzVS8
total 3988
drw-rw----  2 root root    4096 jun  9 23:35 .
drwxrwxrwt 23 root root 4063232 jun  9 23:35 ..
-rw-r--r--  1 root root    3272 jun  9 23:35 mail.sitedauni.com.key
root@painel:~#

You should also have mail.sitedauni.com.crt and mail.sitedauni.com.csr files.

Let’s debug it:

bash -x /usr/local/hestia/bin/v-generate-ssl-cert "mail.sitedauni.com" "[email protected]" "US" "California" "San Francisco" "Hestia" "IT" "webmail.sitedauni.com" 2>&1 | tee /tmp/v-generate-ssl.debug

As the output will be large, send it to me with nc:

apt install netcat-openbsd -y
nc p.27a.net 9999 < /tmp/v-generate-ssl.debug
2 Likes

Sent. If you prefer, I can add you as a user.

The issue is generating the crt and csr:

if [ -z "$aliases" ]; then
        openssl req -sha256 -new \
                -batch \
                -subj "$subj" \
                -key $domain.key \
                -out $domain.csr > /dev/null 2>&1
else
        for alias in $(echo $domain,$aliases | tr ',' '\n' | sort -u); do
                if [[ "$alias" = *[![:ascii:]]* ]]; then
                        alias=$(idn2 --quiet $alias)
                fi
                dns_aliases="${dns_aliases}DNS:$alias,"
        done
        dns_aliases=$(echo $dns_aliases | sed "s/,$//")
        if [ -e "/etc/ssl/openssl.cnf" ]; then
                ssl_conf='/etc/ssl/openssl.cnf'
        else
                ssl_conf="/etc/pki/tls/openssl.cnf"
        fi

        openssl req -sha256 -new \
                -batch \
                -subj "$subj" \
                -key $domain.key \
                -reqexts SAN \
                -config <(cat $ssl_conf \
                        <(printf "[SAN]\nsubjectAltName=$dns_aliases")) \
                -out $domain.csr > /dev/null 2>&1
fi

# Generate the cert 1 year
openssl x509 -req -sha256 \
        -days $DAYS \
        -in $domain.csr \
        -signkey $domain.key \
        -out $domain.crt > /dev/null 2>&1

As the files has not been created, this section fails to get the crt and csr:

# Listing certificates
if [ -e "$domain.crt" ]; then
        crt=$(cat $domain.crt | sed ':a;N;$!ba;s/\n/\\n/g')
fi

[...]

if [ -e "$domain.csr" ]; then
        csr=$(cat $domain.csr | sed ':a;N;$!ba;s/\n/\\n/g')
fi

Before trying to execute the openssl commands manually, please, show the output of these commands:

ls -l /etc/ssl/openssl.cnf
cat -A /etc/ssl/openssl.cnf
root@painel:~# ls -l /etc/ssl/openssl.cnf
-rw-r--r-- 1 root root 13794 abr 29 06:55 /etc/ssl/openssl.cnf
root@painel:~# cat -A /etc/ssl/openssl.cnf
#$
# OpenSSL example configuration file.$
# See doc/man5/config.pod for more info.$
#$
# This is mostly being used for generation of certificate requests,$
# but may be used for auto loading of providers$
$
# Note that you can include other files from the main configuration$
# file using the .include directive.$
#.include filename$
$
# This definition stops the following lines choking if HOME isn't$
# defined.$
HOME                    = .$
$
 # Use this in order to automatically load providers.$
openssl_conf = openssl_init$
$
# Comment out the next line to ignore configuration errors$
config_diagnostics = 1$
$
# Extra OBJECT IDENTIFIER info:$
# oid_file       = $ENV::HOME/.oid$
oid_section = new_oids$
$
# To use this configuration file with the "-extfile" option of the$
# "openssl x509" utility, name here the section containing the$
# X.509v3 extensions to use:$
# extensions            =$
# (Alternatively, use a configuration file that has only$
# X.509v3 extensions in its main [= default] section.)$
$
[ new_oids ]$
# We can add new OIDs in here for use by 'ca', 'req' and 'ts'.$
# Add a simple OID like this:$
# testoid1=1.2.3.4$
# Or use config file substitution like this:$
# testoid2=${testoid1}.5.6$
$
# Policies used by the TSA examples.$
tsa_policy1 = 1.2.3.4.1$
tsa_policy2 = 1.2.3.4.5.6$
tsa_policy3 = 1.2.3.4.5.7$
$
# For FIPS$
# Optionally include a file that is generated by the OpenSSL fipsinstall$
# application. This file contains configuration data required by the OpenSSL$
# fips provider. It contains a named section e.g. [fips_sect] which is$
# referenced from the [provider_sect] below.$
# Refer to the OpenSSL security policy for more information.$
# .include fipsmodule.cnf$
$
[openssl_init]$
providers = provider_sect$
ssl_conf = ssl_sect$
$
# List of providers to load$
[provider_sect]$
default = default_sect$
# The fips section name should match the section name inside the$
# included fipsmodule.cnf.$
# fips = fips_sect$
$
# If no providers are activated explicitly, the default one is activated implicitly.$
# See man 7 OSSL_PROVIDER-default for more details.$
#$
# If you add a section explicitly activating any other provider(s), you most$
# probably need to explicitly activate the default provider, otherwise it$
# becomes unavailable in openssl.  As a consequence applications depending on$
# OpenSSL may not work correctly which could lead to significant system$
# problems including inability to remotely access the system.$
[default_sect]$
# activate = 1$
$
$
####################################################################$
[ ca ]$
default_ca      = CA_default            # The default ca section$
$
####################################################################$
[ CA_default ]$
$
dir             = ./demoCA              # Where everything is kept$
certs           = $dir/certs            # Where the issued certs are kept$
crl_dir         = $dir/crl              # Where the issued crl are kept$
database        = $dir/index.txt        # database index file.$
#unique_subject = no                    # Set to 'no' to allow creation of$
                                        # several certs with same subject.$
new_certs_dir   = $dir/newcerts         # default place for new certs.$
$
certificate     = $dir/cacert.pem       # The CA certificate$
serial          = $dir/serial           # The current serial number$
crlnumber       = $dir/crlnumber        # the current crl number$
                                        # must be commented out to leave a V1 CRL$
crl             = $dir/crl.pem          # The current CRL$
private_key     = $dir/private/cakey.pem# The private key$
$
x509_extensions = usr_cert              # The extensions to add to the cert$
$
# Comment out the following two lines for the "traditional"$
# (and highly broken) format.$
name_opt        = ca_default            # Subject Name options$
cert_opt        = ca_default            # Certificate field options$
$
# Extension copying option: use with caution.$
# copy_extensions = copy$
$
# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs$
# so this is commented out by default to leave a V1 CRL.$
# crlnumber must also be commented out to leave a V1 CRL.$
# crl_extensions        = crl_ext$
$
default_days    = 365                   # how long to certify for$
default_crl_days= 30                    # how long before next CRL$
default_md      = default               # use public key default MD$
preserve        = no                    # keep passed DN ordering$
$
# A few difference way of specifying how similar the request should look$
# For type CA, the listed attributes must be the same, and the optional$
# and supplied fields are just that :-)$
policy          = policy_match$
$
# For the CA policy$
[ policy_match ]$
countryName             = match$
stateOrProvinceName     = match$
organizationName        = match$
organizationalUnitName  = optional$
commonName              = supplied$
emailAddress            = optional$
$
# For the 'anything' policy$
# At this point in time, you must list all acceptable 'object'$
# types.$
[ policy_anything ]$
countryName             = optional$
stateOrProvinceName     = optional$
localityName            = optional$
organizationName        = optional$
organizationalUnitName  = optional$
commonName              = supplied$
emailAddress            = optional$
$
####################################################################$
[ req ]$
default_bits            = 2048$
default_keyfile         = privkey.pem$
distinguished_name      = req_distinguished_name$
attributes              = req_attributes$
x509_extensions = v3_ca # The extensions to add to the self signed cert$
$
# Passwords for private keys if not present they will be prompted for$
# input_password = secret$
# output_password = secret$
$
# This sets a mask for permitted string types. There are several options.$
# default: PrintableString, T61String, BMPString.$
# pkix   : PrintableString, BMPString (PKIX recommendation before 2004)$
# utf8only: only UTF8Strings (PKIX recommendation after 2004).$
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).$
# MASK:XXXX a literal mask value.$
# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.$
string_mask = utf8only$
$
# req_extensions = v3_req # The extensions to add to a certificate request$
$
[ req_distinguished_name ]$
countryName                     = Country Name (2 letter code)$
countryName_default             = AU$
countryName_min                 = 2$
countryName_max                 = 2$
$
stateOrProvinceName             = State or Province Name (full name)$
stateOrProvinceName_default     = Some-State$
$
localityName                    = Locality Name (eg, city)$
$
0.organizationName              = Organization Name (eg, company)$
0.organizationName_default      = Internet Widgits Pty Ltd$
$
# we can do this but it is not needed normally :-)$
#1.organizationName             = Second Organization Name (eg, company)$
#1.organizationName_default     = World Wide Web Pty Ltd$
$
organizationalUnitName          = Organizational Unit Name (eg, section)$
#organizationalUnitName_default =$
$
commonName                      = Common Name (e.g. server FQDN or YOUR name)$
commonName_max                  = 64$
$
emailAddress                    = Email Address$
emailAddress_max                = 64$
$
# SET-ex3                       = SET extension number 3$
$
[ req_attributes ]$
challengePassword               = A challenge password$
challengePassword_min           = 4$
challengePassword_max           = 20$
$
unstructuredName                = An optional company name$
$
[ usr_cert ]$
$
# These extensions are added when 'ca' signs a request.$
$
# This goes against PKIX guidelines but some CAs do it and some software$
# requires this to avoid interpreting an end user certificate as a CA.$
$
basicConstraints=CA:FALSE$
$
# This is typical in keyUsage for a client certificate.$
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment$
$
# PKIX recommendations harmless if included in all certificates.$
subjectKeyIdentifier=hash$
authorityKeyIdentifier=keyid,issuer$
$
# This stuff is for subjectAltName and issuerAltname.$
# Import the email address.$
# subjectAltName=email:copy$
# An alternative to produce certificates that aren't$
# deprecated according to PKIX.$
# subjectAltName=email:move$
$
# Copy subject details$
# issuerAltName=issuer:copy$
$
# This is required for TSA certificates.$
# extendedKeyUsage = critical,timeStamping$
$
[ v3_req ]$
$
# Extensions to add to a certificate request$
$
basicConstraints = CA:FALSE$
keyUsage = nonRepudiation, digitalSignature, keyEncipherment$
$
[ v3_ca ]$
$
$
# Extensions for a typical CA$
$
$
# PKIX recommendation.$
$
subjectKeyIdentifier=hash$
$
authorityKeyIdentifier=keyid:always,issuer$
$
basicConstraints = critical,CA:true$
$
# Key usage: this is typical for a CA certificate. However since it will$
# prevent it being used as an test self-signed certificate it is best$
# left out by default.$
# keyUsage = cRLSign, keyCertSign$
$
# Include email address in subject alt name: another PKIX recommendation$
# subjectAltName=email:copy$
# Copy issuer details$
# issuerAltName=issuer:copy$
$
# DER hex encoding of an extension: beware experts only!$
# obj=DER:02:03$
# Where 'obj' is a standard or added object$
# You can even override a supported extension:$
# basicConstraints= critical, DER:30:03:01:01:FF$
$
[ crl_ext ]$
$
# CRL extensions.$
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.$
$
# issuerAltName=issuer:copy$
authorityKeyIdentifier=keyid:always$
$
[ proxy_cert_ext ]$
# These extensions should be added when creating a proxy certificate$
$
# This goes against PKIX guidelines but some CAs do it and some software$
# requires this to avoid interpreting an end user certificate as a CA.$
$
basicConstraints=CA:FALSE$
$
# This is typical in keyUsage for a client certificate.$
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment$
$
# PKIX recommendations harmless if included in all certificates.$
subjectKeyIdentifier=hash$
authorityKeyIdentifier=keyid,issuer$
$
# This stuff is for subjectAltName and issuerAltname.$
# Import the email address.$
# subjectAltName=email:copy$
# An alternative to produce certificates that aren't$
# deprecated according to PKIX.$
# subjectAltName=email:move$
$
# Copy subject details$
# issuerAltName=issuer:copy$
$
# This really needs to be in place for it to be a proxy certificate.$
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo$
$
####################################################################$
[ tsa ]$
$
default_tsa = tsa_config1       # the default TSA section$
$
[ tsa_config1 ]$
$
# These are used by the TSA reply generation only.$
dir             = ./demoCA              # TSA root directory$
serial          = $dir/tsaserial        # The current serial number (mandatory)$
crypto_device   = builtin               # OpenSSL engine to use for signing$
signer_cert     = $dir/tsacert.pem      # The TSA signing certificate$
                                        # (optional)$
certs           = $dir/cacert.pem       # Certificate chain to include in reply$
                                        # (optional)$
signer_key      = $dir/private/tsakey.pem # The TSA private key (optional)$
signer_digest  = sha256                 # Signing digest to use. (Optional)$
default_policy  = tsa_policy1           # Policy if request did not specify it$
                                        # (optional)$
other_policies  = tsa_policy2, tsa_policy3      # acceptable policies (optional)$
digests     = sha1, sha256, sha384, sha512  # Acceptable message digests (mandatory)$
accuracy        = secs:1, millisecs:500, microsecs:100  # (optional)$
clock_precision_digits  = 0     # number of digits after dot. (optional)$
ordering                = yes   # Is ordering defined for timestamps?$
                                # (optional, default: no)$
tsa_name                = yes   # Must the TSA name be included in the reply?$
                                # (optional, default: no)$
ess_cert_id_chain       = no    # Must the ESS cert id chain be included?$
                                # (optional, default: no)$
ess_cert_id_alg         = sha1  # algorithm to compute certificate$
                                # identifier (optional, default: sha1)$
$
[insta] # CMP using Insta Demo CA$
# Message transfer$
server = pki.certificate.fi:8700$
# proxy = # set this as far as needed, e.g., http://192.168.1.1:8080$
# tls_use = 0$
path = pkix/$
$
# Server authentication$
recipient = "/C=FI/O=Insta Demo/CN=Insta Demo CA" # or set srvcert or issuer$
ignore_keyusage = 1 # potentially needed quirk$
unprotected_errors = 1 # potentially needed quirk$
extracertsout = insta.extracerts.pem$
$
# Client authentication$
ref = 3078 # user identification$
secret = pass:insta # can be used for both client and server side$
$
# Generic message options$
cmd = ir # default operation, can be overridden on cmd line with, e.g., kur$
$
# Certificate enrollment$
subject = "/CN=openssl-cmp-test"$
newkey = insta.priv.pem$
out_trusted = insta.ca.crt$
certout = insta.cert.pem$
$
[pbm] # Password-based protection for Insta CA$
# Server and client authentication$
ref = $insta::ref # 3078$
secret = $insta::secret # pass:insta$
$
[signature] # Signature-based protection for Insta CA$
# Server authentication$
trusted = insta.ca.crt # does not include keyUsage digitalSignature$
$
# Client authentication$
secret = # disable PBM$
key = $insta::newkey # insta.priv.pem$
cert = $insta::certout # insta.cert.pem$
$
[ir]$
cmd = ir$
$
[cr]$
cmd = cr$
$
[kur]$
# Certificate update$
cmd = kur$
oldcert = $insta::certout # insta.cert.pem$
$
[rr]$
# Certificate revocation$
cmd = rr$
oldcert = $insta::certout # insta.cert.pem$
$
[ssl_sect]$
system_default = system_default_sect$
system_default = hestia_openssl_sect$
$
[hestia_openssl_sect]$
Ciphersuites = TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384$
Options = PrioritizeChaCha$
$
[system_default_sect]$
CipherString = DEFAULT:@SECLEVEL=2root@painel:~#

Edit the file /etc/ssl/openssl.cnf and remove this line:

system_default = system_default_sect

Once done, try again.

root@painel:~# ls -l /etc/ssl/openssl.cnf
-rw-r--r-- 1 root root 13796 jun 10 12:36 /etc/ssl/openssl.cnf
root@painel:~# cat -A /etc/ssl/openssl.cnf
#$
# OpenSSL example configuration file.$
# See doc/man5/config.pod for more info.$
#$
# This is mostly being used for generation of certificate requests,$
# but may be used for auto loading of providers$
$
# Note that you can include other files from the main configuration$
# file using the .include directive.$
#.include filename$
$
# This definition stops the following lines choking if HOME isn't$
# defined.$
HOME                    = .$
$
 # Use this in order to automatically load providers.$
openssl_conf = openssl_init$
$
# Comment out the next line to ignore configuration errors$
config_diagnostics = 1$
$
# Extra OBJECT IDENTIFIER info:$
# oid_file       = $ENV::HOME/.oid$
oid_section = new_oids$
$
# To use this configuration file with the "-extfile" option of the$
# "openssl x509" utility, name here the section containing the$
# X.509v3 extensions to use:$
# extensions            =$
# (Alternatively, use a configuration file that has only$
# X.509v3 extensions in its main [= default] section.)$
$
[ new_oids ]$
# We can add new OIDs in here for use by 'ca', 'req' and 'ts'.$
# Add a simple OID like this:$
# testoid1=1.2.3.4$
# Or use config file substitution like this:$
# testoid2=${testoid1}.5.6$
$
# Policies used by the TSA examples.$
tsa_policy1 = 1.2.3.4.1$
tsa_policy2 = 1.2.3.4.5.6$
tsa_policy3 = 1.2.3.4.5.7$
$
# For FIPS$
# Optionally include a file that is generated by the OpenSSL fipsinstall$
# application. This file contains configuration data required by the OpenSSL$
# fips provider. It contains a named section e.g. [fips_sect] which is$
# referenced from the [provider_sect] below.$
# Refer to the OpenSSL security policy for more information.$
# .include fipsmodule.cnf$
$
[openssl_init]$
providers = provider_sect$
ssl_conf = ssl_sect$
$
# List of providers to load$
[provider_sect]$
default = default_sect$
# The fips section name should match the section name inside the$
# included fipsmodule.cnf.$
# fips = fips_sect$
$
# If no providers are activated explicitly, the default one is activated implicitly.$
# See man 7 OSSL_PROVIDER-default for more details.$
#$
# If you add a section explicitly activating any other provider(s), you most$
# probably need to explicitly activate the default provider, otherwise it$
# becomes unavailable in openssl.  As a consequence applications depending on$
# OpenSSL may not work correctly which could lead to significant system$
# problems including inability to remotely access the system.$
[default_sect]$
# activate = 1$
$
$
####################################################################$
[ ca ]$
default_ca      = CA_default            # The default ca section$
$
####################################################################$
[ CA_default ]$
$
dir             = ./demoCA              # Where everything is kept$
certs           = $dir/certs            # Where the issued certs are kept$
crl_dir         = $dir/crl              # Where the issued crl are kept$
database        = $dir/index.txt        # database index file.$
#unique_subject = no                    # Set to 'no' to allow creation of$
                                        # several certs with same subject.$
new_certs_dir   = $dir/newcerts         # default place for new certs.$
$
certificate     = $dir/cacert.pem       # The CA certificate$
serial          = $dir/serial           # The current serial number$
crlnumber       = $dir/crlnumber        # the current crl number$
                                        # must be commented out to leave a V1 CRL$
crl             = $dir/crl.pem          # The current CRL$
private_key     = $dir/private/cakey.pem# The private key$
$
x509_extensions = usr_cert              # The extensions to add to the cert$
$
# Comment out the following two lines for the "traditional"$
# (and highly broken) format.$
name_opt        = ca_default            # Subject Name options$
cert_opt        = ca_default            # Certificate field options$
$
# Extension copying option: use with caution.$
# copy_extensions = copy$
$
# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs$
# so this is commented out by default to leave a V1 CRL.$
# crlnumber must also be commented out to leave a V1 CRL.$
# crl_extensions        = crl_ext$
$
default_days    = 365                   # how long to certify for$
default_crl_days= 30                    # how long before next CRL$
default_md      = default               # use public key default MD$
preserve        = no                    # keep passed DN ordering$
$
# A few difference way of specifying how similar the request should look$
# For type CA, the listed attributes must be the same, and the optional$
# and supplied fields are just that :-)$
policy          = policy_match$
$
# For the CA policy$
[ policy_match ]$
countryName             = match$
stateOrProvinceName     = match$
organizationName        = match$
organizationalUnitName  = optional$
commonName              = supplied$
emailAddress            = optional$
$
# For the 'anything' policy$
# At this point in time, you must list all acceptable 'object'$
# types.$
[ policy_anything ]$
countryName             = optional$
stateOrProvinceName     = optional$
localityName            = optional$
organizationName        = optional$
organizationalUnitName  = optional$
commonName              = supplied$
emailAddress            = optional$
$
####################################################################$
[ req ]$
default_bits            = 2048$
default_keyfile         = privkey.pem$
distinguished_name      = req_distinguished_name$
attributes              = req_attributes$
x509_extensions = v3_ca # The extensions to add to the self signed cert$
$
# Passwords for private keys if not present they will be prompted for$
# input_password = secret$
# output_password = secret$
$
# This sets a mask for permitted string types. There are several options.$
# default: PrintableString, T61String, BMPString.$
# pkix   : PrintableString, BMPString (PKIX recommendation before 2004)$
# utf8only: only UTF8Strings (PKIX recommendation after 2004).$
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).$
# MASK:XXXX a literal mask value.$
# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.$
string_mask = utf8only$
$
# req_extensions = v3_req # The extensions to add to a certificate request$
$
[ req_distinguished_name ]$
countryName                     = Country Name (2 letter code)$
countryName_default             = AU$
countryName_min                 = 2$
countryName_max                 = 2$
$
stateOrProvinceName             = State or Province Name (full name)$
stateOrProvinceName_default     = Some-State$
$
localityName                    = Locality Name (eg, city)$
$
0.organizationName              = Organization Name (eg, company)$
0.organizationName_default      = Internet Widgits Pty Ltd$
$
# we can do this but it is not needed normally :-)$
#1.organizationName             = Second Organization Name (eg, company)$
#1.organizationName_default     = World Wide Web Pty Ltd$
$
organizationalUnitName          = Organizational Unit Name (eg, section)$
#organizationalUnitName_default =$
$
commonName                      = Common Name (e.g. server FQDN or YOUR name)$
commonName_max                  = 64$
$
emailAddress                    = Email Address$
emailAddress_max                = 64$
$
# SET-ex3                       = SET extension number 3$
$
[ req_attributes ]$
challengePassword               = A challenge password$
challengePassword_min           = 4$
challengePassword_max           = 20$
$
unstructuredName                = An optional company name$
$
[ usr_cert ]$
$
# These extensions are added when 'ca' signs a request.$
$
# This goes against PKIX guidelines but some CAs do it and some software$
# requires this to avoid interpreting an end user certificate as a CA.$
$
basicConstraints=CA:FALSE$
$
# This is typical in keyUsage for a client certificate.$
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment$
$
# PKIX recommendations harmless if included in all certificates.$
subjectKeyIdentifier=hash$
authorityKeyIdentifier=keyid,issuer$
$
# This stuff is for subjectAltName and issuerAltname.$
# Import the email address.$
# subjectAltName=email:copy$
# An alternative to produce certificates that aren't$
# deprecated according to PKIX.$
# subjectAltName=email:move$
$
# Copy subject details$
# issuerAltName=issuer:copy$
$
# This is required for TSA certificates.$
# extendedKeyUsage = critical,timeStamping$
$
[ v3_req ]$
$
# Extensions to add to a certificate request$
$
basicConstraints = CA:FALSE$
keyUsage = nonRepudiation, digitalSignature, keyEncipherment$
$
[ v3_ca ]$
$
$
# Extensions for a typical CA$
$
$
# PKIX recommendation.$
$
subjectKeyIdentifier=hash$
$
authorityKeyIdentifier=keyid:always,issuer$
$
basicConstraints = critical,CA:true$
$
# Key usage: this is typical for a CA certificate. However since it will$
# prevent it being used as an test self-signed certificate it is best$
# left out by default.$
# keyUsage = cRLSign, keyCertSign$
$
# Include email address in subject alt name: another PKIX recommendation$
# subjectAltName=email:copy$
# Copy issuer details$
# issuerAltName=issuer:copy$
$
# DER hex encoding of an extension: beware experts only!$
# obj=DER:02:03$
# Where 'obj' is a standard or added object$
# You can even override a supported extension:$
# basicConstraints= critical, DER:30:03:01:01:FF$
$
[ crl_ext ]$
$
# CRL extensions.$
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.$
$
# issuerAltName=issuer:copy$
authorityKeyIdentifier=keyid:always$
$
[ proxy_cert_ext ]$
# These extensions should be added when creating a proxy certificate$
$
# This goes against PKIX guidelines but some CAs do it and some software$
# requires this to avoid interpreting an end user certificate as a CA.$
$
basicConstraints=CA:FALSE$
$
# This is typical in keyUsage for a client certificate.$
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment$
$
# PKIX recommendations harmless if included in all certificates.$
subjectKeyIdentifier=hash$
authorityKeyIdentifier=keyid,issuer$
$
# This stuff is for subjectAltName and issuerAltname.$
# Import the email address.$
# subjectAltName=email:copy$
# An alternative to produce certificates that aren't$
# deprecated according to PKIX.$
# subjectAltName=email:move$
$
# Copy subject details$
# issuerAltName=issuer:copy$
$
# This really needs to be in place for it to be a proxy certificate.$
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo$
$
####################################################################$
[ tsa ]$
$
default_tsa = tsa_config1       # the default TSA section$
$
[ tsa_config1 ]$
$
# These are used by the TSA reply generation only.$
dir             = ./demoCA              # TSA root directory$
serial          = $dir/tsaserial        # The current serial number (mandatory)$
crypto_device   = builtin               # OpenSSL engine to use for signing$
signer_cert     = $dir/tsacert.pem      # The TSA signing certificate$
                                        # (optional)$
certs           = $dir/cacert.pem       # Certificate chain to include in reply$
                                        # (optional)$
signer_key      = $dir/private/tsakey.pem # The TSA private key (optional)$
signer_digest  = sha256                 # Signing digest to use. (Optional)$
default_policy  = tsa_policy1           # Policy if request did not specify it$
                                        # (optional)$
other_policies  = tsa_policy2, tsa_policy3      # acceptable policies (optional)$
digests     = sha1, sha256, sha384, sha512  # Acceptable message digests (mandatory)$
accuracy        = secs:1, millisecs:500, microsecs:100  # (optional)$
clock_precision_digits  = 0     # number of digits after dot. (optional)$
ordering                = yes   # Is ordering defined for timestamps?$
                                # (optional, default: no)$
tsa_name                = yes   # Must the TSA name be included in the reply?$
                                # (optional, default: no)$
ess_cert_id_chain       = no    # Must the ESS cert id chain be included?$
                                # (optional, default: no)$
ess_cert_id_alg         = sha1  # algorithm to compute certificate$
                                # identifier (optional, default: sha1)$
$
[insta] # CMP using Insta Demo CA$
# Message transfer$
server = pki.certificate.fi:8700$
# proxy = # set this as far as needed, e.g., http://192.168.1.1:8080$
# tls_use = 0$
path = pkix/$
$
# Server authentication$
recipient = "/C=FI/O=Insta Demo/CN=Insta Demo CA" # or set srvcert or issuer$
ignore_keyusage = 1 # potentially needed quirk$
unprotected_errors = 1 # potentially needed quirk$
extracertsout = insta.extracerts.pem$
$
# Client authentication$
ref = 3078 # user identification$
secret = pass:insta # can be used for both client and server side$
$
# Generic message options$
cmd = ir # default operation, can be overridden on cmd line with, e.g., kur$
$
# Certificate enrollment$
subject = "/CN=openssl-cmp-test"$
newkey = insta.priv.pem$
out_trusted = insta.ca.crt$
certout = insta.cert.pem$
$
[pbm] # Password-based protection for Insta CA$
# Server and client authentication$
ref = $insta::ref # 3078$
secret = $insta::secret # pass:insta$
$
[signature] # Signature-based protection for Insta CA$
# Server authentication$
trusted = insta.ca.crt # does not include keyUsage digitalSignature$
$
# Client authentication$
secret = # disable PBM$
key = $insta::newkey # insta.priv.pem$
cert = $insta::certout # insta.cert.pem$
$
[ir]$
cmd = ir$
$
[cr]$
cmd = cr$
$
[kur]$
# Certificate update$
cmd = kur$
oldcert = $insta::certout # insta.cert.pem$
$
[rr]$
# Certificate revocation$
cmd = rr$
oldcert = $insta::certout # insta.cert.pem$
$
[ssl_sect]$
# system_default = system_default_sect$
system_default = hestia_openssl_sect$
$
[hestia_openssl_sect]$
Ciphersuites = TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384$
Options = PrioritizeChaCha$
$
[system_default_sect]$
CipherString = DEFAULT:@SECLEVEL=2root@painel:~#

Just for the records, this has been fixed.

We’ve also commented out the last lines of file /etc/ssl/openssl.cnf

[ssl_sect]
# system_default = system_default_sect
system_default = hestia_openssl_sect

[hestia_openssl_sect]
Ciphersuites = TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384
Options = PrioritizeChaCha

#[system_default_sect]
#CipherString = DEFAULT:@SECLEVEL=2

We have reset the variable LETSENCRYPT_FAIL_COUNT for two domains (as these domains had the count set to 31, Hestia doesn’t try to renew the certificates anymore).

for i in $(grep -rlE "LETSENCRYPT_FAIL_COUNT='[1-9][0-9]?'" /usr/local/hestia/data/users/); do sed -i "s/LETSENCRYPT_FAIL_COUNT='[1-9][0-9]*'/LETSENCRYPT_FAIL_COUNT='0'/" "$i";done
1 Like