Will API V1 be activated today again (June 27th)?

Are you guys having the same issue as me? UTC is now 18:00 and the API V1 is still disabled.

I need to generate a few more SSL certs for some sites while I finish upgrading my code to support version 2.

Any thoughts about this?

**HTTP error: 403 Forbidden\nmap[Replay-Nonce:[0102UigKYLvMsjndPWAy6c5SFqkPuibjZXN8PZW1CGADC7c] Server:[nginx] Date:[Sat, 27 Jun 2020 18:02:34 GMT] Content-Type:[application/problem+json] Content-Length:[230] Boulder-Requester:[54508640] Cache-Control:[public, max-age=0, no-cache]]\n{\n “type”: “urn:acme:error:unauthorized”,\n “detail”: “Error creating new authz :: Validations for new domains are disabled in the V1 API (End of Life Plan for ACMEv1)”,\n “status”: 403\n}"
**

1 Like

@realleoman

https://letsencrypt.status.io/ says V1 is active at this time.
But Is there a reason preventing you from switching to V2?

Rip

1 Like

Thanks @Rip

Yes, I am using a service call lets-proxy to get my ssl certs automatically but it is obsolete since it does not support V2 API. (https://github.com/rekby/lets-proxy)

There is a new version, lets-proxy2, but I am still unsure if that one works out with new ACME V2 version.

Anyone here has used lets-proxy2 and installed succesfully?

1 Like