The emca from caspervector

emca's People

Contributors

Watchers

emca's Issues

Wrong chain cert in README

Problem resolved by downloading the x3 https://letsencrypt.org/certs/lets-encrypt-x3-cross-signed.pem chain cert.

The problem was described accurately here:
https://community.letsencrypt.org/t/solved-not-trusted-on-mobile-maybe-error-setting-up-chain-cert/13316

I think the letsencrypt server reserves the right to update the intermediate chain without warning.

Thanks for the useful code client!

Authorization not found or expired

When attempting to renew a cert for a domain that has expired I get:

./emca.py auth emca.conf; ./emca.py sign emca.conf > serveronly.crt

{
  "type": "urn:acme:error:unauthorized",
  "detail": "Error creating new cert :: authorizations for these names not found or expired: mydomain.example.com",
  "status": 403
}
Traceback (most recent call last):
  File "./emca.py", line 192, in <module>
    main(sys.argv)
  File "./emca.py", line 188, in main
    sign_cert(jws, cfg["csr"])
  File "./emca.py", line 165, in sign_cert
    http_except(ret, "signing certificate")
  File "./emca.py", line 20, in http_except
    raise Exception("unexpected HTTP status `%d' %s" % (ret, desc))
Exception: unexpected HTTP status `403' signing certificate

Either using old keys or generating a new .csr+keys (and ./emca.py reg emca.conf them) yields the above message for my domain.

agmt had to be updated as well agmt = https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf

Any ideas?

Recommend Projects