Linuxserver / letsencrypt

I am encountering a problem that despite my many attempts, I cannot find a solution.
Here is an example of my compose file (extract)

  - SUBDOMAINS=www,jipsy,etherpad
  - DHLEVEL=2048 #optional
  - ONLY_SUBDOMAINS=false #optional
  - STAGING=false #optional

In the DNS configuration at ovh, I have … (extract)


          |||to a server (IPv4 - A)|||
          |||to a server (IPv4 - A)|||
          |||to a server (IPv4 - A)|||
          |||to a server (IPv4 - A)|||
          |||to a server (IPv4 - A)||

The generation of authentication keys for the OVH API also raises some questions …

         according to documentation we need full access (Get, Put, Post, Delete) but for which path ? or (and jitsi ...) ?

Finally here is the error I ended up with … (extract docker log)

         Unsafe permissions on credentials configuration file: /config/dns-conf/ovh.ini
         Cleaning up challenges
         Error determining zone identifier for 403 Client Error: Forbidden for url: (Are your Application Key and Consumer Key values correct?)
         ERROR: Cert does not exist! Please see the validation error above. Make sure you entered correct credentials into the /config/dns-conf/ovh.ini file.

After a lot of tests, I don’t see what to change ! The error may be in the generation of authentication keys (I read that there was a necessary pre-authorization …) or in the DNS declarations.

Do you have an idea ?


did you put the full access credentials into the corresponding config file under /config/dns-conf?

you likely need to set perms to 0600 on your ovh.ini for the very first error

but it very clearly says your credentials are wrong for ovh in ovh.ini

please also share your full docker compose, you can redact any personal info

Hmmm, my gid/pid of the container is set to 0,0 …
Anyway hereby *.ini access

-rw-r–r-- 1 root root 245 Apr 22 13:09 digitalocean.ini
-rw-r–r-- 1 root root 201 Apr 22 13:09 dnsimple.ini
-rw-r–r-- 1 root root 283 Apr 22 13:09 dnsmadeeasy.ini
-rw-r–r-- 1 root root 292 Apr 22 13:09 domeneshop.ini
-rw-r–r-- 1 root root 135 Apr 22 13:09 gandi.ini
-rw-r–r-- 1 root root 208 Apr 22 13:09 google.json
-rw-r–r-- 1 root root 344 Apr 22 13:09 inwx.ini
-rw-r–r-- 1 root root 226 Apr 22 13:09 linode.ini
-rw-r–r-- 1 root root 232 Apr 22 13:09 luadns.ini
-rw-r–r-- 1 root root 182 Apr 22 13:09 nsone.ini
-rw-r–r-- 1 root root 300 Apr 22 13:44 ovh.ini
-rw-r–r-- 1 root root 429 Apr 22 13:09 rfc2136.ini
-rw-r–r-- 1 root root 258 Apr 22 13:09 route53.ini
-rw-r–r-- 1 root root 402 Apr 22 13:09 transip.ini

And the whole compose file

version: “2.1”
image: linuxserver/letsencrypt
container_name: letsencrypt
- PUID=0
- PGID=0
- TZ=Europe/Brussels
- SUBDOMAINS=www,jipsy,etherpad
- DHLEVEL=2048 #optional
- ONLY_SUBDOMAINS=false #optional
- STAGING=false #optional
- /etc/letsencrypt/docker/config:/config
- 443:443
- 80:80 #optional
restart: unless-stopped

I believe that the Docker part is ok but that on the other hand the values given at the time of the generation of the keys are erroneous. In the interface filled in, the domain is asked for. But what are the expected values? The main domain or each sub-domain? I also have questions about DNS entries. At the moment, I only have one A record per domain/subdomain.

Here is hyperlink of the OVH Authentification interface :

Thank you for your feedback!


I found another approach that …

sudo certbot certonly --cert-name -d,,, -w /var/www/_letsencrypt


certbot-auto certificates or

This ticker can be closed ! Thanks

in case anyone else comes here

  1. we don’t support using puid/pgid 0, it causes issues
  2. the logs clearly state the ovh key was incorrect or lacked permissions based on the requirements
  3. the unsafe permissions on the ini should likely be changed to 0600 to eliminate that error