You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2020. It is now read-only.
A certificate (re-)deploy fails if the key has changed,
and certificate filename timestamping is disabled.
this bug can be worked around if you enable timestamping on the certificate filenames,
or if you temporarily delete/set another certificate/key in the active profile.
Error Received from the REST call:
02/19/2019:10:02:09 restCall():/usr/bin/curl -sk --connect-timeout 5 -m 120 -H Content-Type: application/json --user letsencrypt:*********** https://***********/mgmt/tm/sys/crypto/key -X POST -d "{ "command": "install", "name": "/Common/HOSTNAMEHEREkey", "from-local-file": "/var/config/rest/downloads/HOSTNAMEHERE.key", "securityType": "normal" }"
02/19/2019:10:02:10 createCertFromUpload()[Write Back Results]: {
"apiError": 3,
"code": 400,
"errorStack": [],
"message": "01070317:3: profile /Common/HOSTNAMEHERE's key and certificate do not match"
}
The text was updated successfully, but these errors were encountered:
A certificate (re-)deploy fails if the key has changed,
and certificate filename timestamping is disabled.
this bug can be worked around if you enable timestamping on the certificate filenames,
or if you temporarily delete/set another certificate/key in the active profile.
Error Received from the REST call:
The text was updated successfully, but these errors were encountered: