Closed EugenKon closed 1 month ago
As workaround I changed key_type = "P256"
back and forth.
module.private-cloud.acme_certificate.ssl: Destroying... [id=812a9203-e251-ca25-f9db-2e97259d48a2]
module.private-cloud.aws_db_parameter_group.postgres_v16: Modifying... [id=nomad-v16-ssl-autovacuum]
module.private-cloud.aws_db_parameter_group.postgres_v16: Modifications complete after 1s [id=nomad-v16-ssl-autovacuum]
╷
│ Error: acme: error: 404 :: POST :: https://acme-v02.api.letsencrypt.org/acme/revoke-cert :: urn:ietf:params:acme:error:malformed :: Certificate from unrecognized issuer
│
Because of error I just removed ssl
from the state:
terraform state rm acme_certificate.ssl
@EugenKon generally you need to start with a fresh state if you change the server URL. See https://registry.terraform.io/providers/vancluever/acme/latest/docs/resources/registration and the notes at the top for more details.
Thanks!
I tested the solution with acme-staging. When I am done then I changed
server_url
and try to generate production ready certificate, but it was not generated, the old certificate still at AWS Certificate ManagerConfiguration