Support for OVH API v2

[Kaauw]

Welcome

• Yes, I've searched similar issues on GitHub and didn't find any.

How do you use lego?

Through Traefik

Detailed Description

Hello Team,

While trying to generate a certificate for an application through traefik, I have an error while using an existing API Key.

When looking in the log, it try to reach /domain/zone/<name>/record but it's only available trough API V1. Currently, I'm using API V2.

2024-12-23T13:47:12Z ERR github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:528 > Unable to obtain ACME certificate for domains error="unable to generate a certificate for the domains [njos.be *.njos.be]: error: one or more domains had a problem:\n[*.njos.be] [*.njos.be] acme: error presenting token: ovh: error when call api to add record (/domain/zone/njos.be/record): OVHcloud API error (status code 403): Client::Forbidden: \"This credential is not valid\" (X-OVH-Query-Id: [...]\n[njos.be] [njos.be] acme: error presenting token: ovh: error when call api to add record (/domain/zone/njos.be/record): OVHcloud API error (status code 403): Client::Forbidden: \"This credential is not valid\" (X-OVH-Query-Id: [...])\n" ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory domains=["njos.be","*.njos.be"] providerName=njos.acme routerName=test@docker rule=Host(`test.njos.be`)

Because the API Key is strictly filtering API V2 targets, it's not working.

It would be great to have an environment variables and all the logic to choose between both API.

Regards,

Ben

[ldez]

Hello,

From what I can see, the v2 is in beta, there are missing endpoints.

I didn't find endpoints to create/delete records.

ping @rbeuque74 @yomovh

FYI, lego uses the official OVH API client: https://github.com/ovh/go-ovh

[Neustradamus]

@ldez: I have created a ticket about your problem here:

• v2: Missing endpoints to create/delete records ovh/go-ovh#88

[rbeuque74]

Hello,

We are currently rewriting some part of our information system, to migrate endpoints from v1 to v2.
DNS zone management haven't been migrated to v2 yet, hence, you need to use the v1 endpoint instead.

Regarding your issue, there is no issue for you to use Lego : credentials for APIv1 and APIv2 are the same. You can use Lego using Traefik with your API credential, it will work.

@ldez there is no real issue here, APIv2 doesn't support DNS yet, hence nothing to do on lego side ;)

Romain