Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
subdomain.domain.de
npmplus version (docker):
- [2026-07-24-r1-a30a954-2.15.1]
certbot dns plugin is missing for my host skrime.eu
I have already script running which updates my local IP daily to the host as an
"A record" - subdomain.domain.de - IP -> This works flawlessly
I would need a plugin for my host and here is the API [API • SKRIME](skrime.eu / api)
I would like to use it for *.subdomain.domain.de and run it on a NAS (918+ synology) docker behind a fritzbox as the router.
Any help appreciated.
I am sorry but I don't understand what the problem is with Let's Encrypt. It sounds like you are trying to configure a system using NPM Plus which is a fork of NGINX Proxy Manager (NPM). You should probably contact them to ensure your system is compatible with their configuration requirements.
It looks like skrime is a hosting service and your DNS provider. It does not look like Certbot supports Skrime for DNS Challenges through a provided plugin or even a 3rd party plugin. I also did not see Skrime supported by any other popular ACME Clients. Is it known by a different name? I could not find any docs at the Skrime site about their API for DNS updates. The link you provided requires a login id for their system.
You may be able to use an HTTP Challenge instead but consult with NPM Plus on how to set that up.
Hello,
thank you for the reply. This was a misunderstanding then from my side as I thought certbot was deeply connected with letsencrypt. I took some screenshots for you as it is behind a login as you stated.
Thank you anyways.
That api looks like for bulk ordering, so I'd rather not use it on a public sitting server. looks like it overwrite entire DNS zone, so unless your server has entire zonedump dns record wouldn't be right.
Hello yes it also states that somewhere that it cannot pinpoint just certain DNS records but touches all of them. What I am working now is a call to get all records, change the A record to an IP and publish the whole list again
Many years ago that was true but the EFF has been maintaining Certbot for a long time. You can reach them at their github: GitHub - certbot/certbot: Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol. · GitHub
That said, you don't just have Certbot involved. I know that NPM uses many custom techniques to control Certbot. So not only do you need Certbot do satisfy the challenges to get a cert it has to do so in a way compatible with NPM.
I doubt the EFF will create a plugin for your DNS provider. They only maintain a small number of these plugins themselves and these are for some of the most popular DNS providers globally. Instead of that you could use the --manual-auth-hook and --manual-cleanup-hook for your DNS. You will have to make sure NPM will run Certbot with these options if your config requires that.
You only need to do a DNS Challenge for a wildcard cert. Is that absolutely required? Many people try that until they realize it is much easier to use an HTTP Challenge for the limited number of domain names they use. NPM has built-in support for that and no extra coding required.
