mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #4191] Error Certbot add DNS Challenge witch OVH #2713
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2713
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kwetnico on GitHub (Nov 26, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4191
Hello,
When i wan't create a new certificat to DNS Challenge with OVH , i have this error :
Nginx Proxy Manager Version
2.12.1
Operating System
Debian12/Proxmox, 8.3
@badkeyy commented on GitHub (Dec 4, 2024):
Can't reproduce. For me this works fine with the public and current dev version of the proxy manager.
@jmatraszek commented on GitHub (Dec 5, 2024):
I have the same issue — just installed npm in LXC containter in Proxmox and had the same error message. Tried installing certbot plugins by running
app/scripts/install-certbot-plugins, but installingovhplugin fails with this error:Running the command by hand gives the following error:
@Wendigogo commented on GitHub (Dec 6, 2024):
Got that too.
Seems like certbot-dns-ovh is not up ta date : https://pypi.org/project/certbot-dns-ovh/#history.
Maybe that's why certbot-dns-ovh requires an acme-2 while others require an acme-3 version.
Switching to latest certbot-dns-ovh version could solve this issue.
Enjoy!
@Wendigogo commented on GitHub (Dec 6, 2024):
Trying to force certbot-dns-ovh version leads to this :
So It looks like you have to choose which certbot version you want depending on your provider.
As an enhancement, I would suggest to install only user related certbot-dns provider, by passing it as an argument to installation script. I don't see the point of having all these unused ones installed on my LXC.
EDIT : sorry, the EOL looks like crap in
code. :(@jmatraszek commented on GitHub (Dec 6, 2024):
Hey @Wendigogo, I was able to install OVH plugin by the command you provided, however this did not fix the original error, and I was unable to obtain a certificate. Did it work for you?
@Wendigogo commented on GitHub (Dec 6, 2024):
I didn't try it atm. I'm not at home and I don't want to break things now. ^_^
Maybe you should try with original version with:
. /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-ovh~=2.11.0 && deactivateMaybe that's why script stucks to this version.
EDIT: that doesn't work. After some digging, it looks like something more is missing:
certbot pluginsonly shows a few ones.@Wendigogo commented on GitHub (Dec 6, 2024):
Oh my!
I just see that you could install ONLY wanted certbot plugins in looking to the script:
So I made a clean install (thanks proxmox) and only use
./install-certbot-plugins ovh.No issue in installing but
certbot pluginsstill doesn't show ovh plugin. 😭@jmatraszek commented on GitHub (Dec 6, 2024):
Running
certbot pluginsgave me an idea to use MultiDns provider with the following config:This way, I could generate a cert successfully! Thanks, @Wendigogo.
@Wendigogo commented on GitHub (Dec 6, 2024):
From the GUI?
I find something:
When installing plugins with
/app/scripts/install-certbot-pluginsthere is a kind of chroot and they are installed in/opt/certbot/lib/python3.11/site-packages/instead of/usr/local/lib/python3.11/dist-packages/. That's why modules are not seen in "normal" shell.And if you look in
/usr/local/lib/python3.11/dist-packages/, the ONLY available module iscertbot_dns_multi.So MAYBE, the npm envirronement is not set correctly. I'm using an LXC in proxmox using this script for installation:.
@kwetnico commented on GitHub (Dec 8, 2024):
For information I have the problem with ovh, I use the same version as you with proxmox and the lxc script
@kwetnico commented on GitHub (Dec 8, 2024):
I tested with your solution: Multi Dns provider and same problem with DNS Challenge
@jmatraszek commented on GitHub (Dec 9, 2024):
Yes, from the GUI.
I also use LXC in proxmox with nginxproxymanager installed from the same script.
@kwetnico You sure you selected the
MultiDnsprovider? The screenshot showsOVH.@kwetnico commented on GitHub (Dec 11, 2024):
Yes it's ok to ovh with DNSMulti !
@github-actions[bot] commented on GitHub (Jun 25, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@philj0st commented on GitHub (Jul 20, 2025):
i still have this issue with NPM v2.12.6.
I could get it to work with the DnsMulti plugin instead of using DuckDNS or deSEC ones.
@github-actions[bot] commented on GitHub (Feb 7, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍