i had problems issuing a new certificate with the new api because the regr.json is overriding the —server command
I figured out that my account created in the closed beta is only available on the staging api - not on the v01 api. There I get a nice “Error: urn:acme:error:unauthorized :: The client lacks sufficient authorization :: No registration exists matching provided key” with my key, but this is the api where the cert revocation is provided. The other staging api is only providing the old happy hacker fake CA.
How can I revoke my old certificates when I created my new one?
According to 4.9.3 I can request a new certificate and revoke the old certificate with the new ACME account key associated with the domain. I will test it in the comming days when I renew my old certificate.